Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11354

Version Scope change on the Release Burndown report (added to version) should provide link to issues added/edited

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • AgileBoard
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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:

      1. 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.
      2. add a list of the JIRA issues numbers which were added/edited to cause the scope that was added to the version.

        1. release-burndown-chart-popup.png
          13 kB
          Dwight Holman

          Form Name

            [JSWSERVER-11354] Version Scope change on the Release Burndown report (added to version) should provide link to issues added/edited

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3067164 ] New: JAC Suggestion Workflow 3 [ 3661523 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2621454 ] New: JAC Suggestion Workflow [ 3067164 ]
            Gosia Kowalska made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]
            Rachel Lin (Inactive) made changes -
            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 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2043849 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323937 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032002 ] New: JIRA PM Feature Request Workflow v2 [ 2043849 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 753338 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032002 ]
            Martin (Inactive) made changes -
            Link New: This issue is related to JAGDEV-1068 [ JAGDEV-1068 ]
            Martin (Inactive) made changes -
            Labels New: triaged
            Dwight Holman created issue -

              Unassigned Unassigned
              6e687f59fb46 Dwight Holman
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: