Zoryana Bohutska _SaaSJet_ Atlassian Partner

Hi @Mukama You can consider other apps from Atlassian Marketplace. For example, Time in status for jira cloud tracks time spent in each status automatically. Regards

Dear @Daniel Egan Thank you for your comment! Please contact our support team (support@saasjet.atlassian.net) with a short message. They can check and resolve your issue. Best Regards, Zoryana

Hi @Michał Kwieciński "Control chart - shows the Cycle Time (or Lead Time) for your product, version, or sprint. It takes the time spent by each issue in a particular status (or statuses), and maps it over a specified period of time. The average, rolling average, and standard deviation for this data are shown." You can…

Hi @Ivan Barnade If you were using JSM you can't select an assigned team for SLA condition, but you can try to create custom statuses for different teams (like here https://community.atlassian.com/t5/Jira-Service-Management/time-to-assign-sla/qaq-p/1443458) or add other custom fields. You can also consider another tool…

Hi @Daniel Egan You can also consider other solutions from the Atlassian marketplace: Time Between Statuses - lets you set start and stop statuses for time tracking. SLA Time and Report - allows set SLA timer for issues from any project. For start/stop conditions, you can select statuses and other issue fields. Using it,…

Hi @Micaela Barros I think you can try to set SLA for issues to monitor delays. For example, you can try SLA time and report. For start condition select issue field - flag. For stop condition - any other issues field with which you marked unblocked issues. Then you can set SLA time limits for flagged issues and set…

Hi @[deleted] You can also consider other tools from the Atlassian marketplace. One of them is SLA time and report app. 1-2. It let you set an SLA timer with custom conditions and time goals. For start/stop conditions, you can select any issue field (status, priority, assignee, etc.). You can set automate actions…

Yes, SLA settings can help you. It lets you set condition and time goals. So for every ticket, you can view how long time it will take until the issue will be assigned.

Hi @Gabriel Mercer de Lima S. Also, you can consider SLA time and report app. It is like JSM lets you set SLA timer conditions according to different issue fields, including priority (but for Jira software and core issues). Let me know if you will have further questions. Regards

Hi @[deleted] You can try to set SLA time for Jira Software issues using SLA Time and Report. In this way, you won't need to change the due date according to SLA status of the JSM ticket. You will have a separate countdown for issues in JSW. Hope it will help Regards Zoryana

I think that yes, you need to set a few SLAs. The difference between them would be one condition for timer start - created date (from-to).

Hi @Rachael Humphries You can read about how to add this option in this discussion https://community.atlassian.com/t5/Jira-questions/How-to-create-checklist-in-task-description/qaq-p/728491 As for my team, we have recently begun to use one app from the marketplace.

This requires site-admin permissions, do you have them? If you have Jira Cloud Administrative rights you can use the Import Data option for admins to accomplish what you are trying to do above. Here is the documentation: https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/ Make sure…

Hi @Jenny Thompson Yes, as you see, there a few solutions for your request in the Atlassian marketplace. But now, there is no ability to use JQL to get the data you need. To the list of tools above, you can also consider Time in status for jira cloud or Time between statuses add-ons. Regards

Hi @Naomi Schwaiger You can view how long this time frame is set for using an app like Time Between Statuses. But to find what triggers this automated action you should search in set apps or in the JSD setting.

Hi @Magdalena Migas You can try also Issue History app. It lets you view the whole changelog for your Jira issues. This app saves the full history of any updates that were made for the issue list you want to analyze. Additionally you can view who and when made them. Regards

Hi @Murthy Dusanapudi Check this discussion https://community.atlassian.com/t5/Jira-questions/Best-way-to-migrate-from-HP-ALM-to-JIRA/qaq-p/460878 https://community.atlassian.com/t5/Jira-Core-questions/Migration-from-HP-ALM-to-Jira-server/qaq-p/1147575 looks like it can help you

Hi @tejas vansh As for me, the best is the native Jira mobile app. Also if someone from your team likes voice tools, they can try another app JIVA: Jira Intelligent Virtual Assistant it lets create issues by voice only. Hope it will help Regards

Hi @somnath.yadav For this case, you can consider also Issue History app. It will show you all status transitions, including information on when and who moved issues from one status to others. You can see what sets you should make in column manager in the screenshot below (choose issue key, summary, and status fields).…

Hi @nikita As an alternative, you can try Issue History app. It lets you view all types of issue changes, including status transitions. You need to select 3 issue fields in the app`s column manager: issue key, summary, and statuses. As a result, you will get the full report of status transitions for each issue. Also, this…

Hi @Sjoerd You can try also Issue History add-on from the Atlassian marketplace. The next steps you should do after this app installation: 1. Select the issue list by the parameters you need. 2. In the column manager, choose "Issue Type", " Summary", "Assignee" 3. Export data and open in Google Spreadsheet, then select…

Hi @Vinod Madhappan Optionally, you can try SLA Time and Report app. It let you set a timer, time limits and automate actions for exceeded issues. Add-on lets you select issues by any issue field parameters: project, status, priority, assignee, etc. Best Regards Zoryana

You can try SLA Time and report. This add-on lets you set a separate SLA config with time goals for the issue you need. To do it, create a new configuration and filter this request in condition. For example, you can type the name or any other field that is different for this issue. So you can change the SLA time goal for…

Hi @Caroline What tool do you use? You can try Time in status for jira cloud. It lets you share and export the average time in status data. This information also can be display in graph and tablet views on the Jira dashboard. Regards

Yes, you can consider it as one of alternative tools. It works with all type of Jira's projects (Jira Service Desk (management) Core and Software) 

Hi @Elena del Cura You can try app SLA Time are Report from Atlassian Marketplace. It has flexible SLA conditions, which can you help you to set them according to your needs. Regards

Hi @David Jackson In addition to the above solutions, you can consider another - SLA Time and Report. It lets you set a notification for issues that in the status you need. To achieve it, you need to set SLA conditions in your case - statuses. You can then set triggers: minimum time goal(1-5 minutes) and action for overdue…

Hi @Peter Chodakowski Looks like that no, you can read more in this discussion https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-change-default-issue-type-for-a-next-gen-project/qaq-p/1148127

Hi @Carlos Ramirez You also can consider SLA Time and Report. This tool lets you set flexible SLA conditions and triggers with goals and automate actions. There are available such actions for issues with overdue time goals: notification, change status, assignee or priority. So you can use this function to achieve that you…

Hi @siva You can also consider another tool for status time tracking Time in Status for Jira Cloud by SaaSJet. It lets you get time in each status automatically. Time in two statuses, you can get using the status group feature. This feature allows you to sum the time duration of statuses you need. I hope this will help.