Gökçe Gürsel {Appfire} Atlassian Partner

Hi @Richard Imbrogno , Do you use Server/ DC or Cloud?

Hi @Doğucan Baskın , I believe by SLA end, you mean the target date of the SLA - the last moment that the SLA end condition should be satisfied. For this, you can use Time to SLA Cloud. It has a feature called the SLA target date custom field, which lets you populate a date-time picker type custom field of your choosing…

Hi @Gajanan Sasane , JSM SLAs have search functions that you can use. A JQL like: resolution is not EMPTY AND "Time to resolution" = breached() for the SLA "Time to Resolution" should work. https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/ For the Jira Core and Jira Software (and…

Hi @Shruti and @Shruti Ahuja , Another possible solution for this is Enhancer Plugin for Jira. Enhancer Plugin has a field called Linked ISsue Field which allows you to show the fields of linked issues. Documentation These fields can be added to the issue navigator as columns or to other reports as well. Please let me know…

Perfect! I'd be happy to assist you if you have further questions. Cheers, Gökçe

Hi @Aggeliki K , You can do this with Time to SLA. Time to SLA has the dynamic duration feature which allows users to enter the SLA goal in a custom field of their choosing. The input (should be a time string) will be excepted as the SLA Goal which is exactly what your use case calls for. You can also use Automation to set…

Hi @julio valdez , You can use the Enhancer Plugin for Jira for this. It has a custom field called Time in Status that captures the time spent in a particular status and gives a piece of drill-down information based on the assignee. It also has Time in status gadget that shows the average Time in status info. Please let me…

Hi @Wanina Sanches Pires , You can try Time to SLA. You can define SLAs for your customers and show the SLA panel in the customer portal to your customers. You can show the start date, end date, and target date of your SLAs as well as remaining, elapsed, and pause durations. Please let me know if you have further…

They will get back to you. Don't worry. Please let me know how this goes. Cheers, Gökçe

I can't see any issues tbh. Maybe you can add Resolution: Set to the end conditions like this: If this is a production instance and you are reluctant to make changes, it'd be better to open a support ticket to Atlassian. Cheers, Gökçe

This looks ok. Is it possible to share a screenshot of an issue that doesn't stop when the issue is entered Closed status? You can obfuscate sensitive info.

Is it possible for you to share a screenshot?

Hi @TAC Admin , Is it possible for you to share your SLA configuration? Cheers, Gökçe

Hi @Yogesh Mude , You can use the Enhancer Plugin for Jira to calculate the duration that the issues are spent in the open status. It has a custom field called Time in status which is a perfect fit for your use case. This field is searchable/sortable so you can use it in the issue navigator. What is more, Enhancer also has…

Hi @Gajanan Sasane , You can check out the documentation I've linked but as I've mentioned there is no SLA search function that comes with Jira Cloud that searches the SLAs that will be breached the next day. You can try to find a workaround with the existing functions but at some point, it's probably going to fall short.…

Hi @Gajanan Sasane , You can refer to the doc but there isn't a search function for the target date (your use case) https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/ You can use Time to SLA for this. Time to SLA has Target Date custom fields that can be used in searches. So all…

These two plugins work in Jira Software. But if you mean if your use case can be done OOTB, I don't think so. Please let me know if you have further questions. Cheers, Gökçe

Hi @UsamaMehboob , You can use Time to SLA's one of a kind gadgets for this. Just define your SLAs and calendars in TTS, regenerate the SLA data and start using TTS gadgets in no time. Periodic Met vs Exceeded SLA Gadget can be used for your use case. Also, this gadget is interactive, meaning you can click on the bars and…

Hi @Amber Darko , You can use Time to SLA - Next-Gen SLAs for this. Just add the SLA End > Field Change > Assignee > when assignee is in the group > Developer to your SLA end or pause condition and you are done. It's that easy. Next-Gen SLAs comes with a great performance and you can enjoy the one of a kind TTS features…

Hi @Francel , I don't think Jira has this capability but you can use the Enhancer plugin for Jira. It has the Time between custom field that measures the time spent between two statuses/events. So, for your use case, you can set it to measure the Time spent between the issue creation and the Resolved or Done status for the…

Hi @Jeff Davis , There is no OOTB solution for this but you can use the Enhancer Plugin for Jira. Enhancer has Time in Status custom field that can be configured to calculate how many days issues are in a certain status. You can later use this field in the issue navigator to perform searches. Please let me know if you have…

Hi @Onyx Gendry , You can use the Comment Enhancer app for this. It has features called Last comment, Last Commenter, and Last Comment Date custom fields that will help you to stay on top of your tickets. You can also search issues against these custom fields. Just start typing custom field names, and search issues. You…

Hi @Nasim Chowdhury , You can modify the 24h SLA Goal with a JQL like this: issuetype = Finance AND summary !~ "Additional Order Details" You might need to tweak it a bit as I didn't have a chance to test it. Cheers, Gökçe

Hi @Christy Cheung , There is a section in the left column. Are you able to see that?

Hi @GG , You can try Time to SLA for this. Time to SLA has a wide range of calculation methods that can assist you with your use case. For this, you can try the All Cycles calculation method, which will allow SLAs to continue counting where they left off once the issue goes back to the start status i.e. Re-opened. Please…

Hi @Karen Orr , I think Time to SLA can solve your issue. We have an article about recurring SLAs that you can set up using TTS linked below. https://community.atlassian.com/t5/Jira-Software-articles/How-to-define-recurring-SLAs-for-your-Cloud-projects/ba-p/1504413 Please let me know if you have further questions. Regards,…

Hi @edward huang , This is the server REST API link: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/ and this is the Jira API link: https://docs.atlassian.com/software/jira/docs/api/7.6.1/ Good Luck!

Hi @edward huang , You have tagged this issue as a Cloud question but your screenshot looks like an on-prem instance. For Cloud you can refer to Cloud Rest API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ The Rest endpoints are extensive and you'll use them with ease. For On-prem instances, Jira…

Hi @Milena Kamasova , You can click Apps > Time to SLA > SLA configuration and define your SLAs. If you want to limit the SLA you defined to a particular project, you can add project = xxx in the JQL box. After the SLA definition, please navigate to Apps > Time to SLA > Customer Portal SLAs and select the Request Types…

Hi @Milena Kamasova , You can do this with Time to SLA. Time to SLA has an option to show the SLA panel in the customer portal that has the SLA start, end, target date, SLA remaining, elapsed durations, and SLA state. This is a perfect fit for your use case. Time to SLA also has many exciting features like the ability to…