We recently updated our Jira Core and Jira Service Management implementation to v8.19.0/4.19.0. After the update, we found we were no longer able to move Issues that had any Participants.
Our workaround while we wait for guidance from Atlassian Support is to:
Has anyone else encountered this defect?
Atlassian is aware of the issue - it's logged here. It looks like it'll be fixed when 8.19.1 is released.
Thanks @Kian Stack Mumo Systems ! That's exactly what I was looking to find yesterday but searches turned up nothing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Gabriel Points !
Ohh... sounds very strange...
How does this manifest itself in the system? Any windows with errors? Logs?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Got info from @Kian Stack Mumo Systems link, thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Alexander Bondarev ,
What happens is once you select your Move destination and click next, you end up on the generic, "Sorry, we had some technical problems during your last operation" page with the error details.
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.