nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Linked stories not visible on Portfolio.

Neha Arora_3zp5bl

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'

Comments

Gonchik Tsymzhitov

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

Joseph Chung Yin

@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.

Paul O_qqk8km

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

advanced-roadmaps