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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
If you have experience in using the SAFe framework, you will have noticed that the terms used in Jira and SAFe do not match up, even though they are essentially describing the same concepts.
Someone on your team (definitely not you…) may have tried to change the Jira software native fields to better match with your company’s SAFe workflow and discovered, well, that doesn’t quite work. Scan the Atlassian community threads and there are several companies bemoaning their failed attempts to change the name of fields in Jira agile with near catastrophic results. The risks of changing a field name in Jira are multiple and this is why custom fields used by Jira Software are locked for any modifications for Jira Admins. Every such field has the description “Used by Jira Software, do not remove or modify”, and this notification is not for fun!
Risks of changing a field name include causing:
Basically, if you change the name of the field there is no way for other plugins which are using the API connections to locate this field properly. It’s the same as removing a relation or a link between the plugins and the field. Because it is so hard to keep track of which plugins are using relation by name and what consequences it will lead to, your teams cannot manage or work around this.
The cPrime team is always striving to provide the easiest and most effective way for our clients to use Jira. As such, we’ve developed a new plugin using an Atlassian approved approach to safely translate fields from the Jira Admin UI to match with the SAFe terminology for a seamless approach to task management. The E2F translator for Jira ensures fields are matched properly so all reports and functions of Jira continue to work properly. We have a number of large scale clients safely using our plugin on instances with 10,000+ users already!
Here are some examples in action:
#1 – Defining your enterprise hierarchy of work items: If you’re not using cPrime’s SAFe epic to feature translator, there may be some confusion among teams about the status of work as work items don’t carry across easily from SAFe planning into the Jira board. However, using this plugin organizations can “standardize” a work item hierarchy which makes data consistent and easier to trace.
#2 – Tracking the status of features:
“Visualize the query being translated from Epic to Feature Issue Type”
Seamlessly transfer your SAFe workflow into Jira? Now we’re speaking the same language! To get your free 30 trial simply visit the Atlassian Marketplace and see for yourself how easy it is to translate your SAFe requirements into Jira.
Michele Lim [cPrime]
Product Marketing Manager
1 accepted answer