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

Improve How JIRA Agile Handle Closed Ticket in a Future Sprint

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • 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.

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

      The current Behaviour of a Scrum Sprint JIRA Agile for Closed ticket right now is:

      • when a ticket included in a future sprint and get closed before the sprint is started, it would be still included when the Sprint Master started the sprint then it shows up in the Plan Mode.
      • if a ticket is closed while a sprint is currently running, the issue key of the ticket will be having a strike through and the ticket still shown in the Plan Mode, including the closed ticket above.

      Actually, there is no need to include a ticket that have been closed to a future sprint as it does not need to be worked anymore and the Sprint Master should know about it. But, since the issue will be gone in the Plan Mode if it is closed before Sprint is started, it could be hard to know that there is actually a closed ticket in the sprint. Hence, a notification or a simple behaviour to handle the closed ticket in a future sprint could be useful like:

      • A warning notification that will be pop-up before starting a sprint telling that a closed ticket is inside.
      • the closed ticket is removed from the sprint and the backlog.
      • to still shows closed ticket same as the behaviour of a closed ticket in a running sprint.

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: