Summary

The customer is seeking SAFe 5.0 compliance when it comes to terminology related to the Objective's Category options.

In essence, Jira Align uses the following non-compliant terminology:

References

• Lean Agile Guru : SAFe 5.0 (January 2, 2020)
• Scaled Agile Framework: PI Objectives

How to Replicate

1. Create or edit an Objective, then scroll down and locate the Category dropdown
2. Notice the listed options are:
   • Critical Path
   • Stretch Goal
3. Browse to the Platform Settings page, click Dropdowns tab
4. Notice there's no option to customize Objectives' Category options
5. Browse to Platform Terminology page
6. Notice there's no option to customize Objectives' Category options

Instance Details

• Any instance/release

Investigation Done

• Checked Help Center articles (linked to this ticket) and confirmed there's no option to customize Objectives' Category options
• Checked Public Ideation Portal and found an old, currently shelved Idea, requesting this very same enhancement:
  • iZone 942 - Align with SAFE 5.0 Framework and have Objectives categorized as Committed and Uncommitted
    

Please Help With

Implementing an enhancement request to the Dropdown tab (under Platform Settings); or to the Platform Terminology page would be feasible to allow customers to customize these Objectives' Category names.

The customer's point of view is valid and there's an increasing user community within their enterprise that would benefit from that possibility, seeking that for a long time. That would also clearly increase the user's experience with this product.

Customer's own words:

(...) I anticipated some of this is rigid hard coded into the tool.
(...) I will say between allowing more flexibility into some rigid areas or allowing more custom fields than just a few per work object, it would unlock more innovation and less prescription to our end users/architects, etc.
(...) I'm aware this is a product (Agilecraft) Atlassian purchased and is conforming, if I compare to your already succinct Atlassian culture, the ability to customize fields, etc. in Jira is less rigid than this tool, I hope to see your Atlassian culture enhance and create more flexibility to enable us, and other customers to expand your portfolio of adoption as I would see that to be more marketable.