Velocity Chart is including sprints of other projects

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:

  • Wrong_sprint_1
  • Wrong_sprint_2

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

this situation?

Any comments would be very helpful. 

6 answers

This is bug in JIRA, tracked here - https://jira.atlassian.com/browse/JSW-13783

please vote on this to get more visibility, so that they can look into this and fix this.

thanks

The bug i mentioned above is for JIRA server.

For JIRA cloud this should have been fixed - https://jira.atlassian.com/browse/JSW-12805, please verify.

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.

Voted! Thanks for the link.

2 votes

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.

Best,

Max Förster

Hello

 

We are facing same issue on our instance .

Did you guys get any solution ? 

Help will be appreciated .

 

Thanks

Heman

 

We are seeing this now as well.  We just started using Portfolio and it started to happen.  Not sure that we are doing anything else different.

We are also seeing this issue. We just started using Portfolio also but I saw this before we put that add-on in our production environment. Don't think it is related to Portfolio. 

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:

https://community.atlassian.com/t5/JIRA-questions/How-do-I-remove-an-issue-from-a-completed-sprint/qaq-p/123077

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.

I'm not actually finding the issues that are causing this though. I've checked the sprints in question, and there are no errant issues.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,325 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot