Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-17579

SLA disappears if the close cycle condition happens at the same time as the SLA stop meeting the "Apply to work items" condition

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • SLA
    • None

      Issue Summary

      If you have an SLA with a goal based on custom fields for the "Apply to work items" condition, and you modify this custom field while it matches the close cycle condition for the SLA, the SLA disappears from the ticket instead of showing the closed cycle value. This happens due to race conditions, as both actions occur simultaneously. Therefore, it's more common to see the SLA disappear in this scenario.

      Steps to Reproduce

      1. Have an SLA based on a custom field (for example, Labels)
      2. Have a "Finish counting time when..." condition to another status (for example, Waiting for customer)
      3. Transition the ticket to "Waiting for customer" at the same time you change the Labels field

      Expected Results

      The SLA should display the closed cycle in the ticket.

      Actual Results

      The SLA disappears.

      Video showing the behavior: SLA.mov

      Workaround

      It's not recommended to base SLAs on custom fields that are constantly changing. You should ensure the SLA is closed a few minutes before the custom field value is modified. If possible, consider adjusting this SLA logic.

        1. image-2025-09-09-11-05-33-712.png
          158 kB
          Giang Le
        2. SLA.mov
          13.76 MB
          Matheus

              Unassigned Unassigned
              mdossantos Matheus
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: