Issues in hierarchy in Portfolio for JIRA are not linked automatically

We are using a SAFe-like setup in JIRA with the issues types:

Portfolio Epics -> Capability -> Feature or Epic -> Story

For issues of each issue type we use different JIRA projects. In Portfolio we have configured the Hierarchy in the same way:

Portfolio Epics -> Capability -> Feature or Epic -> Story

After configuring the JIRA projects to use in Portfolio I can see all issues, but they are not shown in a hierarchy (except issues with Epic/Story Link in same project). I configured the Parent Link manually for a couple of issues, and then the hierarchy is shown correctly. But doing this for all our issues manually would be a huge maintenance pain (we have a lot of issues). 

Am I missing something here? I was expecting that the hierarchy is constructed and maintained automatically based on the Portfolio Hierarchy Config. Any help is appreciated.

We are using JIRA Server 7.4.2 and Portfolio 2.5.

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Josh Frank
Posted Apr 04, 2018 in Portfolio for Jira

Factom: Portfolio for Jira case study

Recently, as part of a   series of Portfolio for Jira case studies, we spoke with Carl DiClementi, Director of Product Management at   Factom   about how he uses Portfolio for Jira. In...

270 views 5 4
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you