Emre Toptancı [OBSS] Atlassian Partner

Hello Dylan, Out team at OBSS built Time in Status app for this exact need. Using Time in Status you can: * Report on how much time each issue spent on each status, assignee, user group and more. * Get reports based on 24/7 calendar or define custom work calendars accoring to your working days and hours. * Get averages of…

Hello, I didn't know about that bug and sorry to see that. The existance of that checkbox and the bug seems to mark both the point of solution and the end of the way. The checkbox was put there by Atlassian as part of the control chart so (currently working or not) that seems to be the only way to achieve what you need on…

Hello @rajalingu_dasari , Where do you get this export file? The normal Jira issue navigator export only gives field values of issues in the export file and statuses are not fields on an issue. For exporting durations spent on statuses/users or exporting dates about statuses, our team at OBSS built Time in Status app. I…

Hello Diego, While working on the Control Chart, you should be able to select or unselect the "Include non-working days in calculations"checkbox to include or exclude those days in the report. (The checkbox on the right side of screen, under the chart) If you want a more detailed and advanced solution, our team at OBSS…

Hi @Billie Shato , Time in Status uses the data in Jira issue histories to produce its reports so, YES, you will be able to get Time in Status reports for issues created and completed before the app is installed. EmreT

Hello @Janelle Seto , Jira does not calculate status durations by itself. Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status. You can choose to…

Hi @Timothy , You can't get metrics like cycle time or lead time by just using JQL because all JQL does is filtering. It does not do calculations. On the other hand, a JQL query like below might be helpful for throughput. It fiters issues that are currently resolved or closed and was resolved in January 2019. project = ABC…

Hello @Timothy , Our team at OBSS created Time in Status app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status, you can report how much time each issue spent on each status. You can choose to include, exclude or combine certain statuses so you can easily have TiS calculate…

Hello @Sally Abd Elrahman , Jira does not calculate status durations by itself and the Time Spent column in issue navigator shows the sum of manual worklog entries on the issue. Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center.…

Hello @[deleted] , Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status. You can choose to include, exclude or combine certain statuses and you can add…

Hello @Marzi Goodarzian and @Don Nelson , If you are interested in a ready-to-go solution, our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each…

Hello Aleksey, Control chart calculates the data using the issue history, the same history you can see at the bottom of each issue's view screen. Since it is not stored as a field value on Jira, it is not possible to show it on the card. If you are interested in a ready-to-go solution, our team at OBSS created Timepiece -…

Hello @Madison Rojas If you are interested in a ready-to-go solution, our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can also see the number of times each status or transition was used (very useful for…

Hello Aleksey, This will be a similar answer to your other question but again, if you are interested in a ready-to-go solution, our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each…

Hello Aleksey, If you are interested in a ready-to-go solution, our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user…

Hello Jens, Following this discussion me and my team went through all custom fields on the aforementioned customer system and configured them to have localized contexts rather than global contexts. After that we set search indexers to None for a lot of fields in the system which were being used as form fields and were…

Hello @Dana Gould , The most likely cause is the date filter. Time in Status automatically adds a date clause to your selected filter. By default, the date filter filters issues of the last three months. When you run a Time in Status report, you will see a JQL query at the bottom of the report. That JQL query is your…

Yes, you can use Time in Status by OBSS for this case too. It does not matter if the status transition was done by a user or by automation. As long as you can see the transition in issue history, you can use Time in Status by OBSS to report on it. By the way, you may get the issues that were closed more than 3 months ago…

Hello @Leticia Kralik , If you are looking for a ready solution, our team at OBSS created Timepiece - Time in Status for Jira app for this need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user…

Hello @Nicolas Martin , By on-prem I mean Time in Status (by OBSS) hosted on Server and Data Center editions of Jira (Jira that you host on your servers). Time in Status REST API is currently available only for Jira Server and Jira Data Center. We have plans to introduce a REST API for cloud platform as well. File Export…

Hello @Robert Okemo , Unfortunately, Jira does not give this information directly. If you want to do this yourself, you will have to use make a REST call for each issue to get its history and traverse through issue history to do the calculation yourself. I know you said you don't want to use add-ons but for those who visit…

Hello @ugur.gecgil , Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user group. (useful for calculating lead/cycle…

Hello @Pavan , Our team at OBSS created Timepiece - Time in Status for Jira app for your time related needs. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user group. (useful for calculating lead/cycle…

Hello @Chris Townsend , Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user group. (useful for calculating lead/cycle…

Hello @Nika Aydinyan , Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user group. (useful for calculating lead/cycle…

Hello @Dana Gould , As you said, your firewall might be preventing access. We sometimes see similar issues with other customers as well. When you install Time in Status by OBSS there are two default calendars. One is the 24/7 calendar and the other is the Default Business Calendar (with working hours as Monday-Friday from…

Hello @Dana Gould , I wish you success in your new company. I also want to correct a misunderstanding. Time in Status by OBSS does not only work on a 24 hour calendar. You can define multiple custom calendars, each with its own working days, working hours and time zone. EmreT

Hello Maruthu, If you are interested in a ready-to-go solution, our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user…

Hello Chad, For time and date related metrics, you can use Timepiece - Time in Status for Jira. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user group. (useful for calculating lead/cycle times and…

Hello Ahsan, You cannot calculate cycle time with basic JQL. JQL only does filtering. Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can report how much time each issue spent on each status. You can…