Hi all, I can see there's an ability to create issues that sit above the Epics in advanced roadmaps (which I've done)
What I'm confused about is the mapping upwards. To create a "theme" ticket type I've had to create it as a "Base" level ticket - can I create is as a second Epic type so it displays like epics or can I only have a single epic type ticket?
How do I ensure correct linking up? I've seen that there are some changes around epic-link and parent-link: What do I need to do with that to ensure the hierarchy of Theme>Epic>Story>Task>Sub-task persists and works?
Hi @Erin Davies and welcome to the community!
When it comes down to it, Epics are special and there's no way to replicate their behavior even with those higher hierarchy issue types like Theme in your case.
As for linking...
Hi Mark,
Thanks for replying. Unfortunately this now leaves me with a problem of managing cross-team portfolios using themes. I've tried using Structure for this but it still leaves me without an easily understandable view of the work
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you please provide more detail around "a problem of managing cross-team portfolios using themes"? For example, here are a couple tips for how I manage above the Epic:
These are just some ways that you can make it easier to manage the program level issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.