We have a customer that is entering issues with incorrect issue types (ie. a Bug when it should be a Question).
How do I change that issue type? It does not seem to be editable, regardless of my assignee status.
Hi Matt, Try moving the issue. You can choose to keep the project the same but change the issue type.
This documentation explains step by step how to move an issue: https://confluence.atlassian.com/display/JIRA/Moving+an+Issue
Ironically, this is one place where classic is simpler than next-gen. If configured correctly, classic allows a ticket's type to be changed with a simple pull down menu. @Alex, please get this fix on the roadmap for next-gen.
------------ Note --------
This is working now see subsequent comment
Hmm, I'm not sure exactly why, but it is now working for me as a simple pull down menu to change the issue type.
I suspect it might have to do with the fact that I included all of the same ticket fields across my different issue types. Either that, or something changed on the latest version of Jira Cloud.
First of all wish you a very happy new year!
IMO data from all fields (system as well as custom) remains intact as there is only 1 change happening that is the issue type is changing. in my project i moved a story to task and had data in 2 custom fields (when issuetype = story) which automatically got updated/made visible in the new issuetype = task....
The only catch here is, how have you created your custom field will decide whether the data shall be moved to new issuetype or not.
While creation of custom field, was it done for all possible issue types or you had selected only some issue types...e.g. you created a custom field 1 as an admin and while creation you set this field only for say 2 issue types i.e. story and bug. now you had created a story with data/value in custom field 1. If you move this story to bug, the data/value in custom field 1 will be automatically updated/made visible by ssytem in the new issuetype of bug. But in case you move story to say task, then system will not automatically move/udpate task with this custom field 1 data because this field itself is not associated or set for issue type = task.
Additionally, the workflow shall also matter. That is do all issuetype have same workflow (i.e. same set of status values), if YES, then movement will be automatically taken care but if not then movement may not be possible as there will be no relevant status for the new issue type.
in above e.g. Assume story and bug have status as open, WIP, test and Done..whereas say task has status as open , WIP and Done...lets say story had status as test and now you try to move it to task, system will not be able update the status automatically for this movement.
Hope it helps. in case you have more query, feel free to ask
Is it possible to change issue type using regular edit button when there are different workflows in the project? Scenario: issue is open on the screen, I click on the issue type name, I check the list => there is no issue type (different workflow). Is it just a bug or there is another reason why it is not working?
Hi all. I'm working with Jira Service Desk Cloud. I cannot find the "issue type" field in my "custom fields" screen.
I trying to enable this field in order to permit to change the issue type in the Edit screen using a combo box.
Ref: "You can also allow the issue type field on your edit screen this will allow you to change the issue type as long as it is not restricted by the field configuration." from @Timothy Harris.
thanks in advance.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events