System: Jira DataCenter 8.22
For most of our projects, I have issue types which share the same workflow, screen scheme & field configuration, and I can change the issue type in the detail screen. On one project, the issue types have the same screens, workflow and field configuration, yet I can't change the issue type in the detail screen. What am I missing?
Configure the Screen you are using to add the "Issue Type" field to the Screen.
Does the project you are trying to edit the issue type in using an "edit" screen that includes the issue type?
If it is not that, then you will need to closely check that the workflow scheme and field configuration scheme are the same for the issue types you want to swap between.
It's not just having "schemes that are the same", you need the issue types to be using the exact same shared objects (so the same workflow and same field config scheme. Screens, less so, they just need to be showing a minimum of the mandatory fields)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Adding to OP.
I have the similar situation: I have several issue types using the exact same workflow, issue screen, etc. There is no screen required on Edit. None of the options above are an issue.
I have move permission for the project and can convert other issue types by selecting the issue type icon and selecting the new issue type.
For some of the issue types in the same schemes, etc., I can convert using the icon, but at least one issue type I cannot convert using the icon (Bug).
What would cause one issue type of several to behave differently this way?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My issue was solved here. Apparently only this issue type uses a different screen that didn't have the issue type field for some reason:
https://community.atlassian.com/t5/Jira-questions/Cannot-edit-this-issue-type-in-this-project/qaq-p/1138619
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @George Turnbull
I would suggest to double-check the scheme, if that is really being shared, are you part of the projects, have create issue and move issue permission.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a Move Issues permission in the permission scheme that may need to be configured.
Move Issues
Ability to move issues between projects or between workflows of the same project (if applicable). Note the user can only move issues to a project he or she has the create permission for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.