SLA starts/breach if the SLA pause status is first in the workflow

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Medium
    • Component/s: SLA
    • 3
    • Severity 3 - Minor

      Problem

      SLA starts running or is breached(depening on the elapsed time) if the SLA pause status is first in the workflow

      Steps to Reproduce

      1. Create a SLA with below conditions
      2. Workflow has "Waiting for support" as the starting status
      3. Here, if we perform a self loop on "Waiting for support", the SLA starts running when it must still be in a Pause state.

      The problem does not occur for any other status in the workflow, it happens only when its the first status.

      Expected Results

      SLA must be in Paused state.

      Actual Results

      SLA starts running.

      Workaround

      • Don't have the self transition on this status
      • or don't set the first status as the Pause condition
      • or add one more status before this in the workflow

        1. image-2025-03-28-20-22-39-109.png
          89 kB
          Barkha Bansal
        2. image-2025-03-28-20-23-27-799.png
          83 kB
          Barkha Bansal

            Assignee:
            Unassigned
            Reporter:
            Barkha Bansal
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: