What is going on with all of the System impacts?

Question

Is it just us or is everyone else being impacted by all of these changes that Atlassian is doing in the Cloud? I feel like we are constantly getting performance issues (Automation failures due to issues communicating to Assets, spinning wheel, miscellaneous pop up errors, etc.)

How are these changes they are making not properly tested in the Sandbox more thoroughly? It is becoming difficult to keep up with the noreply@statuspage.io emails that keep coming in and then wondering if every time we do something on the Admin side of things, if it will actually work.

I miss the ability to control things better with the Jira Server/Data Center option as we had much less system impact since we could control the changes better.

Arkadiusz Wroblewski · Answer

@Alan Bruce

Yep it’s not just you. If you’re sitting in Admin/Automation/Assets all day, you’re basically the first one to feel every little Cloud wobble.

What’s going on is pretty simple (and a bit frustrating):

Cloud is always moving. Atlassian ships changes continuously and rolls them out in waves. Most weeks it’s fine, but when something slips, we get the spinning wheels, random pop-ups, weird UI behavior, or automations failing for “no good reason”.

Sandbox isn’t a perfect mirror. It helps test our configs/rules, but it won’t always catch platform-side issues or rollout quirks (feature flags, staged rollouts, etc.).

Automation + Assets is a classic pain combo. If Assets has a hiccup, Automation often looks broken even though your rule logic is fine.

How I keep my sanity with it:

When something fails, I check the status/incident timing first before spending hours blaming the rule.

I try to build automation assuming “cloudy days happen” (smaller rules, less chaining, fewer massive bursts, good audit logging).

If we’ve got Premium/Enterprise, I push for using whatever release control / change predictability we can get.

And I filter the status emails, otherwise you live in noreply@statuspage.io hell.

And yeah… I totally get the Server/DC point. With Cloud you lose the “we control the change window” feeling, and when Atlassian sneezes, admins catch the cold.

Alan Bruce · Answer

I already do that. Most of the time the assignee has no idea what to do with it as the issue is intermittent (might be an error looking up an asset, but then works when you do a refresh. Might be an Automation error (unable to connect to cmdb), etc.).

I am just saying that this is happening with a much higher frequency than even 6 months ago. I know I would be called out if our system had this many impacts in such a short time.

Joseph Chung Yin · Answer

@Alan Bruce -

I would recommend you to contact Atlassian Support Team (support.atlassian.com) to obtain further explanation on the recent issues you have facing.

Hope this helps.

Best, Joseph Chung Yin