Hello Atlassian community.
We have upgraded the Jira to 9.4.10 LTS version few weeks ago and customers noticed that when moving any issue type from one project to another, the moving screen defaults the ticket to a "story" issuetype in the new project disregarding the original value. In previous version means 8.20 when moving any issue type from one project to another, the moving screen defaults the ticket to the same issuetype like source project. Is it a bug or intended behaviour? How we can resolve that?
Best regards,
Ernest
Welcome to the Atlassian Community!
This will happen when the target project does not have the same issue type available.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you show us the two project issue-type schemes?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have upgraded to newer LTS hotfix version and it is working.
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.
I cannot replicate that behaviour without having two different issue type schemes set on the projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have upgraded to newer LTS hotfix version and it is working.
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.