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

As a product owner, I need to fix estimates which break Burndown and other reports

XMLWordPrintable

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

      We had to add an issue to our sprint. The person entering the issue mistyped and put "45" in the estimate field, meaning minutes but the system was set to default to days. This caused our burndown report to show a spike of 9 weeks scope change for the ongoing sprint, which completely flattened the useful part of the graph to a slim line at the bottom.

      You can revise the estimate but the large spike still flattens the graph. We need a supported mechanism which can be used by product owners (ie not SQL experts) to edit or remove the history of a bad estimate change to restore the graph.

      Mistypes happen. To have a sprint completely and utterly broken with invalid/unreadable results by a single mistype is not reasonable or expected behavior.

            [JSWSERVER-8439] As a product owner, I need to fix estimates which break Burndown and other reports

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069314 ] New: JAC Suggestion Workflow 3 [ 3659294 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626379 ] New: JAC Suggestion Workflow [ 3069314 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2323997 ] New: Confluence Workflow - Public Facing v4 [ 2626379 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044536 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323997 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032776 ] New: JIRA PM Feature Request Workflow v2 [ 2044536 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736650 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032776 ]
            jonah (Inactive) made changes -
            Description Original: We had to add an issue to our sprint. The person entering the issue mistyped and put "45" in the estimate field, meaning minutes but the system was set to default to days. This caused our burndown report to show a spike of 9 weeks scope change for the ongoing sprint, which completely flattened the useful part of the graph to a slim line at the bottom.

            You can revise the estimate but the large spike still flattens the graph. We need a supported mechanism which can be used by product owners (ie not SQL experts) to edit or remove the history of a bad estimate change to restore the graph.

            Mistypes happen. To have a sprint completely and utterly broken with invalid/unreadable results by a single mistype is not reasonable or expected behavior.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSWCLOUD-8439].
              {panel}

            We had to add an issue to our sprint. The person entering the issue mistyped and put "45" in the estimate field, meaning minutes but the system was set to default to days. This caused our burndown report to show a spike of 9 weeks scope change for the ongoing sprint, which completely flattened the useful part of the graph to a slim line at the bottom.

            You can revise the estimate but the large spike still flattens the graph. We need a supported mechanism which can be used by product owners (ie not SQL experts) to edit or remove the history of a bad estimate change to restore the graph.

            Mistypes happen. To have a sprint completely and utterly broken with invalid/unreadable results by a single mistype is not reasonable or expected behavior.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSWCLOUD-8439 [ JSWCLOUD-8439 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 525409 ] New: JIRA PM Feature Request Workflow v2 [ 736650 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

              Unassigned Unassigned
              8372cf0e6631 Jo Rhett
              Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: