-
Bug
-
Resolution: Fixed
-
Medium
-
6.0.8, 6.7.11
-
6
-
Summary
Agile boards have Days in Column value offset by a large incorrect amount
Steps to Reproduce
- Create or use a project with an agile simplified workflow.
- Ensure the Days in Column feature is enabled.
- On the board, transition an issue to the same status it is currently in.
- View Days in Column
Expected Results
The Days in Column value remains the same.
Actual Results
The Days in Column dots max out and mousing over displays a huge value (e.g. over 16k days).
Solution / Workaround
Transition the ticket to other status, and then back to the target column. Consider changing the workflow to prevent recursive transitions.
Notes/Details
".. days in column" data is based on opt_data.issue.timeInColumn.days value and is calculated the following way:
if (b.timeInColumn) { b.timeInColumn.days = Math.floor((b.timeInColumn.durationPreviously + new Date().getTime() - b.timeInColumn.enteredStatus) / a) }
which is calculated from timeInColumn value from JSON https://<JIRA>/rest/greenhopper/1.0/xboard/work/allData.json?rapidViewId=<BOARD_ID>.
Normally, this data looks like:
"timeInColumn": { "enteredStatus": 1442936354000, "durationPreviously": 0 },
in case of an issue was transitioned to the same status it is currently in:
"timeInColumn": { "enteredStatus": 0, "durationPreviously": 2301491000 },
which leads to large opt_data.issue.timeInColumn.days value
- duplicates
-
JSWSERVER-11555 Days in Column value offset by a large incorrect amount when status transitioned to is the same as source.
- Closed
- is duplicated by
-
JSWSERVER-9639 If new issue is created the "X days in this column" marker is at full length
- Closed
- relates to
-
JSWSERVER-7380 Setting Flagging field with loop transition sets days in column to incorrect value
- Closed
- mentioned in
-
Page Loading...