Emre Toptancı [OBSS] Atlassian Partner

Hello @Shirish Unfortunately, you can't have this report with plain JQL. JQL queries can filter issues but can't calculate resolution times. The "resolutiondate not in (-72h)" clause in your query filters issues where the resolution date (which is the date when the issue was resolved) is not in the last 72 hours. It…

Hello @Scott 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 group)…

@Barış Özer Bey Merhaba, 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 @[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…

Hello Phil, I don't know any other built-in gadgets but I guess you can use those built-in gadgets but run them with a query like... project = ABC and created >= -30d (which will only include the issues created in the last 30 days) ... or with a query like ... project = ABC and created > startOfMonth() (which will only…

Hello @zacharoula_brinia 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 @Smita Kalunge You are correct. Our app, Timepiece - Time in Status for Jira, needs to be installed as a separate app to your Jira. I am sorry since I am unable to provide help on easyBI functions. EmreT

Hello @Martin 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 see how much time each…

Hello @Smita Kalunge The data needed for such a measurement is present in each issue's history but Jira does not give this as a ready-to-use report. For that, you will need to use 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…

Hello @Emmanuel F-D , The data needed for such a measurement is present in each issue's history but Jira does not give this as a ready-to-use report. For that, you will need to use 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…

Hello @Lucile Cornet If you don't want to use an app, your best bet would be to get this data from Jira DB. It will be much more complex than running a simple SELECT query but it is technically possible. I suggest you use a marketplace app to get ready-to-go reports. Our team at OBSS built Timepiece - Time in Status for…

Hello @TN Raju As others have pointed out, this is possible but certainly not easy. You will need to build separate scripted fields for each status you want to see and it is a really hard calculation. Besides, this is not a cheap calculation to make by script. Remember, the script will run every time the issue is…

Hello @Venkata Sagar Ganesh Rao Mahendrakar, The data needed for such a measurement is present in each issue's history but Jira does not give this as a ready-to-use report. For that, you will need to use a marketplace app. Our team at OBSS built Time in Status exactly for this. It is available for Jira Server, Cloud, and…

Hello @Jennifer Arkell Jira does not provide this functionality out-of-the-box. JQL queries can "filter" issues but they can't make calculations and they do not show transition dates as columns in their result set. The data you need is available in each issue's history but Jira doesn't show this as a ready-to-go report.…

Hello @Klaus.Hasslinger The data needed for such a measurement is present in each issue's history but Jira does not give this as a ready-to-use report. For that, you will need to use 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…

Hello @Andrew Hardisty I can offer something better. The assignees of issues change over time. It can change even throughout the day. So seeing the number can be misleading. A better approach would be to see the time where the issues were unassigned. Our team at OBSS built Timepiece - Time in Status for Jira for this. It…

Hello @Sanjog Sigdel Jira does not provide this functionality out-of-the-box. JQL queries can "filter" issues but they can't make calculations and they do not show transition dates as columns in their result set. You are correct, the required data is available in each issue's history but you will need to use a marketplace…

Hello @prasad biddika I know you asked for a script solution but let me recommend an alternative since scripts are expensive to build and maintain. Using a ready-to-go marketplace solution will be cheaper and more comprehensive. Our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira…

Hello @Steven Janvrin Jira does not provide this functionality out-of-the-box. JQL queries can "filter" issues but they can't make calculations and they do not show transition dates as columns in their result set. You will need to use a marketplace app to get ready-to-go reports. Our team at OBSS built Timepiece - Time in…

Hello @Denise Ellis Jira does not provide this functionality out-of-the-box. All the data needed for this report is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira Server,…

Hello @Casper Jira does not provide this functionality out-of-the-box. You will need to use a marketplace app to get ready-to-go reports. 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 see how much time each…

Hello @Sowmiya Srinivasan I saw above that you said your company is also using Data Center. In that case, I can recommend Keychain - Delegation for Jira app that is built by our team at OBSS. This app allows all kinds of delegations scenarios to be realized on Jira, including JSM customer portal approvals.…

Hello @Paolo Motosso , For better flexibility and maximum details, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. Time in Status can create reports for both Company-Managed and Team-Managed projects. (It is available for Jira Server, Cloud, and Data Center.) Time in Status mainly allows you…

Hello @靳光光 , Jira keeps all transition dates in each issue's history but those values can't be obtained as an issue field. On any issue, you can only get create, resolution, and last updated dates as system fields. For better flexibility and maximum details, our team at OBSS built Timepiece - Time in Status for Jira…

Hello @Visa Kask , If you are using Jira Software, you can use the Control Chart that is available as part of Kanban Board reports. The Control Chart is built-in but it offers limited details and limited flexibility. For better flexibility and maximum details, our team at OBSS built Timepiece - Time in Status for Jira…

Hello @Gieroll Macaya I will point to some built-in Jira solutions and then recommend a marketplace app. First, you can get such a report using Jira's Resolution Time dashboard gadget. Second, if you are using Jira Software, you can use the Control Chart that is available as part of Kanban Board reports. Both of these…

Hello @Anthony Amirfar For Charts 3 and 4, our marketplace app can help you with some of your needs. 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 see how much time each issue spent on each status or each…

Hello @Hemang Dave JQL queries can't do this because JQL just filters issues. It can't perform calculations on issues or issue histories. I will point to some built-in Jira solutions and then recommend a marketplace app. First, you can get such a report using Jira's Resolution Time dashboard gadget. Second, if you are…

Hello @Ahmed Dahy I will point to some built-in Jira solutions and then recommend a marketplace app. First, you can get such a report using Jira's Resolution Time dashboard gadget. Second, if you are using Jira Software, you can use the Control Chart that is available as part of Kanban Board reports. Both of these reports…

Hello @Devender Singh , You can do this by simple filter subscriptions. Go to Jira's issue search screen. Search with a JQL query like below: project = ABC and status = Blocked and not status changed FROM Blocked AFTER -3d and assignee = currentUser() The query is pretty self-explanatory. This will filter the issues "in…