Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5312

SLA Caching leads to SLAs overwriting Each Other

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • 3.6.4
    • 3.4.0
    • SLA
    • None

      Issue Summary

      When an issue transitions to a condition that is meant to meet a complete condition for an SLA, there are times the SLA would simply start to count again.

      Environment

      JIRA Service Desk 3.4.x

      Steps to Reproduce
      1. Setup the time to resolution condition in a JIRA Project.
      2. Transition an issue to a status such as done to meet the condition for the SLA to be met.

      Reproducing this issue is difficult since it happens randomly, however the above steps match the use case.

      Expected Behavior

      JIRA would mark the SLA as done and it would stop counting.

      Actual Behavior

      For some reason, JIRA would mark the SLA as done and after a while, it would start to count.

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: