Possible Estimation
1. Problem Statement
A Data Fetcher in Jira is a tool that allows you to extract data from Jira and store it in a desired format (CSV).
2. Analysis
Checked the API’s for getting worklog details.
| Method | API | Description | |
---|---|---|---|---|
1 | Get Issue | GET |
| will return the project details |
2 | Get Worklog | GET |
| will return the worklog |
3.Solution
Step1: Get the project list from the cloud instance.
Step2: Get the issue list from the project list.
Step3: Get the worklog from all the issues on the list.
Step4: Create a CSV that contains a worklog of all the issues for the particular projects.
4.Estimation
| Tasks | Description | Estimated Efforts(hrs) |
---|---|---|---|
1 | UI |
|
|
1.1 | Create an Atlassian project with pre-requisites. | create a cloud project with pre-requisites | 2h |
1.2 | Create an UI with an Add Projects Field, Date Range Field, Worklog Data Button, and Worklog Data Table. | complete UI design | 10h |
2 | Business Logic |
|
|
2.1 | List the APIs and check with Postman. |
| 3h |
2.2 | Script for the frontend to get user-entered data from the UI. | will have the user enter details | 6h |
2.3 | Get the project list. | Call APIs and get the details | 2h |
2.4 | Get the issue list. | Call APIs and get the details | 2h |
2.5 | Get the worklog data. | Call APIs and get the details | 3h |
2.6 | Get the worklog data in the UI table view. |
| 4h |
2.7 | Get the worklog data in a csv file with the click of the csv download button. | Create a CSV to get the worklog data | 3h |
2.6 | Testing |
| 2h |
3 | Logger Implementation |
|
|
3.1 | logger implement |
| 7h |
4 | End-to-end testing |
|
|
| Complete process testing |
| 8h |
| Total Estimation Time |
| 52h |
Estimation for filter update
Task | Description |
|
---|---|---|
User Filter | Need to allow multi select user functionality | 10h |
Project Filter | Need to allow multi select project functionality | 10h |