-
Suggestion
-
Resolution: Won't Do
-
None
As a scrum master (or product owner) I want to understand WHY scope changed during development of a release.
The Release Burndown report helpfully shows scope changes as "added to version" (see attached screenshot), but leaves me to manually figure out what was added or edited to result in that change.
Suggested solutions:
- turn the caption "added to version" into a link to the issues that caused the version scope to change. This would greatly reduce the effort required to understand why scope changed.
- add a list of the JIRA issues numbers which were added/edited to cause the scope that was added to the version.
[JSWSERVER-11354] Version Scope change on the Release Burndown report (added to version) should provide link to issues added/edited
Workflow | Original: JAC Suggestion Workflow [ 3067164 ] | New: JAC Suggestion Workflow 3 [ 3661523 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2621454 ] | New: JAC Suggestion Workflow [ 3067164 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2323937 ] | New: Confluence Workflow - Public Facing v4 [ 2621454 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2043849 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323937 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032002 ] | New: JIRA PM Feature Request Workflow v2 [ 2043849 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 753338 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032002 ] |
Link | New: This issue is related to JAGDEV-1068 [ JAGDEV-1068 ] |
Labels | New: triaged |