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

As an administrator of a project, I need to be able to edit sprint contents as our velocity doesn't accurately represent the work that was done

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

      I've found times where sprints were started accidentally and we need to add stories to the sprint (as part of the commitment) and times where sprints were closed accidentally and we need to close stories before we completed the sprint because the work was done.

          Form Name

            [JSWSERVER-8831] As an administrator of a project, I need to be able to edit sprint contents as our velocity doesn't accurately represent the work that was done

            Hi Scott,

            Apologies for the confusion. When I said "where you want scope completed just after the sprint finish time to be considered as part of the sprint scope", I was assuming that the sprint has not yet been completed. If the sprint is closed, the dates cannot be changed.

            The linked story (allow reopening of sprints) would be the best way to address that.

            Michael Tokar added a comment - Hi Scott, Apologies for the confusion. When I said "where you want scope completed just after the sprint finish time to be considered as part of the sprint scope", I was assuming that the sprint has not yet been completed. If the sprint is closed, the dates cannot be changed. The linked story (allow reopening of sprints) would be the best way to address that.

            Hi Michael,
            I’m not following where you've provided a solution to the second scenario. While I know you can edit the start/end date and time while a sprint is open, how is it changed after the sprint has been completed? For example: A 2 week sprint is started on Monday, a day later someone accidentally completes the sprint. What are the steps to edit the end date, thereby “reopening” the sprint?

            Scott Wagner added a comment - Hi Michael, I’m not following where you've provided a solution to the second scenario. While I know you can edit the start/end date and time while a sprint is open, how is it changed after the sprint has been completed? For example: A 2 week sprint is started on Monday, a day later someone accidentally completes the sprint. What are the steps to edit the end date, thereby “reopening” the sprint?

            Hi snims,

            You outline two scenarios:

            • where you want scope added just after the sprint start to be considered as part of the original scope;
            • where you want scope completed just after the sprint finish time to be considered as part of the sprint scope

            In both of these cases, would it suffice to modify the sprint date/time to include those scope events? i.e. if you start the sprint, then 5 minutes later you add another issue, you could try setting the start date of the sprint to 5 minutes after so that the addition is now included.

            Let me know how you go with this.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Hi snims , You outline two scenarios: where you want scope added just after the sprint start to be considered as part of the original scope; where you want scope completed just after the sprint finish time to be considered as part of the sprint scope In both of these cases, would it suffice to modify the sprint date/time to include those scope events? i.e. if you start the sprint, then 5 minutes later you add another issue, you could try setting the start date of the sprint to 5 minutes after so that the addition is now included. Let me know how you go with this. Regards, JIRA Agile Team

              Unassigned Unassigned
              c9fab9d1-3846-4815-bb8d-fc7a7e31afeb Steve Nims (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: