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

as a user I need to see the *remaining* story points in an epic

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

      Currently in JIRA to to see the remaining (not total) story points in an epic, you must create a custom filter, you can not simply pull down a chart to do it.

      Having this kind of roll up is very valuable to teams working epics.

      What doesn't work:

      1) Crete a new context based on Epic issue type: http://confluence.atlassian.com/display/GH/Using+Contexts+to+Filter+and+Highlight+Issues, this doesn't help because it just shows the total points, it doesn't show the time remaining on a per epic issue.

      2) use the task board: http://confluence.atlassian.com/display/GH/Working+with+Epics, that doesn't help either because again, it does not show the time remaining per epic.

      We need a way to see a chart that shows the time remaining per epic, not per version.

      The awkward work around; if you use a burndown chart with a custom filter for a specific epic name, then yes you can see the time remaining for that epic, but only for that epic...if your project hs several epics having to manually create this filter all the time (as new epics are created) is not practical.

      We need a way to see a chart that shows the time remaining per epic.

        1. manual_filter_on_burndown_chart.png
          46 kB
          Michael Garvin
        2. taskboard_epic_no_remaining_points_shown.png
          110 kB
          Michael Garvin

            [JSWSERVER-3938] as a user I need to see the *remaining* story points in an epic

            Thanks for your thoughts on this issue. With the upcoming release of the new Epic Burndown report, I feel that we can resolve this issue.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Thanks for your thoughts on this issue. With the upcoming release of the new Epic Burndown report , I feel that we can resolve this issue. Regards, JIRA Agile Team

            Bob Hunt added a comment -

            We have a need for this as well.
            We would like to conduct high-level planning at the Epic level and assign a Story Point 'budget' to each Epic (this would be a relatively high number).
            Then as we decompose the epics into Stories we could track how well we are doing against our budget.

            Bob Hunt added a comment - We have a need for this as well. We would like to conduct high-level planning at the Epic level and assign a Story Point 'budget' to each Epic (this would be a relatively high number). Then as we decompose the epics into Stories we could track how well we are doing against our budget.

            The Epic Report would be an okay temporary solution is I could turn some things off. It's got so much on it that it's just hard to look at, and too hard to explain if you're trying to use it to report to people outside the team. It would be so nice to have a simple burndown chart for epics. Stakeholders are used to seeing sprint burndown charts, so they are familiar and easy to understand.
            The Epic Report legend is somewhat confusing because it shows everything as areas, but some are just lines. And I wish I could hide non-working days. I also only need to see number of issues and number of unestimated issues in the summary, not on the graph (and that would help with the legend issue as well).

            Dominique Monie added a comment - The Epic Report would be an okay temporary solution is I could turn some things off. It's got so much on it that it's just hard to look at, and too hard to explain if you're trying to use it to report to people outside the team. It would be so nice to have a simple burndown chart for epics. Stakeholders are used to seeing sprint burndown charts, so they are familiar and easy to understand. The Epic Report legend is somewhat confusing because it shows everything as areas, but some are just lines. And I wish I could hide non-working days. I also only need to see number of issues and number of unestimated issues in the summary, not on the graph (and that would help with the legend issue as well).

            dmonie, do you think the Epic Report would work for you, as a temporary solution? It doesn't display the remaining Story Points, but it does show the completed vs. total value.

            Dobroslawa Wierzbicka (Inactive) added a comment - dmonie , do you think the Epic Report would work for you, as a temporary solution? It doesn't display the remaining Story Points, but it does show the completed vs. total value.

            An epic burndown chart would be great.

            Dominique Monie added a comment - An epic burndown chart would be great.

            Hello,

            We also have the need. We use issue links to manage a hierarchy of features refined in Epics that are refined in Stories. Stories are estimated in story points. In order to measure progress over time at feature and epic level (release view), we would like to have a way to get aggregate remaining story points by summing up story points of stories that are not done yet.

            Jira proposes it in the time tracking report http://confluence.atlassian.com/display/JIRA044/Time+Tracking+Report : if sub-tasks are enabled, the ∑ column at the right of the field shows the aggregate time tracking information for each 'parent' issue (i.e. the sum of the issue's own values plus those of its sub-tasks).

            Can we solve it by creating a new custom field ? Please advice.

            Thanks,
            Alain

            Alain Giraud added a comment - Hello, We also have the need. We use issue links to manage a hierarchy of features refined in Epics that are refined in Stories. Stories are estimated in story points. In order to measure progress over time at feature and epic level (release view), we would like to have a way to get aggregate remaining story points by summing up story points of stories that are not done yet. Jira proposes it in the time tracking report http://confluence.atlassian.com/display/JIRA044/Time+Tracking+Report : if sub-tasks are enabled, the ∑ column at the right of the field shows the aggregate time tracking information for each 'parent' issue (i.e. the sum of the issue's own values plus those of its sub-tasks). Can we solve it by creating a new custom field ? Please advice. Thanks, Alain

              Unassigned Unassigned
              bd66199eb4a8 Michael Garvin
              Votes:
              17 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: