Comments
-
Hello @Christian Jordan , Listing issues with their linked issues is in our current roadmap but, I can tell you how to calculate total cycle times and provide you a workaround for listing linked issues while this feature is being developed by my team at OBSS. You can calculate Cycle Time by using, Timepiece - Time in…
-
Hello @Samuel Kolloch , In order to track the duration on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type that will meet your need. Our app is available for…
-
Hello @Ali Raza , Welcome to the communtiy! There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at…
-
Hello @Karim Mohamed , From what you have written, I understand that you need the total time taken to resolve a ticket. You will find it much easier to use a third party application to do this. You will need different metrics and measurements from time to time to measure the productivity and speed of the team(s). Instead…
-
Hello @Eran Roiter , There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type…
-
Hello @Ana Figuera , Jira Product Discovery is keeping its ideas as Jira issues under the hood so any reporting that works for issues should also work for them. You have two options here. One is to use the time logged by the users. However, this is not always ideal as team members tend to forget to log the time spent on…
-
Hello @Shrushti Shah , Welcome to the community! In order to measure Cycle Time, Time for Code Review and QA Cycle I would recommend using a third-party app, as there is no built-in solution in JIRA for this. My recommendation is Timepiece - Time in Status for Jira app, the oldest and leading Time in Status app in…
-
Hello @Cristiane Gonçalves , Welcome to the community! There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my…
-
Hello @Ushna Sarfaraz , There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type…
-
Hello @Dinonath Khan , As others already mention there is no built in solution in Jira for this. I also have an app suggestion for you. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type that will meet your…
-
Hello @Monali Panchal , Welcome to the community! Unfortunately as @Trudy P Claspill mentioned there is no JQL code available natively to exclude weekend days. If you say that working days are not very important to me and just getting reports on a daily basis is enough for me, you can use the JQL query below. project="dm"…
-
Hello @dta , You also asked how you can do it with a time in status plugin. Let me answer that for you. This result can be achieved with Timepiece - Time in Status for Jira app, the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Cloud, and…
-
Hello @Carolann Hess , Welcome to the community! I understand you are not looking for an add on right now, however there is no built in solution in Jira for this. So in order to track the time spent on each ticket per day I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time…
-
Hello @kalvarez , Jira's own SLA counters do not work backwards. Whenever an SLA is enabled, it starts calculating for issues that are within the SLA counter limits at that time. It does not calculate for issues whose SLA definition endpoint has been reached. If you want to see historical SLA breaches, you will need to…
-
Hello @Thatiparthi Venkatesh , There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a…
-
Hello @Tanuja.bhosale , Welcome to the community! There is a lot of discussion about this in the Atlassian community. However, there is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading…
-
Hello @Consuelo Nicoli , Welcome to the community! Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type that will meet your need. Our app is available for both Jira Cloud, and Data Center. Duration Between…
-
Hi @Eduardo Anflor - MindPro , Actually this is what I was trying to tell you in my first answer. Lets say you set your SLA's when your issue is in In Progress status. This means that the Time to First Response counter will not be effective for this issue because the first response has already been given. Unfortunately,…
-
Hello @Dom Cronshaw , Welcome to the community! Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type that will meet your need. Our app is available for both Jira Cloud, and Data Center. Duration Between…
-
Hello @Eduardo Anflor - MindPro , Unfortunately, Jira's own SLA counters do not work backwards. Whenever an SLA is enabled, it starts calculating for issues that are within the SLA counter limits at that time. It does not calculate for issues whose SLA definition endpoint has been reached. If you want to see historical SLA…
-
Hello @Kacper P , Welcome to the community! In order to measure the duration between statuses or the status durations I suggest you use a 3rd party app. For this purpose I can recommend Timepiece - Time in Status for Jira app, the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team at…
-
Meral Hanım Merhabalar @meral cetintas Atlassian Community'e hoşgeldiniz! Talep etmiş olduğunuz raporlara OBSS tarafından geliştirilen Timepiece isimli Jira eklentimiz ile kolaylıkla ulaşabilirsiniz. Aynı soruya cevap arayan diğer kullanıcıların da anlayabilmeleri için açıklamaya İngilizce olarak devam edeceğim. Konuyla…
-
Hello @vincenzo.spatafora , For your KPI reporting needs I can recommend Timepiece - Time in Status for Jira , the oldest and leading "Time in Status" app in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Data Center and Jira Cloud. Timepiece mainly allows you to see how much time…
-
Hello @Syed Mazher Husain & @john smith , Welcome to the community! I would like to introduce you to a very advanced tool with which you can easily count the number of times the tickets have been moved to specific status for given Sprint. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in…
-
Hello @Bill McMillen , I wrote an article on how to manage blocked tasks in Jira. However, the system I suggested includes a blocked status in the workflow. And as you mentioned above, for this system to work, people in the organization need to develop a culture of using blocked tasks. Anyway, I'll give you the link to my…
-
Hello @Hizkeel Khan , All of the goals that you've listed above can be achieved with our app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a dashboard gadget that will meet your need. You mentioned you don't want to use…
-
Hello @Finn Tyndall , Welcome to the community! In order to track the time spent on tickets specifically labelled either reactive or proactive work on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is…
-
Hello Hans, I am happy to hear that your issue is resolved with the help of JIRA automation. However, if there is a place where JIRA's automation capabilities are insufficient, our application is always there for you. Timepiece - Time in Status for Jira also has a very capable REST API. This means you can get the reports…
-
Hello @Hans van Rijsewijk , Welcome to the community! You are correct, the required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Good news that report is available in our application where you can directly learn the transition dates without having to deal…
-
Hello @Saad Haq , In Timepiece - Time in Status for Jira it is also possible to provide a time in status for the time the ticket was in a specific Jira project. In the example below I moved these issues into 3 different projects and you can see how much time each issue spent on each status in each project.
