-
Bug
-
Resolution: Won't Fix
-
Low
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Experienced Behavior:
After creating a project the Default Issue Type Scheme is not automatically updated to include issue types created during project creation.
- The Default Issue Type Scheme must include all issue types. These types not being included in the Default Issue Type Scheme causes errors when performing actions in JIRA
Expected Behavior:
All issue types are added to Default Issue Type Scheme when the issue types are added to JIRA. The description of this scheme indicates it should be automatically updated.
-
- "Default issue type scheme is the list of global issue types. All newly created issue types will automatically be added to this scheme."
Steps to Reproduce:
- Start with new JIRA 7 instance
- Install JIRA Software
- Notice two issue types (epic, story) are created automatically and appear in the Default Issue Type Scheme.
- Create new JIRA Software project
- Notice that new issue types have been created and a new issue type scheme has been created for that project. This new scheme contains the issue types defined in the project template.
- The default issue type scheme is not updated to include the issue types that were added during project creation.
Workaround:
- JIRA Server
Follow the instructions in this KB to add the issue types to the scheme
- JIRA Cloud
Open a support ticket at Atlassian Support to have those issue types added.
- causes
-
JRACLOUD-46227 Move issue error in JIRA software: 'The issue type selected is invalid'
- Closed
- is related to
-
JRACLOUD-70574 Issue types are missing from Default Issue Type Scheme
- Closed
-
JRASERVER-59866 Default Issue Type Scheme not updated when Issue types are added during project creation
- Closed