-
Suggestion
-
Resolution: Duplicate
-
None
Hello Team,
We need the following feature improvement in Jira cloud.
- Ability to create different issue type *names *for epics (in my use case issue name Epic does not make sense and would prefer using different relevant name for Epic issue type)
- Ability to define multiple epic types (like we can create multiple Base and
subtask types for a Jira Software instance) - Remove the current behaviour that the system fixates on the word
"epic" as an issue types name, but to rather use the TYPE value of an issue
type to determine whether it is an epic, base or subtask.
Thanks
- duplicates
-
JRACLOUD-80492 Add the ability to create multiple Epic issue type in JIRA Software
- Closed
-
JSWCLOUD-16819 When the issue type 'Epic' is renames, the labels and options related to 'Epics' should be matched with the new name.
- Closed
Ability to use different issue type name for Epic
-
Suggestion
-
Resolution: Duplicate
-
None
Hello Team,
We need the following feature improvement in Jira cloud.
- Ability to create different issue type *names *for epics (in my use case issue name Epic does not make sense and would prefer using different relevant name for Epic issue type)
- Ability to define multiple epic types (like we can create multiple Base and
subtask types for a Jira Software instance) - Remove the current behaviour that the system fixates on the word
"epic" as an issue types name, but to rather use the TYPE value of an issue
type to determine whether it is an epic, base or subtask.
Thanks
- duplicates
-
JRACLOUD-80492 Add the ability to create multiple Epic issue type in JIRA Software
- Closed
-
JSWCLOUD-16819 When the issue type 'Epic' is renames, the labels and options related to 'Epics' should be matched with the new name.
- Closed