When I log into my cloud hosted service desk instance I noticed that the SLA is displaying the following error:
Error rendering 'com.atlassian.servicedesk:sla-web-panel'. Please contact your Jira administrators.
Anyone run into this before and know how to solve this?
Hello Neal,
Thank you for reaching out to Atlassian Community!
I saw that your team recently migrated from Jira Service Desk Server to Cloud, so maybe this error is happening due to the migration.
To be honest, I didn't find any similar issue in Cloud. The only one I found with the same error message was related to a CSV import that imported the incorrect "Created date". Can you please check if the creation date for the tickets is correct?
Have you checked the SLA configuration?
If possible, as a test, delete and recreate the SLA again to confirm if it will apply to the tickets and show the correct SLA information.
Regards,
Angélica
I tried those proposed solutions and I think there is something wrong outside of my control and will require the Atlassian admins to fix.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for testing, Neal.
Is it showing the same error message if you create a brand new SLA?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oddly enough the issue has been resolved on its own, but I noticed that the existing SLAs were wiped out which my guess is that there was a delay in me removing them and the system recognizing that I had tried to remove them and recreate them. So I will have to assume that by deleting the SLAs and recreating them fixes this issue. Thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for sharing, Neal. I'm glad that it's working.
After an SLA is deleted and created again, it may take a while to sync and shown on tickets.
The issue that happened might be related to migration from Server to Cloud. During a migration, even not showing an error, many features may not work as expected. The option to delete and create the SLA again was the easiest and fastest way to fix it, otherwise, we would need to create a ticket in order to check the logs and access your site to see what was happening.
Please, let us know if there is any other issue regarding SLA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.