I don't have a "time remaining" sla and don't recall it being there in the beginning but could be wrong. Maybe it is a Server SLA? I have time to resolution but it is no longer stock. :-)
Do you know what the SLA was tracking? Maybe we can recreate if no one has an example.
It's one used to automatically close the ticket after 3 days. I am using JSD cloud.
I think when you create a project it creates 3 or 4 SLAs that ship with it, This SLA seems like starts counting on resolution set to done
@Romer Ventura, So a bit confused. I use cloud as well and have created a test project and there is no "SLA time remaining" SLA rule. Can you provide a screenshot of what SLA rules you currently have? Below is a view of my test project. The first one "non-responsive customer" is one i created the other two are the defaults. Also can you provide a screen capture of the automation details, specifically the If and when details?
BTW, I can certainly help reconfiguring the close after 3 days as that was one I just answered yesterday here. So we can certainly solve this.
Hello Atlassian Community! I'm Tania, a Senior Product Marketing Manager for Jira Service Desk Cloud! I'm excited to announce some exciting improvements coming up for those who work with queues and...
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