Hello community,
I have the ask to create a new issuetype that is at the same level as an Epic, thus an issuetype that cannot be a child of an Epic.
My JIRA instance is utilizing Portfolio so I went into the hierarchy and set it up as such (Epic level Name has Epic/ Team Effort/ Maintenance), since we utilize Parent Link and Epic Link to define the parent child relationships:
thought that would do the job but I have noticed that on boards (backlog view) you can grab a team Effort or a Mainteance issuetype and you can drag it under an Epic effectively making it a children of the Epic.
We want to avoid this behaviour and not allow a team effort or a Maintenance issue type to ever become a child of an Epic.
Any input on this would be appreciate :)
Thanks!
-Roberto
I don't think that it can be done out of the box, you can only have one Epic type in standard jira / portfolio jira.
If i remember correctly the plugin that adds this functionality is Structure: https://marketplace.atlassian.com/apps/34717/structure-project-management-at-scale?hosting=cloud&tab=overview
Have not worked with that myself though so cant say for sure.
I can confirm what Krister says here.
Also, don't rename Epic, it breaks some stuff in interesting ways. Structure can give you a load of layers that can help you out, but not quite issues that are Epic-like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.