When JIRA create a issue, this issue don´t let change issue type, JIRA ask move issue.
How can I change issue type whitout JIRA ask to move data?
Welcome to the Atlassian Community!
Yes, the issue type is not a simple field, it's an integral definition of what the issue might be, and determines how it works.
Unless the configuration of two types is identical, Jira has to change things when you move from one type to another, and the "move" functionality is the only process that has been written to do all the checks and ask the users to change what needs to be changed (and warn them of data loss)
To change issue type, you need to make sure both issue types are configured identically, or you have to use "move"
Rigth, Nic, but the e-mail request type, is a generical request for after reclassify. So all time change request type for every ticket is a rework.
Do you Know some solution to this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, stop trying to change issue type arbitrarily and set up the system so that it creates the right one. In other words, re-evaluate why you're allowing people to set up the "wrong" thing.
Help by email is not of a lot of use nowadays, because it requires someone to understand what they're asking for. When you have probelsm with people emailing the wrong place, you should a) sort out why they're emailing the wrong place and b) give them a better route than email.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community. I agreed with @Nic Brough -Adaptavist- stated. Issue Type is not a custom field. One will need to use the "Move" operation to change an issue's Issue Type.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks a lot for everybody, finally I choice the automation for resolve this condicion; so, the JIRA show me coution about risk select this option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I could help you out, I stumbled to this problem as well.
To make it easier, I created a custom field + automation
Custom field
Single list will all the issue types
- Issue type A
- Issue type B
- Etc
Automation
Trigger: when issue gets updated
If: custom field matches issue type A
Action: edit issue type
re-fetch issue data
edit request type
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Um, this does not change the issue type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It does, literally works for me. Check automation edit issue type
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It doesn't when they are configured differently.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
like what differently...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you not read the warning message you get when you try to create this automation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.