We constantly run into issues where Team A using sprint name Iteration 1 and Team B uses the same name but on 2 different sprints. This causes teams to not be able to start/complete sprints since the owners of Team A are not on Team B. The only way around this we have found is to have team remove the unstarted sprint and recreate it with a new name or have a JIRA Administrator complete/start it for them since we have access to all projects.
Is there a way to enforce/correct the use of duplicate sprint names so it does not occur on current/future sprints?
Awesome so how do you tell 5000 associates on just one of our instances which has 500 projects and 1060 agile boards that information and have them change there ways. We are currently running 3 instances all are roughly the same in size as the one I listed.
Why does Atlassian allow duplicates to be entered when they know it causes issues.
Here is our team's workaround:
1) Sprints are uniquely named by project
2) Only 1 person creates Sprints
3) Sprints are created from the ecosystem board
4) A Sprint goal story is created mid-sprint for each team, and is assigned to the next sprint
this ensures unique naming, only one sprint ID per sprint, and the Sprint becomes visible on related boards for team A, team B, etc.
...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....
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