-
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.
