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

Epics should use parent-child-grandchild structure as opposed to utilising a label

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.1
    • 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.

      Atlassian Status as of 12 March 2012

      We understand that the use of labels for Epics is not adequate to model the relationships between items in an Agile backlog.

      We have worked with the JIRA team to implement performant issue links. We can now use this form of issue relationship instead of labels.

      At this stage, we have not integrated this specific functionality in GreenHopper, though it can be used. In the future we will use it to model Epics (and more generally the breakdown of higher level stories in to smaller ones) in the GreenHopper Rapid Board.

              Unassigned Unassigned
              nmuldoon Nicholas Muldoon [Atlassian]
              Votes:
              145 Vote for this issue
              Watchers:
              101 Start watching this issue

                Created:
                Updated:
                Resolved: