Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Issues in hierarchy in Portfolio for JIRA are not linked automatically

Beat Burkhard
Beat Burkhard Jan 23, 2018

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.

Answer
Watch
Like Dale Wolfe likes this
500 views

0 answers

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced planning
TAGS
AUG Leaders

Atlassian Community Events

See all events