You're reading one of the top pains on Atlassian Marketplace — a free sample of the catalog. Create a free account to browse all Shopify & Atlassian pains and the basic Chrome catalog.
Jira admins face slow performance and bugs in SLA Time and Report app
.19
Demand — how loud & how many (score)
Willing to payImplicit
Momentum (7d)▼ 2.1%
Cluster18 posts · 17 people
MarketplaceAtlassian Marketplace
UpdatedSep 12, 2026
The story
The pain
We're Jira admins trying to manage SLAs, but the SLA Time and Report app is riddled with performance and reliability issues. The permissions page loads very slowly, the app slows down after saving changes, and custom field creation triggers mass update notifications to thousands of tickets. These bugs make configuration and daily management frustrating and inefficient.
Evidence
What people said · 18 complaints, 17 people
When I click on the "Permissions" option, the page takes a significant amount of time to load. The loading time is much longer than expected, which makes it difficult to access and manage the permissions efficiently.
Slow After Saving SLAs - If you make major changes to your SLA such as creating a custom field the app slows down to where you can't make any other changes for a while. You will have to let those changes take affect and then come back later to continue configuring.
The other problem is that when the system creates those custom fields, it adds those fields to every ticket in the project and then updates them. This generates an update notification for every ticket in the project including resolved ones. We have about 29k tickets in our Help Desk queue, so people were literally getting thousands of update emails.
A lot of problems with this app right from the get go. I couldn't delete the "demo" SLA which was created; it kept saying it was in used. That same mechanism wouldn't let me create a new SLA. I had to clone that SLA (which worked somehow), delete the original and then reconfigure the new one. Also, the reports page kept hanging up with either the demo SLA or the new one running.
Symptom:: We are using the SLA Time and Report for Jira Cloud app and have configured the Custom Fields option for our SLA configuration. However, the configured custom field is not being populated/updated with the expected SLA information, even though the SLA itself is calculating correctly.
Export the pain — problem, evidence and market signals — as Markdown, PDF or JSON. The Markdown export ships with a built-in briefing you can hand straight to a developer or an AI agent.