Swimlanes with the new Epics and Features

Kevin Dickson
Contributor
July 25, 2023

Ever since renaming Epic to Feature, and creating a custom Epic field (to follow SAFe's hierarchy), I cannot base my swimlanes on Epics - only Features, Stories, etc).

Is there a way to show Epics still - even though it's now a custom Epic field?

I would like to be able to still base my swimlanes on Epics, with them expanding to Features, and then to Stories

5 answers

0 votes
Kevin Dickson
Contributor
July 27, 2023

Thanks Cassie,

Yes, we have Preium, and it does work there.
I think though, the team is still used to the old "standard" way of looking at things, so I will give them some coahing on advanced roadmaps.

Appreiciate your suggestion - will attempt that today

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 26, 2023

Hi @Kevin Dickson 

So you renamed the Epic issue type to Feature, no then there is no option the have swim lanes based on Epic, but on Feature.

The issue type Epic (default) is the only type with this functionality. 

The only option you would have is to base swim lanes on your based on queries. Then you are able to create a swim lane on:

e.g.

Epic = "value in custom field Epic"

Repeat this for each value you have

Kevin Dickson
Contributor
July 27, 2023

Thank you, Marc. I'll try this and revert.

Like Marc - Devoteam likes this
0 votes
Danut M _StonikByte_
Atlassian Partner
July 25, 2023

Hi @Kevin Dickson,

If you do SAFe, this article on our blog might be useful for you: How to track multi-team or scaled-agile projects (such as SAFe®) in Jira with Great Gadgets app

As you will see, with our Great Gadgets app you can track all the SAFe-specific metrics!

In addition, the app offers a Team Wallboard dashboard gadget that supports swim-lanes by Epic. Here is an example:

image.png

I hope this helps.

Thank you,

Danut Manda 

Kevin Dickson
Contributor
July 27, 2023

Thank, Danut - I'll check it out this morning and revert.

0 votes
Linh Pham_Ricksoft_Inc
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 25, 2023

Hi @Kevin Dickson 

You mentioned that you want to "base my swimlanes on Epics, with them expanding to Features, and then to Stories" , so if I understand it correctly, the intended hierarchy would be  Epic - Feature - Story - Subtask.

But since you renamed Epic to Feature, your "Feature" issue type is now the parent level and Epic at the story level, you can't group issues on the swimlanes under Epic - it will only show sub-tasks.

Kevin Dickson
Contributor
July 27, 2023

Thanks Linh

0 votes
Cassie the Jira Mechanic
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 25, 2023

@Kevin Dickson are you talking about the advance roadmaps? If not to achieve this you will have to upgrade to premium to get advance roadmaps. Then you can update your Hierarchy this way:

Step 1. Go to the Jira Admin Settings cog and click issues.
admin cog.JPG

Step 2. Click Hierarchy then tweak it to flow how you now want it. *this is a global change that affects the entire site and all its projects. I found this screen a little confusing when I first used it but read it top to bottom .. things bottom up roll into the things above.
**Oh, edited this to add that this additional level hierarchy will not show anywhere else but the tickets fields ( parent link is in use now in addition to epic link) and visually in Advance Roadmaps.**

Hope this helps!

hierarchy.JPG

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events