Although I would expect the latter to be a pointer to the first, i can't see the Epics I have created through "Create Issue" in the pull down of the Epic/Theme field (Which can optionally be shown inside an issue in edit mode).
My current conclusion is that they are not the same thing, and that the similar name is just a confusion. I assume that the Epic/Theme field is more like a free label, and is not shown in the Issues table as an Epic created via "Create Issue".
Is my understanding correct? do we have here 2 different Epic entities with no correlation between them?
Please see:
I believe that will explain the correlation. If you feel that document could be better organized or more thorough, feel free to leave a comment on it.
I hope that helps.
Can't find anything on the topic of themes from the wiki. We are migrating our "ongoing" issues from a scrum board to kanban, and we are going to miss epics as a way to categorize loosely related issues. Should we stick to labels, or is there a Theme concept that could be used too? We don't really want to use "Components", because something as "resilience improvements" or "stabilizing tests" is hardly a component.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It generally just works "out of the box" (having enabled the GH scrum template to the project)
Some things to check
In JIRA (eg the Default display screen) custom field don't generally appear (even as a label) unless there is a value for that custom field which gets created via the issue edit screen or some other way like the GH cards entry
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.