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,298,792
Community Members
 
Community Events
165
Community Groups

Using SAFe Enablers

Hi everybody,

I was wondering if anyone out there has experience in using Enablers in Jira which has been set up for SAFe.

We have been using a Custom field on all levels so we know if it's an Epic or an Epic Enabler, a Capability or a Capability Enabler, a Feature or a Feature Enabler.

Maybe I don't really have a question but it's more looking for confirmation: You can't use issue types for this since you cannot configure this in the hierarchy structure of Portfolio for JIRA right? 

Interested to see what you all think.

Regards

4 comments

We tried the Plugin Jira Structure to implement it, and it works fine. Simply creating  a new Issue type named "Enabler" works also fine if you expect it to be at the "User Story" Level and not at the Epic Level

Regards

Sylvain

Like Jamstation likes this

Thanks for the answer! Sounds like a workable solution!

Hi Wessel, as Solution Partners we have implemented the same approach for various organizations but found that we needed to be able to propagate this flag to all children in that tree starting from Initiative all the way to the Story. For that we’ve developed an addon that will allow you to inherit any value from your parent issue down to the hierarchy automatically. You can then display it or report on it either in Structure or any other tool. From my experience implementing SAFe in Jira I wouldn’t recommend introducing a separate issue types Enabler Feature, Enabler Capability, Enabler Story etc as it clutters the setup quite a bit.  

Like Jason Ng likes this

Hi Irina,

Thanks a lot for this feed back

It's 2020 and SAFe 5.0 is out ... I too am wondering the best way to add Enablers to Epics.  Also how best to indicate whether an Enabler, Feature or nested Story is for Product, Architecture or Engineering (so we can filter them for each role).

Like # people like this

I have the same question,
I think we need to use same issue types; Epic for Enabler Epic, but add label "Enabler",
and do the same for story, then link any issue to the Enabler labelled issue,
What do you think?

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

233 views 1 4
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