Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
17
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
With the removal of the JIRA Classic Project Template when new projects are created a new Issue Type Scheme and Workflow is also created, instead of the project inheriting the Default Issue Type Scheme and Workflow for the instance.
This causes additional work for users who already have a Default Issue Type Scheme and Workflow implemented and want to use that for all new projects, as users will have to switch back to the Defaults after the project gets created (and delete the newly create Issue Type Scheme and Workflow if they don't want to use it).
When creating a new project JIRA should give users at least three different options as for the Issue Type scheme and Workflow for the new project:
- Inherit the Default Issue Type Scheme and Workflow.
- Give users the option to select an existing Issue Type and Workflow.
- Give users the option to create new Issue Type Schemes and Workflow.
This will reduce friction when creating new projects.
Attachments
Issue Links
- is duplicated by
-
CLOUD-7472 Creating new project also creates unneeded, unnecessary, UNWANTED schemes and workflows
- Closed
- relates to
-
JRACLOUD-39966 New Projects no Longer Inherit the Default Issue Type Scheme and Default Workflow
- Gathering Interest