Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,373
Community Members
 
Community Events
176
Community Groups

Using custom hierarchy in Advanced roadmaps

In one of my clients, there is a setup in Jira where they have crated the SAFe structure as follows:

  • Jira Epic - SAFe Epic
  • Custom issue type Feature - SAFe Feature
  • Jira Story - SAFe Story

Feature are linked to Epics using Epic link. Stories are linked to Features using a custom issue link "implements" / "Implemented by". 

Then there can be blocks/blocked by -links between features or stories. 

Can

- Advanced Roadmaps handle this Feature between Jira Epics and Jira Stories or does it always assume that Jira Stories are always linked directly to Jira Epics

- If we would have a blocking relationship between two Stories belonging to two different Features, would Advanced Roadmaps then show that dependency also at Feature level (if it at all supports this structure). 

We are already using Jira Structure to show the hierarchies so that is not an issue, the question is that does Advanced Roadmaps support this kind of setup?

1 answer

1 accepted

4 votes
Answer accepted

@Vesa Purho -

Welcome to the community.

In AR for Jira plan, it currently cannot process issues source that have issue links (i.e. Stories linked to Feature).  It has to be what is defined in your issue hierarchy configuration - by default is the standard setup of 

Epic 

>>> Story (Any other standard issues type the rolls up to an Epic, i.e I am assuming your Feature issue type).

>>>> Subtasks

In your case with AR for Jira plan, you may need to have your story also roll up to EPIC via Epic link just like your Feature issue type.  Or create subtask associate to your Feature issue instead of have story issues.

Yes, Structure for Jira can handle your current setup, but it cannot be done in AR for Jira plan.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Thanks Joseph, so this option is out for visualising the dependencies. In the standard setup, if there are blocks-links between stories belonging to two different Epics, does the AR show then a visual link also between the Epics when the stories are not shown?

Unfortunately no, you will need to display the stories to see the dependencies link visually.

Best, Joseph

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events