Issue Summary

Preserve all historical SLA cycles when SLA start condition is met again

Steps to Reproduce

1. Configure an SLA in Jira Service Management (e.g., Resolution SLA) with specific start and stop conditions.

1. Create a ticket that meets the SLA start condition.

1. Allow the SLA to reach a specific outcome (e.g., let it breach or complete it by meeting the stop condition).

1. Perform an action on the ticket that triggers the SLA start condition again (e.g., move the ticket from a "Resolved" status back to "In Progress").

1. Observe the SLA panel in the issue view.

Expected Results

Jira should start a new SLA cycle while permanently preserving and displaying the complete history and result of all previous SLA cycles (Met, Breached, Paused, etc.) for audit and reporting purposes.

Actual Results

Jira starts a new SLA cycle, but the previous SLA cycle/history (including earlier breaches) is no longer easily visible or available in the primary UI/reporting views, appearing as if it has been overwritten or erased.

Workaround

A potential workaround involves using Jira Automation to capture SLA data (using smart values like {}{{issue.SLA Name.completedCycles{}}}) and storing it in a custom long-text field or an external system whenever an SLA cycle completes. This ensures a permanent text-based audit trail is maintained on the issue.