How do I make an Epic a child of a new issue type?

[Georgia Harlow]

We just purchased the premium jira so we could use advanced roadmaps.  I created a new issue type "Initiative" but can't figure out how to link Epics as children under the new type so that they will display in the plans.  Thanks in advance for your help!

[Josh Frank · Accepted solution]

@Georgia Harlow We also created this short video on how to configure issue hierarchy here: https://community.atlassian.com/t5/Advanced-Roadmaps-articles/3-short-videos-to-help-you-get-started-with-Advanced-Roadmaps/ba-p/1439078

[Sramanth Pandeti · Accepted solution]

Hi @Georgia Harlow Weclome to the Atlassian Community!

You can link Epics to your initiatives using the "parent link" field. You need to configure the field on your screens if it is not already available. 

[Georgia Harlow]

Thanks!  I'll try that.

[Georgia Harlow]

This solved my issue!  I had followed the training but this step was missing!

[Joseph Chung Yin]

@Georgia Harlow - Exposing the "Parent Link" field in your issue screen in Jira is not the recommended way to associated your EPICs to Initiatives as one will need to know exactly the Initiative issue key to use.  This is a work-around.

The proper way to conduct the association is via the Plan.

If you choose to conduct it in the Jira project issue screens, you will need to create a separate screen scheme for EPIC issue type only, because if it is applied to screen schemes for other non-EPIC issue types, then it will give you problems downstream.

Best, Joseph

[Georgia Harlow]

I went to the plan and couldn't find a way to add the Epic as a child.  I could create a new one but not associate an existing.

[Joseph Chung Yin]

@Georgia Harlow ; @Sramanth Pandeti - Here at our company, we use both exposing the Parent column in the plan + Mr. Pandeti's suggestions.

The reason why we use both methods was because for some users that they can remain in Jira without the need to access the AR plan to created the rollup to Initiative issues.  Therefore, it will show up in the plan automatically.

Best, Joseph

[Joseph Chung Yin]

@Georgia Harlow - Forgot to mention that the fields that you need to expose in your plan is named "Parent" and not "Parent Link".. Once you expose the field in your plan, then you can associate your EPICs with Initiative.

Best, Joseph

[Georgia Harlow]

That field is not displayed by default in the plan.  You have to add it in order for it to show the parent link.

[Joseph Chung Yin]

@Georgia Harlow - Did you exposed the Parent column in your plan?  Or is your current plan's issue source included the project that contained the "Initatives"?

Best, Joseph

[Georgia Harlow]

If that's the best practice, it should be set up to have Parent visible by default.  This piece of information was not clear in the training.

[Joseph Chung Yin]

Yes, you are correct in AR.  It has to been done manually (we are using Jira DC On-Prems), so don't know if it is different versus Jira Cloud.

It is the same with adding "Parent Link" to the Jira project's issue screens.  It is also a manual process.

Best, Joseph

[Joseph Chung Yin]

@Georgia Harlow - Make sure that you already configured the hierarchy configuration that Initiative issue type is a parent of Epic.  To access the configuration (you will need to be a Jira System Admin) > access "Manage Apps" > access "Hierarchy configuration" option associated with AR for Jira.  

    

  

The Hierarchy must be setup first for the "Parent Link" column to work in your plan.

Best, Joseph Chung Yin

Jira Functional Lead, Global Infrastructure Apps Team

Viasat Inc.