-
Suggestion
-
Resolution: Answered
-
None
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. We even had an issue today where 1 planned sprint had the same name created as an active sprint on a different board. When the planned sprint was attempted to be started it could not start. When they renamed the planned sprint it renamed the active sprint. They had to delete the planned sprint and start over just to get back this but there was not indication of the issue in the UI. I was able to see this in the database.
We a way to enforce/correct the use of duplicate sprint names so it does not occur on current/future sprints?
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-12419] Duplicate Sprint names causes multiple issues with teams
| Link | New: This issue relates to JSWSERVER-15634 [ JSWSERVER-15634 ] |
| Workflow | Original: JAC Suggestion Workflow [ 3066013 ] | New: JAC Suggestion Workflow 3 [ 3663263 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2625924 ] | New: JAC Suggestion Workflow [ 3066013 ] |
Frankly, I'm absolutely staggered that Atlassian have closed this issue and issue
JSW-9961. Sprints being named the same is not only highly likely to happen, it creates massive disruption for users, Project Admins and JIRA Admins across the instance.
This is still and issue for us.
Please at least add a warning of "that name is already taken"
| Link | New: This issue relates to JSWSERVER-11992 [ JSWSERVER-11992 ] |
This is still an issue. It seems that sprints with the same names in different projects get the same id, and closing one closes the other.
Please fix.
Thanks
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2322596 ] | New: Confluence Workflow - Public Facing v4 [ 2625924 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
This is definitely a bug. You shouldn't be able to give a sprint the same name as another sprint if that causes these issues. The issue should be re-opened.
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2040277 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2322596 ] |
Yes, agree that this is still an issue for us as well - please at least add a warning of "that name is already taken" when a user tries to name a sprint or save a sprint using a name that is already taken. I don't understand why this issue is closed when the basic intent of it has not yet been met, and this problem continues to create so many issues.