How do I remove an Epic child issue from 1 of 2 parent initiatives to which is has been associated

[James (Jim) Halpenny]

How do I remove an Epic child issue from 1 of 2 parent initiatives to which is has been associated

I have an Epic that shows incorrectly (at least in this instance) as a child issue of 2 different Initiatives at the same time.

I want to delete association of the Epic child issue from one of its parent initiatives.

I cannot find a way to do that either on the parent Init OR from the child Epic.

When I google, I've seen some potential-ish answers pointing toward Advanced roadmap.  I don't think i have access to that.  We are using Big Picture.

This dual association is messing up the Big Picture view.  It shows the child Epic under only the 1 or 2 parent Initis--& it's the wrong one. :(

Appreciate any answer or direction elsewhere.

Thanks!

Jim

[Chris K]

Hi @James (Jim) Halpenny,

From the scenario you described, I have a clue what may be the problem here.

Are you able to view the field(s) which link from the epic to the initiatives? It may be possible that there are different fields used in your instance. The default field should be the field "Parent Link". There it should only be possible to select one parent issue. That's why it is strange that you get two parents for one child issue...

But there is also the field "linked issues", where you can choose between different links between issues, like "relates to", "child of", "parent of". Maybe this field is also used in your instance.

For the right display of the Parent-Child hierarchy, you should check the configuration of Big Picture. You can configure the field, which you want to use for the hierarchy in Big Picture via Tasks -> Task structure, as shown in this community question: https://community.atlassian.com/t5/Jira-Software-questions/BigPicture-How-to-Set-Display-Order-by-Hierarchy/qaq-p/1375815

My guess is, that there are more than two fields configured and used in your instance. If you don't have access to this configuration, you can ask your admin to check it.

As I mentioned above, I am not a 100 percent sure, if this is the solution for your problem, but it may be a first direction for troubleshooting :) Maybe someone from the community can add some more hints and insights ;)

Greetings Chris

[Chris K]

Welcome to the Atlassian Community btw 🎉