Jira - Feature vs Epic

[Amanda Armstrong]

In Jira, the parent of a story is called an EPIC.

In Jira Align, the parent of a story is called a Feature.

Will there ever be alignment across the 2 platforms?

[Robert Wen_Cprime_]

Hello @Amanda Armstrong ! Welcome to the Atlassian community!

The discrepancy between Jira and Jira Align can come down to the Scaled Agile Framework (SAFe).  Back in the early history of Jira Align, it was a company and product called AgileCraft that created a way of tying Jira and other tools used by teams and integrated them for higher levels that incorporated teams of teams (seen in SAFe as Agile Release Trains).

The Agile Release Trains would work in higher level work items called Features that were made up of Stories.  In the event that Jira Align/AgileCraft needed to tie into Jira, Features were mapped to the issue type that is above Stories (Epics).

At some point in the future, Jira will allow Epics to be renamed so there will be alignment.  But for now on Jira Align and other apps that are around to work with SAFe, there's a mapping between SAFe Features and Jira Epics.

[Davis Gleaton]

Just onboarding our Team to Jira Align - the terminology difference between Core JIra (Epics) and Jira Align Features and (Portfolio) Epics is so confusing.  It is hard to believe that as a software company this would continue as a foundational issue and should be resolved.

[Lavetta Stevenson]

I totally agree with you @Davis Gleaton  - if it doesn't directly reduce sales - it isn't a priority is all I can gather from this huge gap in product terminology.  There is always help in another upgrade or a different product.  Good News - Atlassian got it right in Jira Align.    Happy Holidays!