-
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
-
-
- 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
Hello, I was just wondering if there is any update on when this fix will be deployed ? We constantly work in several epics at once and we really need this report to be functional to help us with planning and resource allocation.
The workaround to create the issues and assign the epic afterwards is not a great one as we already have hundreds of stories in our backlog. Any status update would be much appreciated !
Chris Diller
added a comment - Seems odd that being thorough and adding the appropriate Epic when creating a new issue would result in loss of functionality. Very disappointing...
Chris Diller
added a comment - Seems odd that being thorough and adding the appropriate Epic when creating a new issue would result in loss of functionality. Very disappointing... 
Kevin Stanton
added a comment - This is critical for our management team. It makes it impossible to measure velocity in a team that has more than 1 epic being worked on. This in turn makes it impossible to plan future work or get any insight into possible completion dates.
Kevin Stanton
added a comment - This is critical for our management team. It makes it impossible to measure velocity in a team that has more than 1 epic being worked on. This in turn makes it impossible to plan future work or get any insight into possible completion dates. This is critical for our workflow and our processes. Please fix it as soon as possible. Thank you !
From the linked ticket is seems like there is still no workaround the epic was set a creation time correct?
Same here. This report is used regularly by our management team.
Very annoying bug from a user and management perspective. Our executive team is pushing us for epic transparency and forecasts.
Hi mbroda, I created bug SW-5001 caused by a commit connected with this issue. Epic Links are not being created during JIM import.