We've created an issue type "Initiative" and added it to our Jira Hierarchy above Epic. Our planners wanted an issue type "workstream" between the Initaive and Epic. Unfortunately, we can no longer associate Epics directly to initiatives without having a associated workstream. How can we address?
Hello @Michael Ballenger
That is expected behavior.
You cannot skip levels when you are wanting a parent/child relationship between issues.
If you want the Workstream issue in between the Epic and Initiative issues, then Epics can be made children only of Workstreams, and only Workstreams can be made children of Initiatives.
The only alternative you have is to create a generic link between the Epic and the Initiative, but Jira will not recognize that as a parent/child relationship.
That is kind of what I feared. But it is what it is. Thank you for your prompt response.
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.