-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
2016-01-18 Cloud, 2016-02-01 Cloud
-
None
Original description by reporter – Currently, if any issues in Sprint A in one board (Board A) got moved to Sprint B in another board (Board B), Sprint B will show up in the Velocity Report for Board A.
It would be nice to limit sprints within a board in the Velocity Report. So no other sprints belonging to other boards should show up in the report.
Summary
Velocity report include sprints from other boards.
Environment
- 2016-01-18 Cloud, 2016-02-01 Cloud
Steps to Reproduce
Basically this might happen in the following scenario:
- You have Board A with filter "project = A". You have Sprint 1 with issue A-1, A-2 inside it. The Sprint 1 has to be a future Sprint otherwise it correctly shows up in the report.
- You have Board B with filter "project = B". You have Sprint 2 with issue B-1,B-2 inside it. The Sprint 2 has to be a future Sprint otherwise it correctly shows up in the report.
If issue A-1 is moved to Sprint B it means that Sprint B will contain 1 issue that match the filter of Board A, thus will make Sprint B APPEAR in board A. If that happen then the velocity report of board A will include Sprint B too.
Expected Results
Velocity Report should only show sprints from other boards if the issues were moved between active sprints, not in planning phase (between future sprints).
As moving issues to-from sprints affects velocity (committed/completed), the report should show it accordingly.
Actual Results
- The chart include Sprint outside the scope of the board, and Sprint might result empty.
Workaround
No workaround.
- causes
-
-
- Closed
-
- was cloned as
-
-
- Closed
-
![[JIRA]](/images/icons/generic_link_16.png "[JIRA]"){kind=icon}
[JSWSERVER-12805] Velocity Report Should Only Show Sprints Related To The Current Board
Supporting Frederic's comment that this issue does exist in Jira Cloud.
Any timetable for a fix.
thagen - could you please create a support ticket at https://support.atlassian.com
That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com).
Kind regards,
Martin
JIRA Software
We are still having trouble in JIRA Cloud. During sprint planning, an issue from our "DataPro" board was accidentally assigned to another board's active sprint, "Analyst 2016F." Even though the sprint assignment was corrected, the other team's sprint is still showing up in our Velocity Chart.
karina.sobina198037109 - that is correct.
Kind regards,
Martin
JIRA Software
Deleted Account (Inactive)
added a comment - Do I understand correctly that this bug is fixed in Jira Cloud?
Deleted Account (Inactive)
added a comment - Do I understand correctly that this bug is fixed in Jira Cloud? 
Troy Liesinger
added a comment - Would love to see this addressed either by allowing me to filter the sprints in the report or just by allowing me to toggle the empty sprints that show up if we mistakenly add an issue to the wrong sprint.
Troy Liesinger
added a comment - Would love to see this addressed either by allowing me to filter the sprints in the report or just by allowing me to toggle the empty sprints that show up if we mistakenly add an issue to the wrong sprint. Is the behavior with this bug related to issues in planned sprints or active sprints?
If you think this is minor I'm not sure you understand how your own products work.
Where I work we are highly invested in the Atlassian suite. But I feel that all the problems we are encountering are not treated seriously. Small problems do add up and this could lead to us making a drastic decision in the future.
Atlassian if you read this - you have to improve your customer experience. It is unacceptable that a open bug is marked as resolved and that we receive no support whatsoever in a timely fashion.