Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-13214

Backlog: Prevent Stories from being added to a sprint which are not READY

XMLWordPrintable

    • 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.

      It would be great if we could configure a warning popup, if the user tries to add a Story/Issue to a planned/ongoing Sprint, when the Story is not in a certain status.

      Agile/Scrum Teams often use a "Definition of Ready" gateway to take stories for the next sprint. We have a configured a dedicated workflow step, a status called "Ready for Implementation" for this. When reaching this status, the workflow ensures that all relevant fields were filled before. We would like to prevent users, from adding Issues to a sprint container, which are not in this Status.

      Currently, they can also add Issues in status "Open" to a sprint. Of course we could change the board filter, to display only Issues in Status "Ready for Implementation" on the Backlog. But we really like the Idea of a groomed and ranked Backlog, with the READY items on top and the rough ideas at the bottom.

          Form Name

            [JSWSERVER-13214] Backlog: Prevent Stories from being added to a sprint which are not READY

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069125 ] New: JAC Suggestion Workflow 3 [ 3662437 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626117 ] New: JAC Suggestion Workflow [ 3069125 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2321098 ] New: Confluence Workflow - Public Facing v4 [ 2626117 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040365 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2321098 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2028949 ] New: JIRA PM Feature Request Workflow v2 [ 2040365 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 1138298 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2028949 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            Martin (Inactive) added a comment -

            This should be possible today with workflow conditions, please see the documentation at https://confluence.atlassian.com/adminjiraserver070/advanced-workflow-configuration-749383189.html

            Kind regards,
            Martin
            JIRA Software

            Martin (Inactive) added a comment - This should be possible today with workflow conditions, please see the documentation at https://confluence.atlassian.com/adminjiraserver070/advanced-workflow-configuration-749383189.html Kind regards, Martin JIRA Software
            Dennis Markwart made changes -
            Affects Version/s New: 7.0.10 Server [ 60553 ]

              Unassigned Unassigned
              e9e7322136cb Dennis Markwart
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: