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; } } }

Remove this SLA in red

Carlos Ramirez_k2towh

Hi channel,

I have a strange case... This issue was create with a type of request with no SLA, then I change the type of request to a request type that the SLA is 4 hours.

When I change, the SLA updated ant this issue is 78 hours out of the SLA.

So, I change to the original type request and the SLA still in red.

I went to the SLA and manually set that for this issue the SLA to "no target", but the SLA in the issue still in red

I did another test, set the SLA for this specific issue with more hours and it didnt result

What can I do for remove this SLA in red?

Thank you

Accepted answers

Gökçe Gürsel {Appfire}

Hi Carlos,

Can you share a screenshot of your SLA configuration and your issue history so that we can check the SLA calculations?

Cheers,

Gökçe

All comments

Gökçe Gürsel {Appfire}

Hi Carlos,

Can you share a screenshot of your SLA configuration and your issue history so that we can check the SLA calculations?

Cheers,

Gökçe

Carlos Ramirez_k2towh

Sure,

Thank you.

Gökçe Gürsel {Appfire}

Hi again,

What is your SLA End condition and SLA calculation method?

Carlos Ramirez_k2towh

Hi Gokce,

Since the beginning of the service desk, for this type of issue that is an "order" I set up with "no target".

For this situation, first I set to "not target" the specific issue in the third row, but it doesnt work.

Next, I set in the first row with 80 hours and doesnt work.

Its strange this case because as you can see, I have some issues in third row that I need to change with no target when I make some test.

This SLA is for the first time response.

Thank you

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management