-
Bug
-
Resolution: Fixed
-
High
-
None
-
15
-
Severity 1 - Critical
-
3
-
Steps to reproduce:
- Create an epic.
- Create a issue in the epic. Make sure that you populate the epic field when you create the issue.
- Create a sprint. Put the newly created issue in the sprint and start the sprint.
- Move the issue to done and complete the sprint.
- Go to the Epic Burndown chart.
Expected result:
The issue shows up on the Epic Burndown chart, and is also present in the 'Completed Issues' section.
Actual result:
The issue doesn't show up in the Epic Burndown.
Notes on the fix:
The fix will be not correct old issues that were created with an epic link. It will only affect new issues.
To correct previous Epic Burndown reports on a Cloud JIRA site please contact Cloud support
- is duplicated by
-
JSWCLOUD-15944 Epic burndown chart report not displaying issues when linked during issue creation
-
- Closed
-
-
SW-4807 Failed to load
- causes
-
SW-5001 Failed to load
- duplicates
-
SW-4335 Failed to load
- mentioned in
-
Page Failed to load
[JSWCLOUD-15938] Epic burndown chart doesn't include issues that have the epic link populated at issue creation time
Workflow | Original: JSWCLOUD Bug Workflow [ 3191473 ] | New: JAC Bug Workflow v3 [ 3473741 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1546854 ] | New: JSWCLOUD Bug Workflow [ 3191473 ] |
Key |
Original:
|
New:
|
Project | Original: JIRA Software (including JIRA Agile) [ 12200 ] | New: JIRA Software for Cloud [ 18511 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Soaking [ 10041 ] | New: Resolved [ 5 ] |
Assignee | New: Nick [ npellow ] | |
Status | Original: Awaiting Soak [ 10040 ] | New: Soaking [ 10041 ] |
UIS - Server | Original: 9 | New: 3 |
UIS - Cloud | Original: 1 |
UIS - Server | Original: 12 | New: 9 |
UIS - Server | Original: 15 | New: 12 |