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

Changing the Stop time on an SLA recalculates SLA status for resolved issues

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 4.5.4, 4.4.2, 4.5.3, 4.8.1
    • SLA

      Issue Summary

      The SLA documentation mentions SLA status is not recalculated for resolved issues:

      The SLA status is only recalculated for open issues, not for resolved issues.

      However, SLA status for resolved issues is recalculated by changing the Stop time on an SLA.

      Steps to Reproduce

      1. Create a Service Desk project
      2. Create an issue
      3. Resolve the issue
      4. Note SLA status and SLA timer has stopped for SLA Time to resolution, as an example.
      5. Change the SLA Stop (Finish counting time when) condition in the project settings from default Resolution: Set to another value.
        1. Tested with: Entered Status: Canceled, Comment: By Customer, Due Date changed.
      6. Return to the resolved issue and note the SLA status and SLA timer are active, even though the issue is resolved.

      Expected Results

      No changes to an SLA will impact the SLA status for resolved issues.

      Actual Results

      The SLA becomes ongoing again which can verified in SLA audit logs.

      • Issue resolved within 1h SLA:

      • After changing Stop condition:

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSDSERVER-6844] Changing the Stop time on an SLA recalculates SLA status for resolved issues

            There are no comments yet on this issue.

              Unassigned Unassigned
              cterry@atlassian.com Chris Terry
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: