Zoryana Bohutska _SaaSJet_ Atlassian Partner

Hi @Frank Reveles Additionally, you can try out another solution Time between Statuses. It lets you set start and stop statuses for time calculation. So you just need to select your projects custom statuses for Cycle and Lead time. Also, this app has the function for setting time limits with highlights (at time reports).…

Hi @Alexandre Also, you can consider other tools from the marketplace to generate reports of Cycle and Lead Time. For example Time in Status for Jira Cloud and Time Between Statuses add-ons. You can read more information about them and the Control Chart at this article 3 tools to analyze Cycle and Lead Time in the Jira…

Hi @Brian Gitonga You can consider solution from Atlassian Marketplace like SLA Time and Report. It lets you resolve this case by creating 2 SLA time configs. For the first case, you can use such SLA conditions as st the screenshot №1 Then save and copy this Config for the next case. But in the second case, you will need…

Hi @Andy Nichols At this video tutorial you can view all kinds of build-in reports for JSD https://www.youtube.com/watch?v=pRkVqQxOsVw Did you try all of them?

Hi @Isfan Fajar Sawito Except those great tools have listed above, you can try SLA Time and Report. If the first response in your case is determined by changing status or assignee (or another issue fields), this tool can help you too. It lets you set multi-calendars according to your needs (in your case with a work…

Hi @lludwick Welcome to the community! Also, you can try some app for time calculation like Time in Status for Jira Cloud or Time Between Statuses. Using those tools, you will be able to add to reports any columns according to your issue fields: assignee, label, etc. Moreover, Time in Status for Jira Cloud lets view time…

Hi @Samuel Bar Also, you can consider SLA Time and Report. It lets you set SLA time limit for 3 days and configure automate action for overdue issues as notification, changing assignee, status or priority. This tool works with issues from Jira Core, Jira Sofware and Jira Service Desk. Hope it helps Regards

Thank you very much for your answer!

Maybe you need to change customers permissions https://support.atlassian.com/jira-service-desk-cloud/docs/change-project-customer-permissions/ 

Hi @Hisham Badr Have you read this post? https://community.atlassian.com/t5/Jira-Questions/How-do-i-remove-a-customer-in-Jira-Service-Desk/qaq-p/33194

Sorry, no, it is available only for scrum and kanban projects, but in this year it will be released for nextgen https://community.atlassian.com/t5/Jira-Software-questions/Control-chart-for-next-gen-project/qaq-p/1342760 By the way, mentioned apps work with nextgen. Regards Zoryna

Hi @Jamie You could achieve this with a combination of a custom SLA and an automation rule: 1. Settings -> SLAs -> New Metric. Create a new SLA Metric that starts when the issue is resolved and stop when the issue is closed. You'll need to add some JQL to search for resolved issues and set a goal of 3 days or '72h'. 2.…

Hi @Javier_Corchado Maybe some issues were not from Jira Service Desk but from Jira Core or Jira Software. In this case, you can try third-party solutions like SLA Time and Report. It has flexible Start/Pause/Stop conditions according to your project issue fields ((Status, Assignee, Issue Type, etc). Also, this app lets…

Hi @Dan Towler You can monitor data history changelog with issue fields using Issue History add-on. It shows a changelog report, that includes data about who, when, and which changes have done to each issue. You can configure applications column manager to monitor data about specific issue fields you are interested in. For…

Hi @Hammat Samir Did you try to set SLA timer for your issues? For example, you can try SLA Time and Report. It lets you set start and stop condition for SLA timer (according to you issue fields), set time limits with automating actions for overdue issues: notification, changing reporter, priority or status. Data about…

Hi @Lionel Wolberger At this discussion https://community.atlassian.com/t5/Jira-Questions/How-to-track-amount-of-time-spent-in-status/qaq-p/590835, Dana mentioned Time in Status by OBSS : " We looked at the Time in Status plugin by OBSS, but so far find that it runs on a 24-hour clock and hasn't been that useful or…

Hi @matt welcome to the community:)! I think you can consider apps from Atlassian Marketplace developed by my team: Time in Status for Jira Cloud lets you monitor time in status data for each assignee and total time issues have been assigned to each user (assignee time). You can monitor all the data regardless of a…

Hi @Anastassiya Ulichnova Also, you can consider another solution from Atlassian marketplace: - reminders like Boomerang - lets to set reminders for each Jira issue with specified message, time, recipients and recurring settings. - apps for setting SLA timer (timelines), for example, Jira Service Desk (solution from Jira)…

Hi @Divjyot Puri Also, you can consider another tool from the Atlassian marketplace. It lets you monitor data about the number of times a ticket went to a certain and moved from one status to another. Regards

Hi @Yana Nikolayeva Have you read this post https://community.atlassian.com/t5/Jira-Questions/Could-I-set-up-a-kanban-board-on-JIRA-Service-Desk/qaq-p/389279 ?

Hi @Eri Abe Also, you can try Issue History application. It will let you generate a report about all changes made in each sprint including issue movings to the backlogs throughout the sprint. If you`ve questions I will be happy to help you Regards

The last column deletes when Sprint closing. You can find issues from the last column in the previous Sprint. 

Maybe you can find the answer here https://community.atlassian.com/t5/Jira-Questions/Cannot-integrate-Azure-AD-with-Jira/qaq-p/1314118

Hi @Arpita Dasgupta Also, you can consider another additional solution: Issue History can show you all changes have been made to these issues (+when and by who) Time in Status for Jira Cloud lets to monitor: - how long each issue was at different statuses of workflow, (+total and average time) - time each assignee spent…

Hi @Chander Korshika Also, you can consider Time between Statuses(Server). This app lets you view time each service desk ticket moved from one to another status. In your case, you just need to set Issue Created status as start status for the calculation and Resolved - as end status. You can get the average time using…

Hi @Amit Athalye You can try Time between Statuses add-on from Atlassian Marketplace. This tool allows you to get status to status data by setting a start and stop statuses for time calculation. To get information about the time issue was in one status you just need to select the same status for start and stop conditions.…

Hi @María Elena de León I think Time in Status for Jira Cloud could help you. This app from Atlassian Marketplace shows the time that each issue was at the workflow totally and time it was at each status. To get total time in each project you can export time in status data for each project and calculate the sum of total…

If you want to add new custom fields start and end dates to your instance, you need to have Jira administration global permission and create custom fields as described here.

Hi @Sai kumar Also, you can consider alternative solution Time in Status for Jira Cloud by SaaSJet. This tool lets you view average time in status data in time format you need: DHM (Days, Hours, Minutes), HM (Hours, Minutes), h:m (hours:minutes), M (Minutes), Decimal Hours etc. Additionally, this app calculates other…

Hi @DarkKnightess Issue History can help you get time and date when each issue was created, pulled into the sprint and moved to any status. But to get all this data together you need to use data export and compare all these data manually. Hope you will find the best solution for this request. Regards Zoryana