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

Rapid board burndown determiner

XMLWordPrintable

    • 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.

      According to https://answers.atlassian.com/questions/6569/how-do-you-burndown-story-points-in-greenhopper-on-a-daily-basis, Rapid board burn down is determined by the rightmost column on the rapid board, this should be change to be a configurable column specified by the user.

      The reason for this is that right most columns might include QA/testing activities, that do not effectively represent development burn down,
      resulting in skewed burn down charts.

            [JSWSERVER-5522] Rapid board burndown determiner

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3065141 ] New: JAC Suggestion Workflow 3 [ 3660659 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2622359 ] New: JAC Suggestion Workflow [ 3065141 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2321424 ] New: Confluence Workflow - Public Facing v4 [ 2622359 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040725 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2321424 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2029303 ] New: JIRA PM Feature Request Workflow v2 [ 2040725 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 734489 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2029303 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Michael Tokar made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 398152 ] New: JIRA PM Feature Request Workflow v2 [ 734489 ]
            Issue Type Original: Task [ 3 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Martin (Inactive) made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Michael Coulter created issue -

              Unassigned Unassigned
              f5c02c373c2f Michael Coulter
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: