It seems to be a little better @Tanguy Crusson It was intermittent yesterday. Just slow to respond to clicks etc. At first I thought it was my home internet playing up. That was until I saw this thread. I'll continue to monitor it today.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 5, 2024 edited
Hi everyone, we've been working on this for the past couple of days and found the root cause for this behaviour. Ironically, it was linked to a new library we're using to track UI performance metrics across Jira đ¤¨
Today's update:
Most of JPD should be back to normal now
With the exception of the status field which may still play up and now we're focusing on that. The screen may still hang a bit when you try to update its value
While investigating all this we identified areas where we can improve performance further (the app gets re-rendered fully on some operations instead of changing just a part of the screen). We will fix that.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 5, 2024 edited
Peter: would you mind doing a screen recording (e.g. Loom) and sending it to tcrusson@atlassian.com? (please make sure you refresh your screen first so the changes come into effect). Thanks!
Atlassian Team members are employees working across the company in a wide variety of roles.
December 5, 2024 edited
Quick update: it looks like I spoke too fast and the deployment wasn't yet complete for all the changes. My apologies! đ By tomorrow it should be fully rolled out đ
In the meantime, if you're facing slow performance and it's blocking you, please raise a support ticket and we can investigate and see what we can do on your site.
In Jira product discovery
left sidebar > give feedback
select "get help from the support team"
paste the following:
"Tanguy Crusson from the JPD team asked me to create this support ticket so the team can investigate a performance problem we're facing in the tool today - he told me they'd need access to our site to figure out what the problem is. The team is working on this in the Slack channel #hot-113571"
32 comments