Can create Initiatives and added them to hierarchy above Epics but can't add as Parents to Epics

[Robbie Fergusson]

Hello,

Initiatives are created and added to the Hierarchy above Epics, and Parent Link/Parent field are visible on my Epics. But i can't select any Initiatives as the Parent. Any idea why or how?

Organisation is using Jira Premium

[Rune Rasmussen]

Have you also added your Initiative work type to the Work type scheme(s)?

https://YOUR-SITE.atlassian.net/jira/settings/issues/issue-type-schemes

[Robbie Fergusson]

Yes, just checked - Initiatives are there in Work Items / Types

[Bevan Williams]

Hi @Robbie Fergusson

If I understand your request correctly, you should have the following in place:

• Hierarchy level "Initiative" added to work item hierarchy ✅
• Work Item "Initiative" exists and has been added to the specified level in the hierarchy ✅
• Initiative is a valid work item for the spaces in which they can be created 

If the parent and child are not in the same Space then:

• Users need at least view permissions (Browse Projects) for the parent space and edit permissions in the child space.
• All spaces involved in the relationship must be company managed.

The permission one trips folks up most of the time - a quick check would be to use the Permission Helper in General Settings. I'm assuming you have admin privileges, but if not, this is where they should look.

Edit: I just remembered you may also need to check which account groups have been added to Plans Global Permissions. To add a parent, they'll need the "Plans User" permission. 

[Robbie Fergusson]

Thank you! I've got this to work. 

If i also wanted to use High Level Initiatives, is it as easy as adding them as a JIRA work type?

Robbie 

[Rune Rasmussen]

@Robbie Fergusson If your High Level Initiatives will be comprised of (parent of) multiple Initiatives, then yes.

But depending on the specifics of your situation, the higher up your work type hierarchy you move you may be better off using either Goals from Atlassian Home or Jira Product Discovery.

[Bevan Williams]

@Robbie Fergusson that's great to hear.

I agree 100% with @Rune Rasmussen You absolutely can continue to extend your hierarchy upwards tooling-wise.

To help decide, I usually look at how organisations track their cash.

• Most organisations fund outputs via programmes/projects/initiatives. Reporting and the data needed for it (captured in Jira) would follow this. If this is true at your org, then I would recommend using a work item.
• If, however, the High Level Initiative being funded is more of an outcome or ambition, then I would use Goals.

By keeping it separate, you can leverage not only the Atlassian toolset, but also the adaptability that comes from separating the problem (outcome) from the solution (output).