Birkan Yildiz _OBSS_ Atlassian Partner

Hey @Ashraf B , You've run into one of the most common and frustrating challenges with that approach: the Jira Automation run limits. When you have a busy project, those rule executions disappear quickly. For this exact problem, a dedicated reporting app is often a simpler and more sustainable solution. Full disclosure,…

Hello @Dan Allenby That's a great set of questions. You're looking for some very specific and valuable KPIs that, as you've discovered, go beyond what standard JSM reports can easily provide. For this level of granular, time-based analysis, a dedicated reporting app is often the best path forward. Full disclosure, I'm on…

To avoid double-counting or data overlaps, use the AVERAGE function instead of SUM. This will show you the average time an Assignee dedicates to an EPIC each month. For more detailed information, book a demo with us, and we'll work through your specific use cases during the session. 

Hey @mborinstein Calculating the total time each engineer contributes to an epic is a powerful metric, but it's not something you can get with native Jira reports. This is a perfect use case for a Marketplace app. Full disclosure, I'm on the team that makes Timepiece - Time in Status for Jira, and it can create this exact…

Hey @ckopanon That's a great question. It's a very common reporting need, but unfortunately, native JQL can't perform calculations between two date fields like created and resolved. This is a classic scenario where a Marketplace app with advanced reporting is the most direct solution. Full disclosure, I'm on the team that…

Hey @Sean Martin That's a great question, and you've correctly identified a frustrating limitation in Jira's native filter subscriptions. While you can get the results in the body of an email, there's no built-in way to get them as a CSV attachment automatically. For this kind of automated report delivery, a Marketplace…

Hey @Natalie Keane It is free for up to 10 users. For detailed information, please visit the pricing page. Also, please let me know if you have any further questions about Timepiece. Happy to help.

Hey @Natalie Keane That's a great question. Getting automatic weekly reports ( or daily, monthly) is a common need that can be tricky with Jira's built-in tools. But, if you are open to using a marketplace app, Timepiece - Time in Status for Jira’s ‘'Scheduled Reports & Alarms’' feature is built exactly to make this…

Hey @Asif Khan While Jira dashboards are powerful, they are often limited by the data they can display out of the box. A Marketplace app is usually the most direct solution for the kind of deep-dive reporting you're looking for. Timepiece- Time in Status for Jira’s ‘'Assignee Duration’' report is great feature to track…

Hey @Abhinav Welcome to Community! The native timesheet report is great for tracking logged hours, but it isn't designed to give you a simple count of all the different issue types created in a month. If you are open to using a marketplace app, Timepiece - Time in Status for Jira is built to create exactly the kind of…

Hi @Ken Saey You can easily achieve your goal by using a third-party app. I recommend TicketBook - Service Time and Contract Management for Jira, developed by my team at OBSS. While Ticketbook doesn't display per-ticket estimation fields or live SLA timers, it is designed to provide a more powerful, high-level view of the…

Hey @sunil Kumar BV , Jira's built-in features can fall short of getting the data you want. So, if you are open to using a marketplace app, Timepiece - Time in Status for Jira’s Status Duration report will give you exactly what you're looking for. It provides a clear breakdown of how long each issue spent in every status…

Selamlar @Orkun Ovayurt Bey, If you are open to using a marketplace app, Timepiece - Time in Status for Jira is what you are asking for. Its Duration Between Statuses report is designed to do exactly what you need. You can simply select the first status (e.g., To Do) as your start point and last status (e.g., Resolved) as…

Hey @khushboo_puri Jira’s native Time in Status reports can be problematic. There are no custom calendars, report types are limited, and export restrictions often make it hard to get accurate data. If you’re open to a Marketplace app, you might want to check out Timepiece – Time in Status for Jira. It has custom calendars,…

Hello @Augu J N Automating the calculation of key metrics and getting them directly onto your issues is a common need, and for that, a powerful time tracking app is one of the most effective solutions. If you are open to using a 3rd party app, Timepiece - Time in Status for Jira can directly help you with this. Calculating…

Hey @Ramya First, welcome to Atlassian community :) It is a common need for many teams. You can try ‘Filter’ subscriptions for sure. But, if you want more detailed reports, custom calendars, use your automated reports as a warning system, and also deliver them with Slack, email, and MS Teams, you can also try Timepiece -…

Hello @Sara Yasser While T-shirt sizing is a good way to start conversations about effort, for Kanban capacity planning, a more direct approach is to use your team's historic performance data. This shifts planning from guesswork to forecasting based on facts. You can focus on 2 metrics: Throughput: How many work items does…

Hey @Brad Schultz While this data is available in the Jira issue history, generating a proper report from it requires a third-party reporting tool. The good news is that the report is available in our application, Timepiece - Time in Status for Jira. With the app, you can directly learn the status counts without having to…

Happy to hear that @Édpo César Please let me know if you have further questions. 

Hi @Dinakaran R That's an excellent question. Being able to sort issues by age or SLA status is a common and important goal. While a calculated custom field might seem like the direct solution, that approach can cause significant performance issues and data staleness, as the values don't update in real-time. If you are…

Hello @Édpo César Calculating the time a ticket spends assigned to each value of a custom field is a key reporting requirement for measuring team performance. Jira's native reports can show a field's current value, but are not designed to calculate the total time an issue has spent with each previous value. A specialized…

Hello @Hamsa Ranganathaiah Great question and you’re definitely not alone! Understanding the difference between Lead Time and Cycle Time, and then visualizing them correctly in Jira, is a common challenge for many teams. Let’s quickly clarify the concepts: Cycle Time is the time it takes to complete a task once work has…