Hi @Kirill ,
There could be different reasons for this error. Did you try to reproduce the error and check the server logs in parallel. You can narrow down the issue with the logs
Here is a KB that is related to 500 error responses and one of the causes described here may be the root cause for your issue as well. But pls check the logs first
Which Jira version are you using exactly? There has been a bug a while ago which described this behaviour in case the permissions are not sufficient for the executing user after the move took place.
As this only affected older versions this might or might not apply - I'll be happy to look for the specific bug but the info about your current version would be helpful.
OK, no in that case it is not related to an old bug - it was applicable to a later Jira version 7 only.
In your case I'd recommend checking log files for further signs of errors - this message must be caused by something specific.
If you have the chance to test out of office hours, then putting Jira to safe mode where all Apps are disabled, is a handy way to determine if this error is cause by an App (which could be a realistic the case!).
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events