nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SLA match is lost when costumer adds a comment

Herman Jansen

We have a list of SLAs in our system based on issuetype, priority and an insight field with the type of SLA that was sold to the customer (silver, gold, platinum.

When we create a new issue, we see the SLA is matched and the remaining time is set according to the SLA.

At some point the agent changes the status of the issue to a Stop status for "time to first response". Meaning the time to first response is met.

Then next the customer adds a comment to the issue, and at that point the SLA shows that it matches All remaining issues. For some reason the proper SLA can not be found anymore.

Of course this is not correct as it should still match based on issuetype, priority and the customer SLA field.

Accepted answers

Aidan Goldthorpe

Hi @Herman Jansen,

Thanks so much for your question.

I understand your SLAs aren’t matching the expected goal after a customer adds a comment. Would you be able to provide a screenshot of your configuration to help identify what may be causing this issue?

Thank you,

Aidan
Jira Service Desk

All comments

Aidan Goldthorpe

Hi @Herman Jansen,

Thanks so much for your question.

Thank you,

Aidan
Jira Service Desk

Herman Jansen

Aidan,

We have already identified the problem.

In the query we use for the SLA we used data from the Insight database to determine what kind of an SLA a specific customer has (Platinum, Gold, etc.). For some reason this mechanisme is not very reliable.

We have now changed this mechanisme.

When creating a ticket we fil a custom field with a value based on the insight data, and then we determine the SLA on that custom field.
This changed solved the problem for us now all our customer issues have a correct SLA all the time.

Sorry for not updating this question with our solution.

Herman Jansen

Aidan Goldthorpe

I'm glad to hear you've solved the problem! Using custom fields sounds like a good fix.

Regards,

Aidan

Tim Eddelbüttel

Hello @Herman Jansen ,

what is your Jira Service Desk version? I have the same issue on an instance.

Jira Service Desk is running on 3.16.8.

@Aidan Goldthorpehere is a simple SLA configuration.

Bildschirmfoto 2020-05-19 um 20.27.37.png

Maybe this helps. I've created a support ticket for that: SDS-50873

Herman Jansen

We are using 4.4.3

Aidan Goldthorpe

Hi @Tim Eddelbüttel

That's very unusual behaviour. It's interesting that both of you observe this with Insight custom fields. Are there any differences in the JQL results after adding a customer comment? Does any other behaviour trigger changing the goal, such as transitioning the issue or adding internal comments?

I suspect the issue is in some way connected to how that particular custom field works, but it would be good to identify the root cause.

Tim Eddelbüttel

Hello @Aidan Goldthorpe,

no there is no other behaviour. Here are the steps to reproduce:

Setup clean Jira Service Desk instance
Created project with IT Service Desk Template (ITIL).
Install recent Insight version
For testing (as it creates the custom field) I've created another project with the Insight provided project template as it creates the schema and custom fields (e.g. affected business service)
Create 1-3 test business services in the insight schema
I've added the field to the Service Request screens from the IT Service Desk template project.
Added my SLA goal as above. Technically the SLA goal for the example will be set if a service is selected
Create sample customer
Customer creates simle "Get it help" issue from the portal
As agent / admin i've adding the affected business services.
The SLA will be shown.
Customer comments from portal (transition isn't needed) and the SLA goal disappears.

Maybe the problem is the "dynamic" JQL. For example if I change the JQL to be more static like "affected business service" = KEY-123 then I don't have the problem.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server