[JSWCLOUD-16819] When the issue type 'Epic' is renames, the labels and options related to 'Epics' should be matched with the new name. - Create and track feature requests for Atlassian products.

UIS:
3
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

There are few places in JIRA where the word 'Epic' seems to be hard coded, such as:

In board page, click on more menu, you'll see the options Show/Hide epics panel and/or Show/Hide epic labels
In backlog > 'Epic' panel you could see EPICS, Create epic, Create issue in epic and Issues without epics options.
The system fields Epic Name and Epic Link in issues screens.

Currently even if we rename the issue type Epic, these options and labels persist having the word 'Epic'.

There are few places in JIRA where the word 'Epic' seems to be hard coded, such as:

In board page, click on more menu, you'll see the options Show/Hide epics panel and/or Show/Hide epic labels
In backlog > 'Epic' panel you could see EPICS, Create epic, Create issue in epic and Issues without epics options.
The system fields Epic Name and Epic Link in issues screens.

Currently even if we rename the issue type Epic, these options and labels persist having the word 'Epic'.

When the issue type 'Epic' is renames, the labels and options related to 'Epics' should be matched with the new name.