Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90474

Add user that closed the Sprint to the Sprint Burndown Report in Team managed projects

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      In Company managed projects the Sprint report included the details of the user that completed a sprint, however, in Team managed projects (Previously Next-gen) the functionality of the "Sprint report" was combined with the "Sprint Burndown Report" as detailed in:

      Problem

      As the Sprint report was removed from team managed projects the user that completed the sprint data was not added to the Sprint Burndown report, and there is currently no method to see this data in Team managed project reports

      Suggested Fix:

      Add the user that completed sprint value to the Sprint Burndown Report in team managed projects

      Workaround

      Use "Company managed projects" for access to the Sprint Report to see the user that completed the sprint, you can migrate a "Team managed project" to a "Company managed project" as covered in:

            [JRACLOUD-90474] Add user that closed the Sprint to the Sprint Burndown Report in Team managed projects

            Matthew Hunter added a comment -
            Atlassian Update - March 14, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - March 14, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              emccutcheon Earl McCutcheon
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: