Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-12616

Agile Boards containing multiple active Sprints lead to inaccurate information in Release Burndown report

    XMLWordPrintable

    Details

    • Introduced in Version:
      6.03
    • Support reference count:
      31
    • Symptom Severity:
      Severity 3 - Minor
    • UIS:
      5
    • Current Status:
      Hide
      Atlassian Update – 22 Oct 2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem.
      The team has acknowledged that the issue has an impact on the Software Teams and agree that it has to be prioritised in the Long Term.

      We would aim to address the problem within the next 6-9 months or so, yet please do not consider this a deadline to fix the bug, but rather as an estimated timeline.

      While our decision to prioritise this in distant timeline might be frustrating, we want to be clear in managing your expectations.
      The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 22 Oct 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. The team has acknowledged that the issue has an impact on the Software Teams and agree that it has to be prioritised in the Long Term . We would aim to address the problem within the next 6-9 months or so, yet please do not consider this a deadline to fix the bug, but rather as an estimated timeline. While our decision to prioritise this in distant timeline might be frustrating, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      Description

      Summary

      • In the Release Burndown report, if the "Active" period of two or more sprints that contain issues under a given Version overlap, all issues will be displayed under one single, latest sprint.
      • Having multiple overlapping Sprints on a single Agile board can happen if:
        • "Parallel Sprints" is enabled;
        • The board contains issues from other boards;

      Steps to Reproduce

      With "Parallel Sprints" enabled
      1. Enable "Parallel Sprints", as described here;
      2. Create a project;
      3. Create a version under that project;
      4. Create a board with all issues from the project;
      5. Create two or more Sprints, associating one or more issues of the board per Sprint;
      6. Estimate all issues and set the created version as "Fix Version" of the issues;
      7. Start all created Sprints;
      8. Close one or more issues in each Sprint;
      9. Complete all Sprints;

      Starting Multiple Active Sprints without 'Parallel Sprints'

      1. Have an existing board (Board 1) with a filter showing: "project = SSP ORDER BY Rank ASC"
      2. Create a second board (Board 2) with a filter covering just a limited set of issues in the SSP project: "issue in (SSP-1,SSP-2) ORDER BY Rank ASC"
      3. Now start a Sprint in Board 1, then Board 2
      4. Refresh Board 1, notice that there are two active Sprints showing

      Expected Result

      • Release Burndown report will show list of issue respectively to its own sprint

      Actual Result

      • Release Burndown report shows all the issues under the Sprint last closed.

      Workaround

      If due to Parallel Sprints
      • Avoid using parallel sprint

        Attachments

        1. agile.png
          agile.png
          65 kB
        2. agile1.png
          agile1.png
          69 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              amasut Azfar Masut (Inactive)
              Votes:
              43 Vote for this issue
              Watchers:
              50 Start watching this issue

                Dates

                Created:
                Updated: