[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'.

When the issue type 'Epic' is renames, these labels should automatically match the new name.

is duplicated by

JRACLOUD-77533 Ability to use different issue type name for Epic

relates to

JRACLOUD-80492 Add the ability to create multiple Epic issue type in JIRA Software

mentioned in: Page Failed to load; Page Failed to load; Page Failed to load; Page Loading...

(1 mentioned in)

Form Name

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'.