JIRA Boards/Tickets not being saved/synced

[Michael Cerantola]

We've been using JIRA cloud for almost 3 years now.

Recently, this last year, and a lot more often recently, we have issues where people are creating tickets, and they disappear - as if they aren't being saved to the cloud, or there is a long delay where things do not show up, and then 5 of the same tasks suddenly appear.

Often times, during a sprint, when I'm moving things across kanban boards, 5 seconds later, everything reverts to what it was.

We're only using a max license of 50 seats, and we checked our storage, everything is low.

Has anyone encountered this issue? It's almost as if individual accounts are doing things that ultimately overload JIRA and it stops syncing/saving progress.

Some of our project managers are a bit irritated today, saying they created tickets 4 times and they keep disappearing.

This is a new system for our IT team as well, so they cannot see anything odd on the admin side.

Has anyone had this occur, and any steps to help resolve it?

Thank you!

[Lucas Knorr]

@Michael Cerantola are you sure your issue is not related to issue security? Are you utilizing issue security schemes? Together with automation rules, which often run unknowingly in the background, this can lead to problems similar to those you have described. 

[Michael Cerantola]

Interesting. Thanks, Lucas. I am not sure we're using security schemes. I will follow up and take a look.

[Nikola Perisic]

Hello @Michael Cerantola 

That is a very strange behaviour. Two days ago there was an incident that involved users that had 'Too many requests' error appearing to them. That issue has been mitigated. All of the other sites are working normal? Just like Youtube or Google as example. I'd suggest that you report this to Atlassian support as they might need to take a look at the logs and see what was happening. Speaking of logs, did you by any chance were able to catch some errors in the development console?

[Michael Cerantola]

Thanks, Nikola. I'll ask our Jira Admin to put in a request ticket.

I'll check the development console (if you mean F12) next time it happens. I never thought of checking into it when it happened before...and definitely don't think some of the PMs with a lot less tech experience would think of that either.

[Nikola Perisic]

Yes the F12 one, more specifically the console itself and also the network tab to actually see what is the delay when creating the issues.