Emre Toptancı [OBSS] Atlassian Partner

Hello @ori gal You can do this with automation but you will need to create a custom field and an automation for each status time you want to measure. It will be expensive to build and maintain. Additionally, if you try to do this for a lot of measurements, those custom fields will put a lot of pressure on your Jira. On the…

Hello @serge calderara , Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics…

Hello @Elaine Collyer , The Cumulative Flow Diagram shows how many issues were in each status in the past. It doesn't help very much about Cycle Time. Could it be that you are referring to another report? Control Chart maybe? EmreT

Hello @Joe Pitt , Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics…

Hello @Steve Hooczko , I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee. Time in Status offers two report types for your…

Hello @george_bullock Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics…

Hello @Pablo Albani Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. The app can create reports based on a 24/7 calendar you can define…

On the Server or DC platform, you can manipulate the data in your Jira database (namely changegroupitem table) to update those dates. Of course, this is a not-recommended approach and you should be careful about data consistency. On the cloud platform, you don't have direct access to the database so updating dates in the…

Hello @Hizkeel Khan , For development and QA time estimation, your best bet would be to look at the past performance of your teams. To do that, Development and QA stages should be represented with separate status(es) in your workflow. After that you can get reports showing how much time your team spent on those statuses in…

Hello @Pedro_dantas Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics…

Hello @Randy O'Neal , Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics…

Hello @Yufang Vangaasbeek , If you want to go with a different approach and report times based on your workflows rather than the work logged by users, I can recommend our app. Our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly…

Hello @Lauren Hinrichs As Florian mentioned, you can see this information in the History tab of each issue but most of the times Jira users seek this information to get a report showing multiple issues or to calculate metrics like Resolution Time, Cycle Time, etc. And once again as Florian mentioned, our team at OBSS built…

If each customer needs its own portal and inbound e-mail address, the choice is obviously 1 project per customer. However, your choice might also be affected by your team structure. Do you have customer-oriented teams? Or service-oriented teams? maybe location-oriented teams? Personally, I suggest you go with a structure…

Hello @Agafiia Misonzhnikova That one doesn't look like our gadget. Probably, belongs to another app. For our gadget, please make sure you installed Time in Status by OBSS Timepiece - Time in Status for Jira EmreT

Hello @Junaid Moosa This is a really tough one to get. To start things small, you can use a JQL query like below to get the list of issues for a single day (or let's say a single time period): project = ABC and status changed FROM Open TO Resolved AFTER '2023-08-01 00:00' BEFORE '2023-08-02 00:00' But getting this as a…

Hello @de Angelis, Nicholas I see that you are trying to measure Lead Time with Automation. It is of course doable but there are several downsides to this approach. You will need to build and maintain this solution yourself (which is really expensive). You will need to build this for all different times you want to…

Hello @Juwairiyah Zia I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. This app can be used to get Cycle Time, Lead Time, Issue Age, Resolution Time, and some types of Time Tracking reports. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to…

Hello @Darya Kolyvanova There are many different built-in reports and charts in Jira. Each measures times in a different var but as far as I know, none of them take the Flag field into account and none of them exclude "flagged" times from their measurements. The plugin I mentioned above, Timepiece - Time in Status for…

Hello @arno Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics like Issue…

Hello @Jiten Khanna If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly has several types of time reports (showing how much time each issue spent on each status, assignee, or…

Hello @Darya Kolyvanova , If you want to get reports based on times when issues were flagged or not, I can recommend Timepiece - Time in Status for Jira which was built by our team at OBSS. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent…

Hello @Prashant K Sahni Jira's Cycle Time report considers both issues and commits. I believe this might be misleading but that is how Jira does it. A better approach would be to measure the Cycle Time based on Jira issue statuses. If you are OK with measuring this through Jira issue statuses, I can recommend a solution…

Hello @[deleted] Sorry, but you can't have this without an app. The closest you can get will be Jira's Issue Age Chart but it offers an overall view with very limited flexibility. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in…

Hello @Lee Rourke , You didn't indicate if you were using cloud or on-prem. If you are using on-prem, I can recommend our app Keychain to handle delegation-related matters. https://marketplace.atlassian.com/apps/1225037/keychain-delegation-for-jira With Keychain, you can set delegates for people and you can configure…

Hello @Hrishikesh I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee. Time in Status offers two report types for your case:…

Hello @Apurva Manjusha Kumar , Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get…

Hello @Sattar Baig Doing this with Automation is hard because you'll need to create separate custom fields and automation rules for all the times you want to measure. It will be expensive to build and maintain. In fact, all the data needed for this calculation is already available in each issue's history but Jira doesn't…

Hello @Aidin Mahmoodi _ServiceRocket_ Ideas are also represented with Jira issues underneath so anything that works for Jira issues should work for ideas too. Our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to…

Hello @[deleted] , Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics…