20.Estimations
- Gaurav (Unlicensed)
# | Tasks | Sub-task | Estimate(man-hours) |
1 | Initial setup |
| 2 |
2 | Creation of sub-task based on object ids for apps other than IMAGEREQ |
|
|
|
| Design screen for mapping for new JSD | 6 |
|
| Introduce fields in Field Configuration to distinguish between different JSD portals | 5 |
|
| Put checks in the code to identify this new JSD type and create sub-task based on object ids | 24 |
|
|
|
|
3 | Creation of sub-tasks using comma separated values of object ids manually entered by an user |
|
|
|
| Putting the code to identify the request type as multiple request types(in citi and otherwise) now will map to samne issue type | 16 |
|
| Making changes in the code to create support object(not in citi) | 5 |
|
|
|
|
4 | Testing |
|
|
|
| Regression and new features | 8 |
|
|
|
|
5 | Deployment |
|
|
|
| Deployment to QA and Prod | 4 |
| Total |
| 70 |
Note:- Apart from these above requirement there is one more requirement which is about making the Jira imaging plugin resistant to failure by abstracting out the core logic into another process. The actual requirement is as follows: Functionality to tighten up the failure response of the Imaging app in the new multi-node environment based on the discussions with Artic. Artic team is yet to comeback with the details. After getting all the required details we will be estimating this requirement as well.
# | Tasks(Yet to be estimated) | Sub-task | Estimate(man-hours) |
1 | Functionality to tighten up the failure response of the Imaging app in the new multi-node environment. |
|
|