Service Management SLA is not Paused but Rather Restarted

Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

When a user transitions an issue, sometimes, the SLA associated with the issue gets lost.

If the issue then enters a other statuses, it appears again however instead of pausing as it was configured, the SLA is restarted.

  • Create an SLA with a goal that contains a specific issue status.
  • Transition the issue to a status that triggers the SLA to start counting.
  • Transition the issue to the status that requires that the issue be paused.

It would be observed that the SLA would go missing and secondly, if the issue is transitioned back from the pause status, it would be observed that the issue was not paused and actually restarts when it enters the start status again.

Diagnosis

Diagnostic Steps

  • Access the SLA page for the project and check if the SLA link shows a red error next to the link and has the option to update/recalculate it?
  • Check the JQL specified in the SLA goal and ensure that it does not include the status were the SLA starts in itself.
    • This would usually result in the SLA disappearing when you transition it out of the expected status.

Cause

Cause 1

Jira requires a recalculation as something might have broken the SLA available.


Cause 2

Due to the SLA goal specifying the issue status, whenever you transition out of the status in question, the issue would be unable to meet the requirements for the SLA hence why it restarts each time.

Resolution

Cause 1

Trigger a recalculation by clicking on the update link so that Jira would fix any errors that may be causing the problem.

Cause 2

Review the Goal for the SLA and remove the issue status from it to ensure that the conditions would always be met.

    • This would also ensure the SLA does not disappear.





Last modified on Feb 5, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.