Emre Toptancı [OBSS] Atlassian Partner

@Oliver Siebenmarck _Polymetis Apps_ Atlassian documentation doesn't mention which Segment source to use for this integration. I am inclined to use "JavaScript" or "HTTP API" sources, but so far, no luck with either of them. Could you provide any direction about this?

Unfortunately, no. The way custom fields work on the Cloud is vastly different from DC. Jira's technical structure doesn't allow the same solution to be applied on the Cloud. However, we are always on the lookout, searching for ways to bring this solution to the Cloud.

@Kate C_ Great news, thanks.

Hello @Bernard Horowitz , Doesn't that contradict with "moving" the issue to a new project? I mean, if you are moving an existing issue, obviously you want to keep that issue so the original create date stays as it is. If you want a new create date, you can either create a new issue in the new project or (if you don't…

Hello @George Abdo Jira's own Issue Age and Resolution Time charts/gadgets offer limited flexibility and details. For maximum flexibility and details, I suggest you use a marketplace app for this. Even if you don't plan to purchase the app, you can use it to cross-check its results with Jira's own charts. Our team at OBSS…

Hello @Nitzan Goren I don't know of any built-in way or a way introduced by an app to do this exact thing in Jira. Our app Timepiece - Time in Status for Jira might help as a workaround. It is a long shot but might be worth mentioning. Time in Status is a reporting app that mainly allows you to see how much total time each…

Yes, a rich assortment of different errors. The excitement never ends.

Hello @Patricia Modispacher _k15t_ , Emre TOPTANCI from OBSS here. We are the makers of Timepiece - Time in Status for Jira app you mentioned in your article. Thank you very much for such a comprehensive article. I am sure many community members will benefit from it. I'd like to add something: Timepiece - Time in Status…

Hello @Anna Voiniush , 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 @Michael Goslee , 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 @Balaji K M 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 @Jahnavi Pathak 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. Time in Status offers two report types for your case: The first one is…

Hello @Dora Judith Martínez Vera , Resolution Time and Work Logs are two completely different things. Resolution Time (or any other similar metric) measures how long it took for the issue to move from one status to another (for Resolution Time, it is probably the time from Open to Resolved). Worklogs however are the time…

Hello @Rob Manger , You didn't mention which Time in Status app you are using. I certainly hope it is Time in Status by OBSS. For your case, Time in Status by OBSS has the Any Field Duration report that can do duration measurement for any issue field. If you are looking for Flagged/Unflagged dates to measure the duration…

Hello @Jahnavi Pathak , Jira with its out-of-the-box features can't do this. You either have to build customer automation rules or use a marketplace app for this. 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…

Hello @Nikita Simakov , You can use JQL query like... project = ABC and assignee was john.doe ... to filter our issues that were assigned to a specific person in the past. We have an app that might help you in another way. Our team at OBSS built Timepiece - Time in Status for Jira for requirements similar to this. It is…

Hello @Mario Amaya Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It works with all editions of Jira and 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…

Hello @Francisco Duarte Sorry that I can respond only in English. You can't do this with out-of-the-box Jira. JQL only filters issues but it can't make calculations on issue histories. To get this report you will need a marketplace app. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is…

Hello @Laura Merino Diez As others have pointed out, Jira does not give this as a ready-to-use report. You should use a marketplace app for this. If you are OK with using a marketplace app, our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center.…

Hello @Yuliyani , Jira's own Average Age Chart, Resolution Time Chart and Control Chart offer very limited flexibility and details. For more, you should use a marketplace app built for this purpose. If you are OK with using a marketplace app, our team at OBSS built Time in Status exactly for this and it is free for up to…

Hello @Shmuel , As others have pointed out, Jira has limited out-of-the-box capabilities for such a report. Use of a marketplace app is recommended. 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…

Hello @Giulia Carletto Going back and forth between InProgress and Review is some kind of "reopen" action and any reopen should be inspected if you suspect a problem. As others have pointed out, you can use JQL's CHANGED operator to find issues that was moved from one status to another at least once, but counting reviews…

Hello @Dani Bonilla , 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,…

Hello @Kevin Paul , I am from OBSS, the vendor of Timepiece - Time in Status for Jira app that you asked about. The screenshot you've sent is from a dashboard gadget so it shows very limited data in terms of your report configuration. If you click the "View in Time in Status" link at the bottom of the gadget, it will open…

Hello @jiandong.luo , Jira's own Average Age Gadget, Resolution Time Gadget, and even the Control Chart offer very limited flexibility and details. For maximum details, you should use a marketplace app for this. If you are OK with using a marketplace app, our team at OBSS built Timepiece - Time in Status for Jira exactly…

Hello @Mark Geris Building a custom automation will most likely be hard to build and maintain. So it will be expensive. I suggest you use a marketplace app for that. 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…

Hello @Robert Ortega , First, the region has to be represented on your issues in some way. For example, you can create a Select List field named "Region", put all possible region names as options for this field, add this field to your tickets, and make sure all tickets have a value for this field. After that, you can set…

Hello @Marco_Artioli , I guess you want to define SLAs based on who the customer of a given ticket is. In that case, first, the customer has to be represented on your issues in some way. For example, you can create a Select List field named "Customer", put all possible customer names as options for this field, add this…

Hello @Giorgi Tsitsvidze You might find custom scripts to do this with Jira fields but I don't recommend that one. Simply because it will be hard to build and maintain such a solution, you will need to introduce a separate field for each metric you want to track and each workflow you want to put it on. Most importantly,…

Hello @Kris Olds , I don't know if you can do this with EasyBI but I have the perfect solution that works within Jira. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. You can even use our app's REST API to get the calculated data programmatically and push it into EasyBI. First, a small…