-
Bug
-
Resolution: Duplicate
-
Highest
-
None
Summary
Epic burndown chart is not displaying information for tickets with time estimation matching board configuration without JIRA Software. This problem appears to occur specifically when the issue is added to the Epic during issue creation, as opposed to being added after the issue is already created.
Environment
JIRA v1000.35.2
JIRA Agile v1000.0.4-D20160607T123719
Steps to Reproduce
- Create a new Agile board
- Configure the board estimation to be based on Original Time Estimate
- Create a new Epic within an Agile board
- Create a new issue within that Epic
- Give the new issue Original Time Estimate points and Time Remaining points
- Create a new sprint within the Agile board
- Add the new ticket to the sprint
- Start the sprint
- View the Epic burndown chart report
Expected Results
Report should display ticket information for the one ticket you added to the Epic
Actual Results
No issues are displayed
Instead the Epic burndown chart report displays a message stating you have no issues with estimations
Workaround
When creating issues do not link the Epic to the ticket. Once the issue has been created, linking the Epic should result in issues being reported.
It should be noted that for any issues that had their Epic linked during creation, they will not show up. There is currently no work around to fix these issues.
- duplicates
-
-
- Closed
-
[JSWCLOUD-15944] Epic burndown chart report not displaying issues when linked during issue creation
| Workflow | Original: JSWCLOUD Bug Workflow [ 3191274 ] | New: JAC Bug Workflow v3 [ 3473594 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1546775 ] | New: JSWCLOUD Bug Workflow [ 3191274 ] |
| Key |
Original:
|
New:
|
| Affects Version/s | New: 1000.5.0 Cloud [ 70343 ] | |
| Affects Version/s | Original: 1000.5.0 Cloud [ 61751 ] | |
| Project | Original: JIRA Software (including JIRA Agile) [ 12200 ] | New: JIRA Software for Cloud [ 18511 ] |
| Labels | New: affects-cloud |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1406290 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1546775 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
| Description |
Original:
h3. Summary
Epic burndown chart is not displaying information for tickets with time estimation matching board configuration without JIRA Software. This problem appears to occur specifically when the issue is added to the Epic during issue creation, as opposed to being added after the issue is already created. h3. Environment JIRA v1000.35.2 JIRA Agile v1000.0.4-D20160607T123719 h3. Steps to Reproduce # Create a new Agile board # Configure the board estimation to be based on Original Time Estimate # Create a new Epic within an Agile board # Create a new issue within that Epic # Give the new issue Original Time Estimate points and Time Remaining points # Create a new sprint within the Agile board # Add the new ticket to the sprint # Start the sprint # View the Epic burndown chart report h3. Expected Results Report should display ticket information for the one ticket you added to the Epic h3. Actual Results No issues are displayed Instead the Epic burndown chart report displays a message stating you have no issues with estimations h3. Workaround When creating issues do not link the Epic to the ticket. Once the issue has been created, linking the Epic should result in issues being reported. |
New:
h3. Summary
Epic burndown chart is not displaying information for tickets with time estimation matching board configuration without JIRA Software. This problem appears to occur specifically when the issue is added to the Epic during issue creation, as opposed to being added after the issue is already created. h3. Environment JIRA v1000.35.2 JIRA Agile v1000.0.4-D20160607T123719 h3. Steps to Reproduce # Create a new Agile board # Configure the board estimation to be based on Original Time Estimate # Create a new Epic within an Agile board # Create a new issue within that Epic # Give the new issue Original Time Estimate points and Time Remaining points # Create a new sprint within the Agile board # Add the new ticket to the sprint # Start the sprint # View the Epic burndown chart report h3. Expected Results Report should display ticket information for the one ticket you added to the Epic h3. Actual Results No issues are displayed Instead the Epic burndown chart report displays a message stating you have no issues with estimations h3. Workaround When creating issues do not link the Epic to the ticket. Once the issue has been created, linking the Epic should result in issues being reported. It should be noted that for any issues that had their Epic linked during creation, they will not show up. There is currently no work around to fix these issues. |
Closing as a duplicate of
JSW-13750.