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

Allow Velocity Chart to use the Start/Complete date of reopened Sprint

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Sprint
    • None
    • 1
    • 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.

      Problem Definition

      Currently, Velocity Chart's Commitment estimate is taken from the total estimate of the issue which was added to Sprint prior to the Sprint was started.

      In Jira 7.1.0, we added the ability to reopen Sprint. However, in some scenario when the Sprint is reopened, Sprint start date is edited to an earlier date, the Velocity Chart still does not include the issue's story point as part of the Commitment estimate even though the estimate/issue was added before the Sprint was started with the new date value.

      Steps to reproduce

      1. Ensure that there are at least 7 completed Sprints in Scrum board.
      2. Add an issue to a Sprint.
      3. Start the Sprint.
      4. Create a new issue and add an estimate.
      5. Move the to the new Sprint.
      6. Complete the Sprint and check Velocity Chart. The second issue's estimate will not be counted for the Sprint's commitment estimate.
      7. Reopen the Sprint.
      8. Edit the Sprint's start date to an earlier date than the date when the estimate/issue was added to the Sprint.
      9. Complete the Sprint.

      Suggested Solution

      Allow Velocity Chart to use the Start/Complete date of reopened Sprint. This way when user view Velocity Chart, the report will include all the commitment/completed estimate based on the new start/complete dates of the Sprint.

      Workaround

      Ensure that the issue/estimate was added before the Sprint was initially started.

            [JSWSERVER-20136] Allow Velocity Chart to use the Start/Complete date of reopened Sprint

            DOTS Team added a comment -

            Hello, 

            After we migrated the Jira database from Oracle to Postgres, all the commitment time becomes 0 and unfortunately, we cant modify the start/end time of the sprints,  so please try to bix this bug, and it will be helpful 

            DOTS Team added a comment - Hello,  After we migrated the Jira database from Oracle to Postgres, all the commitment time becomes 0 and unfortunately, we cant modify the start/end time of the sprints,  so please try to bix this bug, and it will be helpful 

            andi.kay added a comment -

            This comment is in agreement with Kevin Morton's request for Project Admin to adjust for errors and issues.

            andi.kay added a comment - This comment is in agreement with Kevin Morton's request for Project Admin to adjust for errors and issues.

            Shilpa Narkhede added a comment -

            HI,

            We are facing this issue with 0 velocity for our project "PR-4728 Payments Project (PRPP)" since last couple of sprints!

            We need correct velocity chart values for the project review meetings

             

            Thanks,

            Shilpa

            Shilpa Narkhede added a comment - HI, We are facing this issue with 0 velocity for our project "PR-4728 Payments Project (PRPP)" since last couple of sprints! We need correct velocity chart values for the project review meetings   Thanks, Shilpa

              Unassigned Unassigned
              vshanmugam Vicknesh Shanmugam (Inactive)
              Votes:
              16 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: