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

MVR: Make the burndown chart understand when an issue was added/removed from Sprint (i.e understand scope change)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 5.9.7
    • 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.

      • Should handle change of Story Points value

      https://extranet.atlassian.com/display/GHDEV/Estimation+and+Tracking+in+the+Rapid+Board#EstimationandTrackingintheRapidBoard-Tracking

      • The graph begins at the start time of the Sprint, it logically ends on the specified end date of the Sprint (which is marked on the graph) but continues until the time the Sprint was actually closed
      • Allow the Sprint to be specified but default to currently active Sprint
      • The start value of the graph does not compensate for changes after the start of the sprint to the value
      • Items burn down as they reach the done column
      • Items that are added to the Sprint after its beginning are shown as scope change
      • Items that are removed from the Sprint after its beginning are shown as scope change
      • Items that have their estimate changed after the beginning of the Sprint are shown as scope change
      • Scope changes (i.e anything other than a burndown) are shown with some sort of visual signal and information on hovering the inflection point

              Unassigned Unassigned
              sclowes Shaun Clowes (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: