We have had sprints getting closed automatically when a sprint that used the same sprint name is completed. Why is this happening and how can we prevent it.
For example 14.4.I3 being used by many boards.
One of the boards that was automatically closed had two sprints overlapping: 14.4.I3 and 14.3.2, but the board closing the 14.4.I3 that caused the others to be closed automatically only had 14.4.I3 active.
Downloaded JIRA 6.2.4 and JIRA Agile 22.214.171.124
Since the issues are actually sharing the same sprint, it makes sense that when this sprint is completed on one board it occurs on, any issues linked to this sprint on other boards will also get processed.
I don't have an answer for the other samesake sprints being completed too.. my guess is probably match happens on sprint name, iso sprintID. Maybe it's better to open a support case for this.
2 active sprints
this is possible via the parallel sprints setting on "labs" (see http://<hostname>:8080/secure/GHLabs.jspa?decorator=admin )
Doing what you asked, I identified the Sprint ID and they share the same ID. The scrum board that we did not complete the sprint, but it got completed automatically, actually also had 2 active sprints at the same time. I didn't think that was even possible. The second active sprint was older and had a different sprint id but it also got completed it appears. Really appreciate your help.
Is it possible to only have sprints created for a particular project to only show in the dropdown when selecting a sprint or when starting a sprint? We have all the Sprints created by all of the other teams in the dropdown. I would like to make it exclusively only those created for that project.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs