I am looking for the documentation that explains how Issues in Epic is supposed to behave. In particular, in 6.1.7 when looking at an Epic it shows issues whose Epic field contains the Epic but not those whose Epic/Theme field contains it. Can it be configured to show both sets of issues? Where is the behavior specified?
I think you can find a bit more information here. However, there's not much about it since the concept is quite simple. Issues in Epic is similar to Sub-tasks in Issue, and that's it.
Regarding Epic/Theme, in the previous link you can see that it only applies to the Classic Boards, which is no longer supported. Hence, it can be said that this field is now a mere Label field.
Those issues with an Epic Link pointing to the name of an Epic will be included in the "Issues in Epic" section of that Epic. For example:
Basically, Epic Link of a standard issue is linked to Epic Name of an Epic. Epic/Theme is of type Label hence has nothing to do here. You can read more about this at JIRA Agile Custom Fields.
Thanks. Is this documented anywhere that I can show the user who asked me the question? The link you provided does not mention "Issues in Epic". Also, what is the mental model for using Epic/Theme? How does it fit in an Agile process? Is it just unstructured labels for cross referencing?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs