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?
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.
Hi again @Carlos Ramirez ,
Can you make a REST call to this issue and check output? I'm curious about the SLA info that this call will produce.
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events