I would like to have two Epics related to each other. For example, I have a HTML Epic and a Dev Epic. I need to track both. Is it best to track separately or add Relates in Linked Issues.
I am open to suggestions regarding this question.
Dave
Hi David - Welcome to the Atlassian Community!
How many issues do you expect to have for each different Epic? Is one Epic dependent at all of the other Epic?
If you are just looking for grouping, more or less, I agree with Jack that a single Epic with components attached to each underlying issue would probably serve you better.
you can certainly link the two but that doesn't do anything from a relationship perspective, i.e. like Epic > Story relationships. If the two 'epics' are actually associated w/ the same initiative then I would consider having a single initiative epic and then use Components to illustrate HTML and Dev. But hard to say what is best w/o really understanding your environment, requirements, etc.
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.