Zoryana Bohutska _SaaSJet_ Atlassian Partner

Hi @Gajanan Sasane Optionally, you can consider the solution Dynamic Filters: JQL Replacer for Jira (created by my team). It lets create difficult requests for filtering issue lists without JQL knowelage. 

Hi @Gajanan Sasane As an alternative solution, you can try Dynamic Filters: JQL Replacer for Jira. It allows filtering issues without JQL knowledge. For example, you can create such a smart field for your request and add it in dynamic filters. Also, you can save dynamic filters for Jira filters. Hope it will help Regards

Hi @Tracee Sorrentino You can try to use JQL: summary ~ "text." Or also, you can try Dynamic Filters: JQL Replacer for Jira. It allows creating requests without JQL knowledge. Hope it will help Regards

Hi @Prabhu Chilukuri Also, you can set an SLA timer for JSW issues. But to do it, you need to install an app from Atlassian Marketplace. App will help you set and monitor SLA time limits for the most important issues (using Priority, Lable, Assignee, Status fields, etc.), and send notifications about overdue issues. In…

@Frankie Angai You can try Dynamic Filters: JQL Replacer for Jira. It lets you create a quick filter without JQL knowledge and save it for Jira filters. So you can use it when you need it again. I hope it helps. Regards

Hi @Stéphane You can try to use Dynamic Filters: JQL Replacer for Jira. It allows you to filter issues without JQL. For example, you can select description or summary (field) for your request and contains (operator) + text you are searching for.

Hi @Matt Hackett If Organisation`s name is in the custom field of tickets, you can try SLA Time and Report. It allows set for SLA start/stop conditions any issue fields, inclusion Organisation. Hope it will help you Regards

Hi @Rodriguez, Jhon Ronald For the next cases when you don't know how to build the right JQL, you can try Dynamic Filter: JQL Replacer for Jira (created by my team). It allows generating requests to Jira without JQL knowledge. For example, for your question, you can create such a request as in the screenshot. Regards

Hi @Catherine, yes, this labels = Dev_Review AND ("Epic Link" != 1233 OR "Epic link" is empty) - should work for you. For the next cases when you won't know how to build a complicated request next time, you can try Dynamic Filter: JQL Replacer for Jira (created by my team). It has the flexible builder that allows creating…

Hi @Thomas Harborg Yes, @mogavenasan is right. To get data about when the issue was in each status, you need to consider a solution from Atlassian Marketplace. For example, Issue History - lets you view the time and date any issue field was changed (including status changes). Time in status for Jira Cloud by SaaSJet -…

Hi @Adam King As an alternative, you can try Issue History (developed by my team). It lets you get the full changelog about each issue. You can export its data, sort and send it to external users. Regards

@Dirk Ronsmans Sorry, I misunderstood the problem. For this case, you can consider other solution Time in status for Jira Cloud. Using its Pivot table feature, you can create the time spend report for L3 support (Tech tasks). I hope it will help. Regards

Hi @Jota As an alternative, you can try to use SLA Time and Report (developed by my team). It lets you set SLA for all types of projects (from Jira Service Management, Jira Software, Jira Core). Regards

Hi @Luke Ryan You can try SLA Time and Report app (developed by my team). It has flexible options for setting start/pause/stop conditions: you can select any issues fields (default or custom) for them (issue type, project, label, priority, etc.) Let me know if you will have questions. Regards

Hi @Esther Amunga You can also consider an alternative solution SLA Time and Report (created by my team). It lets you set SLA conditions using any issue field, including issue type or other custom fields (like a service category). This app also allows set SLA for Jira Core, Jira Software issues. I hope it helps.

привет @TAC Admin Возможно у тебе включено multiple cycles option?

Hi @hmnaqvi Also, you can consider other solution Time in status for Jira Cloud app - automatically calculate the time each ticket or issue was on each stage of the workflow (in progress, on hold, etc.). To select issues that have Met or Branched SLA you can use JQL filter (for example "Time to Response" != everBreached())…

Hi @Matt Davis One of the solutions from the Atlassian marketplace is Time in status for Jira Cloud app (created by my team). It lets you set gadgets with time in status, average time in status, and other reports on Jira Dashboard. You can view data in tablet and chart views. Using its build-in JQL filter you can select a…

@Gajanan Sasane If you want filters tickets from JSM, read this instruction https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/. It should help you. Regards.

Hi @WasimBuden You need to search solution from Atlassian Marketplace. I think SLA Time and Report can help you. It lets you set SLA time goals not only for JSM tickets but also for Jira issues. So you can set OLA for L1, L2, L3 teams. This add-on has reports (tablet and chart view) and soon chart reports will be available…

Hi @Yuval Bonen For cases when you want to create a difficult JQL request and don't know how to do it, you can consider Dynamic Filter: JQL Replacer for Jira (created by my team). It allows creating any request to Jira (to select issue list you need) without JQL knowledge. All those requests you can save as dynamic filters…

Hi @Mohamed Darmoul Jira Service Desk (Management) we use only for its support portal. There are only a few workers from the first level of the support team. Other team works with SLAs created using SLA Time and Report app. You can request the free demo call with my team. And they will describe all add-on features in more…

Hi @stephen.abiero @Ste Wright thanks for the mention. My team developed the app Time in status for Jira Cloud. It lets you monitor how long a ticket takes on each status. And you can add its gadget to Jira Dashboard and always view actual data (in tablet or chart view). Additionally, this add-on allows analyze time data…

I don`t know how to do it using JSM, because there aren't such SLA conditions as assignee group. But I think you can try to do it by creating different statuses for each assignee group and by configuring automation rule to move tickets to each status according to the assignee issue field. Then you can configure the status…

What timer do you want to set there?

Hi, have you try this solution https://support.atlassian.com/jira-core-cloud/docs/use-jira-cloud-for-sheets/ ?

Hi @Pete P Maybe, you can find the solution at this discussion https://community.atlassian.com/t5/Jira-questions/SQL-to-return-for-every-project-most-recent-updated-date/qaq-p/437248 

Hi @Bin You can also consider the solution from Atlassian Marketplace developed by my team - SLA Time and Report. It lets you set for star and stop SLA conditions any custom fields: assignee (by role or name), label, issue type, priority, etc. Using this app, you can create SLA goals for issues from all Jira projects…

Hi @Mohamed Darmoul As Nic mentioned, you can use the cheaper version of JSD - until 10 users - only for the first support level. And for tech support and the rest of the team (L2, L3), you can use the app for SLA setting and tracking for Jira Core and Software issues like SLA Time and Report add-on. In this way, you can…

Hi @Denis Leskovar What tool do you use for SLA settings?