Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

is it possible to recalculate the SLA after changing its definition even on closed tasks?

Emilia KASPRZYK
Contributor
March 20, 2025

Hi

is it possible to recalculate the SLA after changing its definition even on closed tasks?

 

Kind regards, Emilia

 

3 answers

1 accepted

9 votes
Answer accepted
Tuncay Senturk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 20, 2025

Hi @Emilia KASPRZYK 

In JSM, you can automate recalculation with Automation, see this article. Other than that SLA calculations are event-driven, meaning that when you update an SLA definition, only new events like issue updates, transitions will trigger the new rules. Existing issues retain their SLA even if closed. 

 

Emilia KASPRZYK
Contributor
March 20, 2025

Hi, thank you very much. 
Rule created but i've made something wrong got 401 error. I'll ask jira support maybe they can help me.


Like Tuncay Senturk likes this
1 vote
Iryna Menzheha_SaaSJet
Atlassian Partner
March 20, 2025 edited

Hi @Emilia KASPRZYK 

In Jira, the ability to recalculate SLAs after changing their definition depends on the tool you’re using. If you consider using other add-ons, option to recalculate SLAs even for closed tasks, can be Time Metrics Tracker (developed by my team)

With Time Metrics Tracker, you can:
✔️ Recalculate historical data based on updated SLA rules, including closed issues.
✔️ Customize your SLA definitions and apply them retroactively.
✔️ Get detailed reports on how SLAs have been met or breached, even after updates.

image.png

TBS2@2x.jpg

Would you like to see how it works? I’d be happy to provide more details!

Hope this helps!

1 vote
Ayça Erdem_OBSS_
Atlassian Partner
March 20, 2025

 Hi Emilia,

Great question! Jira doesn’t automatically recalculate SLA metrics for past issues when you change the SLA definition, but with Timepiece - Time in Status for Jira developed by my team at OBSS, you can still generate historical reports based on your updated criteria.

Our app allows you to analyze SLA-related metrics, including Time to Resolution and Time to First Response, even for closed tasks. Since Timepiece calculates reports dynamically, you can retrieve past data regardless of SLA rule changes and get insights based on your updated definitions.

Here you can see how to  filter your result

resolutiontimefilter.png

 

resolutiontime.png

If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace.

Hope it helps

Ayça

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, atlassian community, journeys for jira service management, journeys for jsm, eap jsm atlassian, early access program atlassian, early access program journeys atlassian, early access program journeys jira service management, join atlassian eap

Join the Early Access Program (EAP) - Journeys for Jira Service Management 🚪

Journeys is a brand new feature in Jira Service Management that helps you streamline various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding that require action from different teams. ✨

Join the EAP →
AUG Leaders

Atlassian Community Events