-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
Component/s: Space - Reports
-
2
-
Severity 3 - Minor
Issue Summary
Predicted completion dates calculation on Version Report is not accurate.
It is considering the first working date in the version's start date week instead of considering the version's start date in the prediction calculation
Environment
Jira Software cloud
Steps to Reproduce
- Create issues in a classic Scrum board
- Estimate the issues in story points
- Create a version
- Add the issues to the version
- Add the issues to a sprint and start the sprint
- Move at least one ticket to the right-most column of the board
- Look at the version report predicted completion dates
Expected Results
Predicted completion date is calculated based on the version's start date
Actual Results
Predicted completion date is calculated based on the first working day of version's start date, which affects the prediction
Notes
The report uses the API call GET /rapidviewconfig/workingdays/rates?rapidViewId=<RAPID_VIEW_ID>&startDate=<START_DATE_MS>&endDate=<END_DATE_MS> to get the working days.
The first day is not the version date, it's the first working day in the version's start date week instead.
Values extracted from a test environment:
{
"timezone": "America/Sao_Paulo",
"rates": [
{
"start": 1557003600000, 04/May 6PM
"end": 1557100800000, 05/May 9PM
"rate": 0
},
{
"start": 1557100800000, 05/May 9PM
"end": 1557532800000, 10/May 9PM
"rate": 1
},
{
"start": 1557532800000,
"end": 1557705600000,
"rate": 0
},
{
"start": 1557705600000,
"end": 1558137600000,
"rate": 1
},
{
"start": 1558137600000,
"end": 1558310400000,
"rate": 0
},
{
"start": 1558310400000,
"end": 1558742400000,
"rate": 1
},
{
"start": 1558742400000,
"end": 1558915200000,
"rate": 0
},
{
"start": 1558915200000,
"end": 1559347200000,
"rate": 1
},
{
"start": 1559347200000,
"end": 1559520000000,
"rate": 0
},
{
"start": 1559520000000,
"end": 1559952000000,
"rate": 1
},
{
"start": 1559952000000,
"end": 1560124800000,
"rate": 0
},
{
"start": 1560124800000,
"end": 1560556800000,
"rate": 1
},
{
"start": 1560556800000,
"end": 1560729600000,
"rate": 0
},
{
"start": 1560729600000,
"end": 1561161600000,
"rate": 1
},
{
"start": 1561161600000,
"end": 1561334400000,
"rate": 0
},
{
"start": 1561334400000,
"end": 1561766400000,
"rate": 1
},
{
"start": 1561766400000,
"end": 1561939200000,
"rate": 0
},
{
"start": 1561939200000,
"end": 1562371200000,
"rate": 1
},
{
"start": 1562371200000,
"end": 1562544000000,
"rate": 0
},
{
"start": 1562544000000,
"end": 1562976000000,
"rate": 1
},
{
"start": 1562976000000,
"end": 1563148800000,
"rate": 0
},
{
"start": 1563148800000,
"end": 1563580800000,
"rate": 1
},
{
"start": 1563580800000,
"end": 1563753600000,
"rate": 0
},
{
"start": 1563753600000,
"end": 1564185600000,
"rate": 1
},
{
"start": 1564185600000,
"end": 1564358400000,
"rate": 0
},
{
"start": 1564358400000,
"end": 1564790400000,
"rate": 1
},
{
"start": 1564790400000,
"end": 1564963200000,
"rate": 0
},
{
"start": 1564963200000,
"end": 1565395200000,
"rate": 1
},
{
"start": 1565395200000,
"end": 1565568000000,
"rate": 0
},
{
"start": 1565568000000,
"end": 1565902800000,
"rate": 1
}
]
}
Workaround
No workaround for now
- is related to
-
JRACLOUD-90170 JIRA Agile version report does not correctly take into account non-working days
-
- Closed
-