Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Linked stories not visible on Portfolio.

We are following two types of hierarchy our Project board - 

A. Initiative --> Epic --> Linked stories and 

B. Initiative --> Epics --> Issue 

When i create a Protfolio, I am only able to see only those stories which are following the hierarchy - A (i.e. Initiative --> Epics --> Issue) but not B. (i.e. Initiative --> Epic --> Linked stories). 

Can someone please help me understand what do i have to do so that i can see both type of linkages in Portfolio/Roadmap ? Really appreciate a response. 

Linking we are using is - 'Implemented by'

3 answers

0 votes

Hm, as I see into my test instance you can't see it :( 

@Neha Arora -

In AR currently, it doesn't support linked issues in the plan scope view.  In our company, we also uses ALM Structure for Jira to supplement the AR plan's lack of this functionality.  We uses Structure to display the entire AR plan's issues (including linked issues).

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Put simply:

A. Initiative --> Epic --> Linked stories   is NOT a hierarchy 

B. Initiative --> Epic --> Issues IN EPIC is a hierarchy

 

An issue linked to another issue is just that - regardless of whether the link is called 'blocked by', 'parent of', or 'duplicate of'.  It's best thinking of link types as labels, and a link as a flat relationship rather than a hierarchical one.

An issue that is the parent of another issue is a different beast: the parent is the sum of the children and from a planning perspective you may consider it the sum of the effort or time. The children are the elements that make up the parent and are intrinsic to the parent. 

You can include non-hierarchical relationships in your plan. (I usually do) and you can work with them on via the dependencies view rather than the planning view because that's what they are : plan dependencies

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....

1,716 views 12 18
Read article

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