Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,295,475
Community Members
 
Community Events
165
Community Groups

Linking Epics to higher level hierarchies

Hi All.

I wanted to start using Advanced Roadmaps for a project I inherited.

Using temporary full admin permissions I no longer have, I created Initiative and Theme issue types for the project scheme. Like this;

Hierarchy.png

Theres a lot of extras in this scheme that I dont want to use, my objectives for this project are to have a hierarchy like;

Theme
Initiative
Epic
Story / Task

I can give Initiatives a parent Theme;

Assign Initiative Parent.png

However, I cannot give Epics an Initiatives parents, or any parent really...;

Assign Epic Parent.png

 

What am I doing wrong here?

2 answers

Hi,

There is an answer here: https://community.atlassian.com/t5/Jira-Software-questions/Adding-a-Parent-Link-to-an-EPIC-issue/qaq-p/1466608

Basically you will have to add "Parent link" field to your EPIC issue type screen. Then you will set up INITIATIVE as parent to EPIC. Last step will be to configure roadmap hierarchy under: Plans->Administration->Hierarchy configuration

When completed you will be able to set up parent issue to EPIC's on roadmap plan.

roadmap.PNG

You're right about the use of the Parent link. It must be done so that Jira knows that Initiative to link the Epic to.

Like # people like this

Thank you Tomasz and Ric both. Through checking your advice, I think I'd found my problem. A strange issue type that exists in between Epic and Initiative, that I cant skip, even though that strange issue type is not available in my project...

So I'd already performed that step of adding a Parent Link field, but it still wouldnt let me connect an epic to an initiative;

image.png

So when I click the down chevron, I see a list of issues of a type that was created in a trial performed by another team I have no contact with;

image.png

and I cant skip that issue type in the hierarchy even though it is not part of my project.... argh....

image.png

So the existence of this "Requirement(Jama)" issue type somewhere in my large organization, which is not even in use by my project, is preventing me from using advanced roadmaps in a way I want to.

Does anyone know of any way to get around this without breaking what the other team are doing with this issue type??

 

Thank you!

If I recall correctly, I had to include a filter, in my list of Issue sources, that includes the list of Initiatives and Themes I want my epics linked to.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

298 views 0 9
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you