We have been encountering a problem which Velocity Chart is including sprints of other projects.
Let me assume that there is one project:"project_1" now. All correct sprints have "Atlas" at the start of sprint name.
When display Velocity Chart of "project_1" board, there are wrong sprints like:
If we search for Atlas tickets with the above sprint name, there is no result. When perform JQL (project=project_1
and sprint in (Wrong_sprint_1), no result though.
Is this known issue? If yes, what is the issue number? What do we need to investigate and how can we resolve
Any comments would be very helpful.
JSW-12805 did not adequately resolve this problem, and it was clonged to JSW-13783. However, In my opinion, the new ticket still does not propose the proper expected results to resolve the problem.
Please also check out my recent comment for JSW-13783 https://jira.atlassian.com/browse/JSW-13783 and up-vote this ticket, especially if you agree with my comments.
We're also facing this issue at the moment on our server instance. A few weeks ago the velocity chart started to mix up our three Projects for the scrum teams. The velocity reports of two boards are filled with sprints of every team. Only one team seems not to be affected, for unknown reason. Just opened a ticket with the support as well.
I've had this happen as well, but know the cause for my scenario. It happened when a ticket was once part of another project and was in a sprint on that project. It then moved over to my project, but since it was once part of other sprints, those sprints now show up in my project's velocity charts.
Unfortunately, I see no way to remove it from being in those other sprints, since they were closed out. I've considered copying the ticket and only having the new version in my project, but I'm not thrilled with that approach...
Good news! I was able to find a way to remove those other project's sprints from the ticket by making use of the "bulk edit" feature. Followed the advice listed here:
Removing those other sprints from it have cleared up the velocity chart. Not really great way to do this (resolving https://jira.atlassian.com/browse/JSWSERVER-13783 would be nicer) but this has worked for me in the meantime.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG