Details
-
Bug
-
Resolution: Fixed
-
High
-
Archived Jira Software Cloud, 7.1.1, 7.3.0, 7.2.6, 7.2.12, 7.6.6, 8.13.1
-
7.01
-
48
-
Severity 2 - Major
-
694
-
-
Description
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
Summary
Scenario A
Issues which Sprint has been set at creation issue screen will not appear in burndown chart if the sprint is removed from this issue.
Steps to Reproduce:
- Create a JIRA Software Project
- Create a Sprint - You can start the Sprint or not.
- Create an issue and set the Sprint in the issue creation screen
- Start the Sprint if you have not started.
- Remove the issue from the Sprint.
Scenario B
The is also applicable for issues in the backlog that were previously associated with an active sprint and moved back to the backlog when the sprint is completed.
Steps to reproduce:
- Create an issue
- Move the issue to the active sprint
- Complete the sprint and choose to move the issue to the backlog
- Create a new Sprint
- Move the issue to the active sprint (Start the Sprint if its not started)
- Move the issue back to the backlog
- The issue will disappear from the burndown chart although it was originally created in the backlog without specifying a sprint
Expected Results
The burndown chart would show the issue as "Scope change issue removed"
Actual Results
The burndown chart does not show the issue on it and make it seems like the issue never existed.
Workaround
The only known workaround for now is to put the issue back in the Sprint after removal and then remove again
No known workaround at this time, the previously noted workaround affects the output of the velocity chart
Note
Affected deleted issue.
Attachments
Issue Links
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
PSR-442 Loading...
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Gathering Impact
-
-
-
-
- is duplicated by
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-