Error occurred while storing issue - Error Message

[Alexandra King]

I am receiving the following error message when attempting to transition through ANY workflow in my projects "Error occurred while storing issue." Some of the transitions show more detailed errors such as "Error occurred while storing issue. It seems that you have tried to perform an illegal workflow operation."

Please advise. As a note, we upgraded to 8.20.2 in November. 

This error is severely impacting our work. Please advise. 

[Kristin Lyons]

Do you have any plugins installed or any workflow validators, post functions, or conditions?

[Alexandra King]

Hi, we determined the issue was due to one of ou newly updated applications "BigPicture."

We have resolved the issue. 

[Marc-Andre Weiss]

@Alexandra King @Anna-BigPicture 

We facing the same problem while updating Jira from 8.3.5 to 8.20.5. 

Could you pls explain how you resolved this? At the moment we deactivated this plugin to make sure our teams can work with jira.

Thx in advance. 

[Alexandra King]

We found that every time we update BigPicture/BigTemplate, we then have to go to the app directly and do a second update from there. We originally update from "manage apps," then go to the plug-in directly, and are required to do a secondary update. 

[Anna-BigPicture]

Hi @Alexandra King and @Marc-Andre Weiss

I am sorry for the inconvenience caused. Please be informed that we have already identified a bug, and our Dev Team is intensively working on the fix right now.

Please note that resolving this problem is our top priority. 

I will keep monitoring the fixing progress and update you when I have more precise data regarding the bugfix release date in this thread.

[Marc-Andre Weiss]

Hey, Anna,

we could fix the isse the same way Alexandra fixed it. So maybe your bug fix should be to trigger this 2nd update automaticly within the app update.

Anyway atm BigPicture is up and running for us.

thx.

[Anna-BigPicture]

Hi @Marc-Andre Weiss

Thank you for the update. I'm glad to hear that you resolved the issue. 

The good news is that the bug is already fixed, and it is now waiting for release.