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

Associate a Story to more than one Epic

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.

      As stated in GHS-7652, in our company Epics stand for big features. So for now we use an Epic for each sub-feature and using labels for associating it to a main feature.
      Sometimes - working on main releases and branches - it occurs that a Story affects more than one sub-feature. But for now it is not possible to actually associate that Story to more than one Epics (via Epic Link).
      (It was possible doing that with the "old" Epic/Theme labels though.)

            [JSWSERVER-7654] Associate a Story to more than one Epic

            Michael Tokar added a comment -

            Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time.

            Regards,
            JIRA Agile team

            Michael Tokar added a comment - Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time. Regards, JIRA Agile team

            TSO Logic Admin added a comment -

            FYI... as an alternative, consider the Behave for Jira Plugin (paid), which makes your outside-in specification (in particular "features") orthogonal to the implementation-tracking issues, i.e., the Epics, Stories, etc.

            Hope that helps!
            -Johnny

            TSO Logic Admin added a comment - FYI... as an alternative, consider the Behave for Jira Plugin (paid), which makes your outside-in specification (in particular "features") orthogonal to the implementation-tracking issues, i.e., the Epics, Stories, etc. Hope that helps! -Johnny

            Dmitry Kozlov added a comment -

            Hi carloth,

            You may want to consider to vote for [GHS-6768] to introduce THEME support in addition to EPIC. Themes seem very close to what you need based on your requirements, as they have many-to-many relationship with other items.

            As descibed in my comment, the epic contains sub-items (i.e. hierarchical), while theme may span may items including epics and stories.

            Though I may be wrong about your use case, then this sounds like "depends on" relationship between stories, not an Epic-Story relationship.

            P.S.: your vote for GHS-6768 will still be highly appreciated
            P.P.S.: if you find it making sense ))

            Dmitry Kozlov added a comment - Hi carloth , You may want to consider to vote for [GHS-6768] to introduce THEME support in addition to EPIC. Themes seem very close to what you need based on your requirements, as they have many-to-many relationship with other items. As descibed in my comment , the epic contains sub-items (i.e. hierarchical), while theme may span may items including epics and stories. Though I may be wrong about your use case, then this sounds like "depends on" relationship between stories, not an Epic-Story relationship. P.S.: your vote for GHS-6768 will still be highly appreciated P.P.S.: if you find it making sense ))

            Carsten A. added a comment -

            Maybe it is "easily" done by changing the EpicLinkCFType from (just) IssueImpl to Set<IssueImpl>?  (Note the quotemarks at "easily". I know all to well that it's not accomplished that easily.)

            Carsten A. added a comment - Maybe it is "easily" done by changing the EpicLinkCFType from (just) IssueImpl to Set<IssueImpl> ?   (Note the quotemarks at "easily". I know all to well that it's not accomplished that easily.)

              Unassigned Unassigned
              8d3097c4be8d Carsten A.
              Votes:
              14 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: