switched from EPIC to FEATURE incl. the whole Look and

[Eric Roetenberg]

Hello

Are there any companies that have switched from EPIC to FEATURE incl. the whole Look and Feel. What should we keep in mind does everything still work as eg:

• Filters
• Automation Rules
• Dashboarding

Am curious about your experience and what was the reason to do this.

Grtz.  Eric

[Vishal Biyani]

@Eric Roetenberg 

As far as I remember, this change was brought in to align with SaFe hierarchy.

As long as you are not deleting Epic from your instance, you should be fine.

Any specific reason, why you are not using Epic at all. It can be placed above Feature and you may not need new issueType = Initiative

[Nikola Perisic]

Hello @Eric Roetenberg 

Not sure what do you mean by switching from EPIC to FEATURE? Are you using FEATURE issue type instead of an EPIC? There is an issue hierarchy that defines which issue types can be associated with the Epic level, which is level 1.

More: https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/

[Eric Roetenberg]

Hi Nicolai

see the attachment I want to move from Epic at level 1 to Feature
because the feature name with us is similar to that from ServiceNow

Grtz.. Eric

[Nikola Perisic]

From the first screenshot, I can see that it's fine, what is the actual issue?