Issues with Jira Ticket-Status updates and Resource Loading Errors

[Quentin J_ Gabriel]

Hey There

I am experiencing multiple issues with my Jira instance that I would like your assistance with. Below are the details of the problems I am encountering:

I am using MacOS Seqouia (15.0) with the current Safari Version.

Resource Loading Errors: I am receiving numerous 404 and 409 errors in the console when using Jira. The specific errors include:

• Failed to load resources with status 404 for various endpoints (e.g., jsm-cmdb-upsell-page-dismissed, customdomain, mypreferences).
• 409 status errors for endpoints such as start.
• Additionally, there are warnings regarding deprecated JavaScript functionalities.

This shows up in statuses that cannot be changed for tickets with the error message “The status could not be updated”. Check your network connection and then reload the process.

Troubleshooting Steps Taken:

• I have switched user-agent profiles in the developer tools to check if the issue persists.
• Verified if there are updates available for Jira; none were found.
• I updated npm globally using the command: sudo npm install -g npm.
• I cleared Cache and Cookies and restarted the process.
• I also checked for funding-related messages from npm, but no actionable issues were found.
  
  Using Chrome everything works fine.

Despite these efforts, the problems continue to persist. I would greatly appreciate your guidance on resolving these issues.

Thank you for your assistance!

Best regards,

Quentin

https://ad20it.atlassian.net/browse/IS-5921

[Jakub Jablonski · Accepted solution]

I see the same problem in macOS 14.7 and Safari 18.0.

For me it helped to enable the feature flag in Safari called "requestIdleCallback" in DOM part (Safari -> Settings -> Feature Flags).

[iKaakkola]

Same problem, same versions and enabling this feature flag indeed fixes the issue.

https://caniuse.com/requestidlecallback  - Jira / Atlassian products shouldn't probably rely on it (yet) though..

[Quentin J_ Gabriel]

That worked, thanks a lot!

[Dan Breyen]

Hi @Quentin J_ Gabriel welcome to the community! From a troubleshooting perspective, have you tried Chrome on your Mac?  Also, are there any other PCs (Mac or Windows) you could try to see if you have the same issues?  Do you have any other users in your instance?  Do they experience the same issues?  

Sequoia is brand new, is this a new Mac?  Do you have someone that might have a Mac that is still running Sonoma?  Wondering if the same issues happen there.

Also, is there another location that you've tried from a different network?  Even trying a coffee shop with a VPN?  

Just trying to narrow down the cause.  I haven't updated to Sequoia yet to try it w/ Jira.

Hope that helps.

[Quentin J_ Gabriel]

Hey Dan, thank you for the answer.

Sadly I've tried kind of all of that.

I've worked without any problems on the same Mac with the same OS with the same browser 2 weeks ago. Then Ive got a break of 1 week, came back and had this problem.
Yeah, like I shortly mentioned above, in Chrome is no problem, it seems like it is between jira and safari where jira made a change to get here.

(Due to the normal functionality of Jira in Chrome, I beliefe there is no issue in the network nor my Mac)

I hope the information are helpful :)