JQL for Time to SLA plugin

[Tatevik Alaverdyan]

Hi community,  we are using Jira cloud and have Time to SLA plugin. 
I want to write JQL to find for example issues which have "SLA name" breached, but Time to SLA does not support JQL's.

Time to SLA plugin has it's Reports, which show information, but i want Dashboard, that's why JQL is necessary.

 I have installed Scriptrunner plugin for issuefunction in (...) JQl, but it is not supported for Jira cloud either. 

Can you help me to find a way to filter SLA's by JQL, plugin or something.

[Alina Kurinna _SaaSJet_]

Hi @Tatevik Alaverdyan !

I have a solution for you: try the SLA Time and Report add-on. This tool allows you to filter and analyze the data you need efficiently. Additionally, it enables you to monitor SLA metrics directly on the SLA Grid in real-time. You can also add a gadget to your Jira dashboard to access key metrics quickly.

How Does It Work?

After configuring your SLA settings in the SLA Configuration menu, navigate to the Reports or Home page to see the results in a grid.

The SLA report includes columns with detailed issue information:

• Type, Key, Summary (permanent columns).
• Assignee, Status, Time to SLA, etc. (customizable in the "Columns" menu).
• A column displaying the SLA Timer for each issue.

The SLA Timer lets you track how much time remains to meet the SLA goal. Tickets with breached timers are highlighted in red, while tickets that are on track or have successfully met their SLA goals are shown in green.

In the grid view, you can customize the issue list by:

• Selecting issues to include.
• Adjusting the date range.
• Changing the time format.
• Managing columns via the column manager.
  
  

You can filter the issue list for SLA reports using various parameters such as:

• Project
• Assignee
• JQL
• Filters
• Labels
• Reporter
• Sprint, and more.

Then, move to Chart view:

Analyze SLA performance visually by switching to the chart view, which includes:

• SLA Met vs. Exceeded issue charts.
• Pie charts of SLA statuses (e.g., met or breached).
• SLA metrics by assignee.
  
  

This enables you to adjust reports based on your specific needs and gain valuable insights into SLA performance.

How to add a Gadget to your Jira Dashboard:

1. Go to the chart you want to add to your dashboard and click Create Gadget.
2. Select the desired dashboard and click Create. If you don’t have a dashboard, you’ll need to create one first.
3. Once the operation is successful, you’ll receive a notification with a link to the dashboard.
   
   

Beyond these functionalities, the add-on provides many other tools for effective SLA tracking and management. For more detailed information, you can refer to our documentation. You can also try the 30-day trial to see if the add-on meets your needs.

Feel free to reach out if you have any questions or need assistance — I’m happy to help! 

[Tatevik Alaverdyan]

@Alina Kurinna _SaaSJet_ thankss, is this app makes reporting based on Time to SLA plugin SLA's, or I should make new sla's with that app?

[Alina Kurinna _SaaSJet_]

@Tatevik Alaverdyan уes, you need to create new SLAs using the SLA Time and Report add-on. I’ve attached the documentation, which provides step-by-step instructions for setting it up, to help you get started quickly.

If you have any additional questions, feel free to reach out 😊

[Tatevik Alaverdyan]

Thank you but currently I cant change SLA configuration, as we use Time to SLA, I just needed jql for that plugin.

[Marc - Devoteam]

Hi @Tatevik Alaverdyan 

Contact the vendor of the app is the app doesn't support JQL or has integrations with other app, then your request is probably currently not possible.

According to the apps documentation it offers 2 dashboard gadgets and you can integrate with PowerBI

Or use the apps API that does offer a call to get SLA overdue (breached) information.

https://appfire.atlassian.net/wiki/spaces/TTSC/pages/36209134/REST+APIs 

[Tomislav Tobijas _Koios_]

Hi @Tatevik Alaverdyan ,

I think I've never used this particular app but I would recommend reaching out to vendor directly, via their support portal. Vendors are usually helpful and do support assistance when it comes to app configuration, or they could potentially forward you to some existing resources related to resolution or potential workarounds related to the solution for your requirement.

Cheers,
Tobi

[Tatevik Alaverdyan]

Thanks Tomi, 

I will try if no solution is provided by Atlassian community