Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-17787

Expanded Reporting Capabilities for Team-managed Projects - Kanban

    XMLWordPrintable

Details

    • 13

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

    Description

      We'd like to upgrade all of our projects from legacy projects to next-gen projects but there is one item giving us pause. Legacy projects have a wide array of reporting capabilities that we rely on. With the new next-gen projects, there are only two available reports, both of which require the use of sprints. We are a Kanban shop so we're not going to be using sprints. This means that if we transitioned to using next-gen projects then we'd have zero visibility into our velocity. Measuring our velocity is important to our team so we won't be able to upgrade until this oversight is addressed.

       

      Attachments

        Issue Links

          is duplicated by

          Suggestion - JSWCLOUD-17405 Kanban reports in team-managed projects

          • Closed
          is related to

          Sub-task - The sub-task of the issue JSWCLOUD-17708 Sprint report in Next-gen

          • Closed

          Suggestion - JSWCLOUD-22859 Add user that closed the Sprint to the Sprint Burndown Report in Team managed projects

          • Closed

          Suggestion - JSWCLOUD-17914 Provide an epic report in Team-Managed scrum project

          • Gathering Interest
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              esa Erika Sa (Inactive)
              ddbb68823516 Roman Reynebeau
              Votes:
              52 Vote for this issue
              Watchers:
              33 Start watching this issue

              Dates

                Created:
                Updated: