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

Ability to view and prioritise epics in the backlog

XMLWordPrintable

    • 22
    • 4
    • Hide
      Atlassian Update – 13 July 2018

      Hi everyone,

      Thanks for your interest in this issue.
      This request is considered a potential addition to our longer-term roadmap.

      We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server

      You can learn more about our approach to highly voted server suggestions here.

      To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 13 July 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • 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.

      Original summary: GreenHopper misuses the concepts of "epics" and "themes"
      –

      An epic is a placeholder for a collection of user stories that will eventually be defined (this has to happen before they're added to a sprint). Epics can be prioritized in the Product Backlog, along with all the other Product Backlog Items.

      A theme is a coherent set of user stories – Often the resulting user stories from an epic. You can't prioritize a theme per se, because its Product Backlog Items may not necessarily be in a consecutive order.

      GreenHopper is mixing the two concepts, leading to the following issues:

      1. You can't prioritize an epic (the issue type) in the Product Backlog. They don't even show up in the Product Backlog.
      2. The "epic" functionality is in some aspects confusing and cumbersome, because it mainly deals with themes, while also assuming that epic = theme. One consequence is having a redundant "Epic Status" field that users must somehow keep in sync with the "Status" field.
      3. You get a separate pseudo backlog for "epics", which allows you to prioritize them. This doesn't mean anything in Scrum.

      Older versions of JIRA/GreenHopper used to get these two things right, albeit with an interface that wasn't as helpful as the new Rapid Boards: Themes were a type of label and epics could be prioritized.

              Unassigned Unassigned
              6a1a35216459 Gustavo Narea
              Votes:
              232 Vote for this issue
              Watchers:
              132 Start watching this issue

                Created:
                Updated: