• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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?

            [JSWSERVER-12419] Duplicate Sprint names causes multiple issues with teams

            Benz Kek (Inactive) made changes -
            Link New: This issue relates to JSWSERVER-15634 [ JSWSERVER-15634 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3066013 ] New: JAC Suggestion Workflow 3 [ 3663263 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2625924 ] New: JAC Suggestion Workflow [ 3066013 ]
            Earl McCutcheon made changes -
            Link New: This issue relates to JSWSERVER-11992 [ JSWSERVER-11992 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2322596 ] New: Confluence Workflow - Public Facing v4 [ 2625924 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040277 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2322596 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2028848 ] New: JIRA PM Feature Request Workflow v2 [ 2040277 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 947957 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2028848 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Yilin (Inactive) made changes -
            Link New: This issue is duplicated by GHS-11502 [ GHS-11502 ]

              Unassigned Unassigned
              kevin.dalton Kevin Dalton
              Votes:
              0 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: