-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
6.3.13.0, 6.3.13.1, 7.0.5, 7.1.7, 7.2.4, 7.4.3
-
6.03
-
47
-
Severity 2 - Major
-
5
-
-
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
- Enable "Parallel Sprints", as described here;
- Create a project;
- Create a version under that project;
- Create a board with all issues from the project;
- Create two or more Sprints, associating one or more issues of the board per Sprint;
- Estimate all issues and set the created version as "Fix Version" of the issues;
- Start all created Sprints;
- Close one or more issues in each Sprint;
- Complete all Sprints;
Starting Multiple Active Sprints without 'Parallel Sprints'
- Have an existing board (Board 1) with a filter showing: "project = SSP ORDER BY Rank ASC"
- 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"
- Now start a Sprint in Board 1, then Board 2
- 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
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-12616] Agile Boards containing multiple active Sprints lead to inaccurate information in Release Burndown report
The same issue we are facing in JIRA v7.10.2 too,any chance this issue can be fixed in latest release?
It was opened from more than 4 years.Please fixed this issue on priority.
We are also experiencing this issue with our parallel sprints, one in the US and one in ASIA.
Thank you for your consideration.
Hi, in my team we also have different sprints for different teams and both the release and epic burnup show issues as completed in the wrong sprint and the burnup show wrong data
We also have multiple teams and need the burndowns in our stakeholder reports. This bug makes them confusing and thus unusable for this purpose.
This issue is a problem for us. We have 3 parallel sprint teams that work across products. Given this issue, the Release Burndown report is not useful and it is difficult to ascertain predicted release completion.
The same issue we are facing in JIRA v7.3.6 too,any chance this issue can be fixed in latest release?
It was opened from more than 2 years.Please fixed this issue on priority.
we have multiple scrum teams work on the same product backlog and using common Board. In this case we see the release Burn down data is not shown correctly as which scrum team completed how many story points in each sprint.. Due to this the we don't get right report on how many more sprints would be needed for this release. Support Request #GHS-94657 is raised for the same.
we feel this Today it is very common for multiple teams to work on a single product backlog and hence reports need to be fixed. without this we can't use the release burn down which is one of most important report . Hence consider raising the priority for this Bug .
Kindly suggest if there is an WA for this issue until this is resolved.
The same issue we are facing in JIRA v7.0.10 too,any chance this issue can be fixed in latest release?
Also see this problem in our Jira software server (v8.14.1)
Please help to fix it. Thanks!