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

SLA should be automatically calculated after JSON import if they contain issue history

XMLWordPrintable

    • 31
    • 34

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Description

      Currently, when issues are created via JSON import into a JSM project, they don't show the SLA values in the issue view. They need to be recalculated via REST calls as mentioned in this article https://confluence.atlassian.com/jirakb/slas-in-jira-service-management-are-missing-or-disappear-954252774.html

      Suggested resolution

      The suggestion is to add this functionality in JSON import by default.

      Notes

      SLA calculation works by getting the issue events from the issue history and calculating it accordingly. CSV import does not support issue history import (only JSON import), hence imported issues via CSV will never have SLA since those issues do not have history.

          Form Name

            [JSDCLOUD-8422] SLA should be automatically calculated after JSON import if they contain issue history

            Diego Leitao added a comment -

            Workaround:

            Send a POST request:

             <your-instance>/rest/servicedesk/1/servicedesk/sla/admin/task/destructive/reconstruct?force=true

            Include the JSON payload in the request body.

            This will trigger SLA recalculation for the specified issues.

            Important Considerations:

            • This API call is a destructive operation. While unlikely, there's a small chance of data loss. Test in a non-production environment first.
            • Ensure you have the necessary permissions to make this API call.

            This workaround provides a temporary solution until the direct CSV import functionality for SLA data is implemented.

            Diego Leitao added a comment - Workaround: Send a POST request:  <your-instance>/ rest /servicedesk/1/servicedesk/sla/admin/task/destructive/reconstruct?force= true Include the JSON payload in the request body. This will trigger SLA recalculation for the specified issues. Important Considerations: This API call is a destructive operation. While unlikely, there's a small chance of data loss. Test in a non-production environment first. Ensure you have the necessary permissions to make this API call. This workaround provides a temporary solution until the direct CSV import functionality for SLA data is implemented.

              Unassigned Unassigned
              akhan@atlassian.com Asim K
              Votes:
              24 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated: