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

As a user, I would like the time estimates of new issues added during the middle of a sprint to be reflected as a spike in the burndown chart.

XMLWordPrintable

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

      Sometimes during the course of a sprint, there are new tasks that need to be added that were not known during sprint planning. When we create new issues to represent these tasks, we assign a time estimate (under the "original time estimate" field). The problem is that the chart board then reflects it as if this estimate was known at the beginning of the sprint. What we would like to see if a spike in the chart. The time estimate should be applied based on the date that the issue was created.

      This is important in having a true representation of the burndown. It's valuable to see how the burndown is affected by new tasks arising mid-sprint.

      The only known workaround for us is to enter an original estimate of "1 minute", and then set the appropriate "remaining estimate" as the actual time estimate. But this isn't intuitive...

            [JSWSERVER-1726] As a user, I would like the time estimates of new issues added during the middle of a sprint to be reflected as a spike in the burndown chart.

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069406 ] New: JAC Suggestion Workflow 3 [ 3662945 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Component/s Original: ↓ Obsolete -- ChartBoard (Classic) [ 12966 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626569 ] New: JAC Suggestion Workflow [ 3069406 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327796 ] New: Confluence Workflow - Public Facing v4 [ 2626569 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044646 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327796 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032900 ] New: JIRA PM Feature Request Workflow v2 [ 2044646 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 738744 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032900 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Backlog Order (Obsolete) Original: 1610000000
            Workflow Original: GreenHopper Kanban Workflow v2 [ 302657 ] New: JIRA PM Feature Request Workflow v2 [ 738744 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Shaun Clowes (Inactive) made changes -
            Fix Version/s New: 6.0 [ 27108 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

              Unassigned Unassigned
              989d1b8add2f Kevin MacClay
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: