Emre Toptancı [OBSS] Atlassian Partner

Hello @Harrica Rion , In short: No, Jira doesn't give this data as a ready-to-use report. Since you are on the cloud, you can't query this data directly from the database. The only option to get this raw data is to get it via Jira public REST API. Most Jira users try to get this data because they want to see how much time…

Hello Aryeh, I totally understand your concern. As I said, Time in Status data for individual issues is currently only available on Jira Boards as a tab on the issue detail view. If you want to display the ticket age on the ticket card on the board, that is not possible at the moment. "Displaying the ticket age on the…

Hello @Ash Viceer, Jira's Control Chart offers limited details and flexibility in terms of report parameters. The dots in the board view are also not very precise. For maximum details and flexibility, you should use a marketplace app. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece -…

Hello @Omri , In short: No, JQL does not offer this functionality out-of-the-box. Yes, you will need a plugin for that. And a longer answer: JQL does not have this. Even if it did, it would be a very expensive JQL query to run since calculating this would require not only issues but also issue histories to be processed.…

Hello @Aryeh Schwob , Time in Status by OBSS has Filter and Sort options which will allow you to filter or sort issues based on time spent in a status. You can see the documentation about these features here and here. You can also see small demo videos of those features here and here. These features are available on both…

Hello @ivana.papacek , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. The app has Consolidated…

Hello @Michael E I don't have anything that will make Control Chart show the correct values but I can recommend the Timepiece - Time in Status for Jira app built by my team at OBSS which has two features that might help you. In summary, Time in Status allows you to see how much time each issue spent on each status. The app…

Hello @Tony Thomas , We developed an app that solves this problem in a more comprehensive way, without changing the assignee. I suggest you take a look at Keychain - Delegation for Jira by OBSS. With Keychain, you can set delegates for people and you can configure workflows and schemas that allow those delegates to perform…

Hello @Brandon Ivey In the script route, you will need to build separate scripts for each metric and as the number gets higher, it is a nightmare to maintain them. I don't have a script but I do have an app recommendation. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in…

Hello @David Verbeure , 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 @Juan Manuel Ramos Taboada , Jira does not have an out-of-the-box report that shows individual status times. If you are interested in overall resolution times, Issue Age Report or Control Chart (of Kanban Boards) might be useful up to a degree. It is worth noting that these options offer limited details and limited…

Hello @Ariel Perez , Sory I can't respond in Spanish but I believe I have the perfect solution for you. For a ready-to-use report, the use of a marketplace app is needed. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for…

Hello @Suma Kustagi , I will recommend Time in Status 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. The two important features of our app that applies to your use case are: * You can filter…

Hello @Lisa Stewart Jira does not have an out-of-the-box report that shows individual status times. If you are interested in overall resolution times, Issue Age Report or Control Chart (of Kanban Boards) might be useful up to a degree. It is worth noting that these options offer limited details and limited flexibility. In…

Hello @Jason Liu You can try building a solution with Automation but it will have to be replicated (and maintained) for each timespan you want to report. And it will not work for your past issues. On the other hand, the data needed to calculate this report is available in each issue's history. I can recommend Timepiece -…

Hello @Kyle McGee , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. You…

Hello @Sreenadh If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need and it also has a free tier. Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee. The app has Consolidated Columns…

Hello @Evalaji Jones , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. The…

Hello @M C If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center. Time in Status will help you to see Lead Times easily (including past issues), filter the ones above or below a given time…

I am afraid not. My team at OBSS are the builders of one such app,Timepiece - Time in Status for Jira. Jira issue histories are the only place that data about this can be found and when it is corrupt, there is nothing anyone can do. This bug also corrupts our reports. The only way forward seems to be to consider any…

Hello @Alex Eldridge , I guess this is caused by a known JCMA bug. While migrating from on-prem to cloud, all Jira entities (and especially statuses in this case) get new IDs but the IDs for changes in issue histories are not updated accordingly. In other words, histories of issues migrated from the source system are…

Hello @Torres, Rodolfo (R.) Jira's own Control Chart offers limited details and flexibility. In order to get more details, you'll need to check each issue's history independently. If you want to get better reports with more flexibility and details, I suggest you use a marketplace app. If you are OK with using a marketplace…

Hello @Justin Princehorn , Your understanding of the app is correct. Every team can prepare a Time in Status report that shows Cycle Time (or any other metric) in a way that is meaningful for them. All numeric report types of Time in Status can be configured to show a List of issues or Averages. Average reports also can be…

Hello @Justin Princehorn , Your question is a nuanced one. You are basically asking how Jira calculates metrics if an issue visits a status multiple times. Jira has multiple reports and gadgets that show this kind of information. One of them is the "Days in Column" show on boards. But there is also Issue Age Chart in…

Hello @Naresh Gantala , It will be very hard to get this with just out-of-the-box Jira features. You can try the Issue Age report/gadget or the Control Chart (which is available as part of Kanban boards if you have Jira Software). But these options offer an overall picture and limited flexibility. If you are OK with using…

Hello @Soham Das This is not available in out-of-the-box Jira but you will be able to get status or assignee based reports with the help of a marketplace app. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this need. It is available for Jira Server,…

Nope, doesn't work. This one returns a value: {{webhookResponse.body.table.body.rows.valueColumns.value.get(0)}} But when you chain an "asNumber", it returns empty: {{webhookResponse.body.table.body.rows.valueColumns.value.get(0).asNumber}} You know what? I tried the same thing with original estimate field. The smart value…

Hello @Bill Sheboy , Below is the complete smart value that we are trying to use with Edit Issue action to update the duedate field. {{now.plusDays({{#=}}round({{asNumber}}{{webhookResponse.body.table.body.rows.valueColumns.value.get(0)}}, 0){{/}})}} As you can see, we are trying to round some value from the json result of…

Hello @John Funk , We did this on the cloud platform just as you said, with a variable. But there is no Create Variable action on Jira DC. Is there a workaround? EmreT

Hello @Mohamed Saad Taha , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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.…