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

Release planning chart

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • 5.6
    • 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.

      We use Jira/GH and competitive tool in parallel so I see the release planning tools amongst the biggest missing parts in GH.
      The reports/charts in GH are based on historical data, but no estimates are made based on the velocity and backlog change pace. For example it would be nice to be able to have a rough prediction of a possible release date that is based on the remaining story points in the backlog + average changes calculated based on historical data and the velocity of the team. These projections would make it easier to keep track of the project and plan further releases.
      Basically when you fix release date you need to plan what stories could be included and if you take into account only two dimensions - velocity and CURRENT backlog content you produce wrong estimate. Of course it won't work for release 1.0 but already 1.1 could be planned with quite reasonable accuracy.
      Would it be possible to add such chart?

            [JSWSERVER-592] Release planning chart

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3068600 ] New: JAC Suggestion Workflow 3 [ 3662940 ]
            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 [ 2626549 ] New: JAC Suggestion Workflow [ 3068600 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327777 ] New: Confluence Workflow - Public Facing v4 [ 2626549 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044626 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327777 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032877 ] New: JIRA PM Feature Request Workflow v2 [ 2044626 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 739153 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032877 ]
            Martin (Inactive) made changes -
            Backlog Order (Obsolete) Original: 128050000000
            Workflow Original: GreenHopper Kanban Workflow v2 [ 301309 ] New: JIRA PM Feature Request Workflow v2 [ 739153 ]
            Assignee Original: Nicholas Muldoon [Atlassian] [ nmuldoon ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Shaun Clowes (Inactive) made changes -
            Remote Link New: This issue links to "Wiki Page (Extranet)" [ 25829 ]
            Stuart Bargon [Atlassian] made changes -
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

              Unassigned Unassigned
              53d487effe4b Dmitry Kvasnevsky
              Votes:
              18 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: