You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In one of my clients, there is a setup in Jira where they have crated the SAFe structure as follows:
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.
- 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?
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
>>> Story (Any other standard issues type the rolls up to an Epic, i.e I am assuming your Feature issue type).
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
Unfortunately no, you will need to display the stories to see the dependencies link visually.
Im trying to execute a similar architecture. I see this thread is over a year old. Is there currently a way to create, and then visualize this with Advanced Roadmaps?
3) User Stories (these could be across multiple dev teams)
I need to display quarterly plans at the epic level across all Features, then increment plans across all teams at the feature level then manage sprint activities on the actual dev teams.
I need to maintain the linking tasks->stories->features->epics