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
          release-burndown-chart-popup.png
          13 kB

          Form Name

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

            Gosia Kowalska added a comment -
            Atlassian Update – 22 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 22 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

            Alexander Casall added a comment -

            Do you have a workaround to find out which issues have been added?

            Alexander Casall added a comment - Do you have a workaround to find out which issues have been added?

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

                Created:
                Updated:
                Resolved: