Skip to end of banner
Go to start of banner

Time To SLA | error "Could not get SLA information for SLA Cards" and stopped working after upgrade

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

💡 INTERNAL ONLY

Error message : Could not get SLA information for SLA Cards

❓  Overview

After upgrading Jira recently the TTS plug-in has stopped working. Navigating to the SLA Configurations page gives a modal dialogue that does nothing, forever, and cannot be dismissed.

image-20240120-044541.png

Navigating to a Jira ticket with SLAs defined gives errors in the page elements responsible for loading SLAs.

image-20240120-044604.png


Error Message :

  1. Automatic Legacy SLA Migration
    Your Legacy SLAs are migrating, please wait..

  2. Error !
    Could not get SLA information for SLA Cards

  3. HAR logs error :
    {"migrationStatus":"COMPLETED","totalCount":1,"successCount":0,"failCount":1,"migrationUser":null,"migrationDate":"2023-11-10T17:15:12.916+00:00","errorMessages":["There cannot be same Start and End condition. (Entered in 'Open, Reopened' status - Entered in 'Done, Open, Proposal Review, QA Testing, Closed, Ready for Acceptance, In Development, Needs 3rd Party Clarification, Needs Reporter Clarification, Ready For Development, In Analysis, Ready for Analysis, Ready For QA' status)"],"errors":null,"warningMessages":[],"context":null}

\uD83C\uDF31 Solution

  1. Disable app

  2. Execute following SQL query(change according to DB that is being used)
    DELETE FROM "AO_C5D949_SLA_MIGRATION_RESULT" WHERE "ENTRY_TYPE" = 'MIGRATION_STATUS'

  3. Re-enable the add-on and wait for it to finish migration.

  4. Re-calculate SLA

  5. The legacy SLA had “Open” in both the start and finish conditions. Removed “Open” from the finish conditions.

    image-20240120-044713.png



  • No labels