Jira Cloud Performance Improvements

[#1]

Hello everyone,

I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extremely important to us is the performance of our products and we are making some of the biggest performance improvement investments in the history of Atlassian. I am happy to share that this has resulted in good progress in the last 6 months. Most used experiences in Jira Software Cloud are now faster by around 30%. Hopefully, you’ve seen;

• Classic board and backlog loads are faster by 30% and 25% respectively thanks to a lighter front-end, single-page app(SPA) framework, and improvements on the side navigation bar

• New Issue View performance improved by 15% driven by several front-end initiatives

• Searching issues is now faster by 32% driven by javascript optimizations and backend call reduction

• Creating issues became faster by 38% thanks to SPA and pre-fetching resources

• Moving issues on the classic backlog are faster by 60% driven by UI improvements

• Next-gen board and backlog loads became faster by 31% and 36% respectively

(*All performance improvements mentioned above are in terms of ‘time to interactive’ at the 90th percentile)

We are committed to making Atlassian Cloud faster and are continuing to fire on all cylinders to make this happen. I look forward to sharing further progress on performance soon.

You can help by letting us know if there are other views or actions outside of those listed above, that are particularly important to you. Or by just providing any other specific feedback or impressions of Jira Software Cloud performance.

Cheers,
Tejasvita

[Bill Wanjohi]

Thank you! Now keep going! We love fast page loads!

[Taranjeet Singh]

It is really great to see this great initiative and progress towards Jira Cloud Performance improvements.

[Lee Irwin]

We logged a call with yourselves under ticket JST-626722 relating to performance issues, and have been advised that these issues are not going to be fixed until Q3/Q4. Despite the above its still extremely slow.

We were advised to speak to Xpand-it and they have advised that the issue is with yourselves and they have received same response from your team, Q3/Q4 fixes...

[Stuart Capel - London]

Now you mention it Jira does feel faster! Good work - keep it up :)

[Valerie Palmer]

Thank you for the update and making things faster.

[Lee Irwin]

We're still no nearer to resolving the Jira Cloud issues we are experiencing. No one seems to be acknowledging my comments regarding the performance issues we are facing as an organisation. It would be really beneficial if someone looked at the Javascript issues affecting load times. Fixes to be investigated in Q3/4 isn't making Jira Cloud a very attractive proposition. We've also had logged calls with X-Pandit that have advised that the architecture is the main issue and they are powerless to resolve what is an Atlassian issue. 

Any feedback as to why this is taking so long to resolve would be really beneficial. 

[Tejasvita Madan]

Hi Lee,

Apologies for the delayed response.

I want to assure you we recognize reducing javascript as an opportunity and are actively working on it. In fact, some of the improvements mentioned above were achieved by reducing javascript and CSS and making the front-end lighter.

Regarding the support ticket JST-626722, all experiences you are facing performance issues with are being actively tracked for performance improvement. I would also encourage you to try out the recommendations provided by the support team. Thank you! 

[Lee Irwin]

Many thanks for your response. 

We have already been advised these issues are not going to be fixed until late Q3/4 and your comments seem to mirror this. The tracking that has been completed shows how slow Cloud is over Server, an average of almost 13 seconds to load a story (Xpand-it then loads after this) compared to 1-2 seconds on server is really problematic when working to deadlines. 

We were advised of the following:

Try not to use so many attachments related to testing, such as Wireframes, Test plans, screenshots for evidence. - these are all things that we require to do our daily tasks

Unlink stories, test plans, test sets - again this is essential for reporting and completing tasks 

Change servers from Frankfurt to Ireland - data migration could be an issue with this though.

Open a ticket with Xpand-it - we completed this and they advised of the Atalssian JS issues being the source of the problem. We managed to speed up X-Ray loading times by a few seconds (once loaded we were able to complete testing with ease) but when switching back to Cloud it slowed us down again. They then referred us back to your support team. 

Following all of this, we were sent a link to the road map and this ticket advising of Q3/4 fix. Overall, it's been quite a frustrating experience.  

[Are Tysnes]

I want to give +1 to Lee Erwin's ticket and concerns regarding performance in Jira Cloud. We are using Xray plugin but the UI is so ridiculous slow that it affects our productivity. I urge Atlassian to address this as soon as possible. Q3/Q4 fix is not acceptable.

[Dave Liao]

@Tejasvita Madan - Tejasvita, thank you for quantifying Jira's performance improvements and sharing them with us! Alongside with managing our expectations for the new issue view in Jira, app performance is just as important. 💪

[Shyam]

@Tejasvita Madan  : We have received complaints from our engineering teams about Jira being super slow and requires page refresh multiple times.

[Gonchik Tsymzhitov]

@Tejasvita Madan  Thank you for the wrap up. 

Are you planning to share some technical solution ?:) 

[G subramanyam]

Thank you @Tejasvita Madan the new performance fixes seems working and glad to read your post.

[Lee Irwin]

Hi all, 

We've now been forced into using the new view of Jira Cloud. This has now made it virtually unusable, staff are complaining of severe slow down to the point of giving up using it altogether. 

Please can you advise as to what we are supposed to do? 

Many thanks 

Lee