Hi Zoranner,
Sorry to hear that you are getting this particular error in Jira Software. We have seen these kinds of errors before a few different times. While some of these have been caused by bugs to Jira Software directly, (you can see a recent list of these in this JQL search on Jira.atlassian.com) it is also possible that these kinds of errors can be caused by unexpected failures in 3rd party plugins to Jira.
To help us better identify the specific cause of your error, please let us know:
Perhaps with this information we can better guide you towards a solution here.
Regards,
Andy
We are also getting this. JIRA Software 7.13.3. We are getting it on one board moving an issue either forward or backward in the workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gaven,
Thanks for the additional info here. Does the issue complete the transition when this error is generated? Or does the transition fail?
Usually when we see these kinds of errors, there is either a plugin in Jira or a custom field type that has some unexpected value(s) within it. I would be interested to try to learn more about your specific board here to try to recreate this problem so that we can try to pin down the exact cause.
I still have not yet found any other reports of this specific error being generated in any bug tickets, or other private support cases. So our knowledge on this specific error is still really limited.
Could you let me know what user plugins/add-ons you are using in your Jira 7.13.3? You can find if you are a system admin in Jira by going to the Cog Icon -> Manage Addons / Manage Apps.
I would also be interested to know what board settings you have here. You can find these as a board admin by going to the top right corner Board button -> Configure Board. Any custom fields added to the issue detail view? If you don't want to edit this existing board, you might try to just copy the board itself and then start adjusting the copy until the problem cannot be recreated. I have a suspicion that there might be a custom field that could cause this kind of error, but it is very difficult to determine exactly which field it might be from this error alone.
Please let us know the results.
Andy
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.