Birkan Yildiz _OBSS_ Atlassian Partner

Hey @Kim_Vencill If you are open to using a Marketplace app, you can easily get this exact average number using Timepiece - Time in Status for Jira. Here is how you can set it up to get your average cycle time number: Filter your Scope: Use the app's JQL filter option to select your specific issue types and the exact time…

Hey @Evie Z_ Thanks for the heads-up. I was aware of the rule around external links. However, before posting, I looked at a few previous App Central articles from other vendors and noticed that many of them included links to webinar registration pages. That made me think webinar links might be an exception, since they're…

Hey @Enrique BESUMAN BARCENAS Tracking how many times an issue bounces back to a specific status (like "Open") is crucial for identifying rework, but native Jira doesn't offer an out-of-the-box report to count these status re-entries without relying on complex automation rules. If you are open to using a Marketplace app,…

Hey @Martin Vali Native Jira dashboards are excellent for real-time reporting, but they generally reflect the current state of your issues. Natively, Jira does not easily allow you to take historical snapshots (like checking what a custom field value was at the exact end of last month) to build trend reports…

Hey @Avijit Nath When tracking "effort," it is important to first distinguish between manually entered worklogs (timesheets) and the actual elapsed time an issue actively spends in progress. If you are looking to track the actual elapsed duration automatically rather than relying on manual time entry, native Jira does not…

Hey @Rafael Marin First, welcome to the Community! When tracking "time invested," it is important to first distinguish between manually entered worklogs (timesheets) and the actual elapsed time an issue spends assigned to a person or entity. If you are looking to track the actual elapsed duration rather than manual…

Hey @paul Welcome to the Community, While native Jira captures all these changes in the issue history, extracting a clean report with exact timestamps and durations is natively difficult without manually parsing the changelog or using complex REST APIs. If you are open to using a Marketplace app, you can easily get this…

Hey @BAL GOVIND YADAV First, welcome to the Community! Trying to calculate durations while pausing the timer for specific statuses using native Jira automation and smart values can quickly become overly complicated and unreliable. If you are open to using a Marketplace app, you can easily achieve this exact use case…

Hey @sravani vennapusa First, welcome to the Community! Native Jira calculates the total time from creation to resolution, but it doesn't natively allow you to pause the timer for specific waiting statuses like "On Hold". To calculate this accurately without complex workarounds, you can use the Duration Between Statuses…

Hey @Jules McCool First, welcome to the Community! If you are open to using a 3rd party app, Historian - Issue History for Jira can help you build this exact report. Here is how its features solve your specific requirements: Selecting Work Items via JQL: You can enter your JQL query in the search box to limit the report to…

Hey @송지현 First of all, welcome to the Community! You have run into a very common and frustrating limitation with native Jira dashboards. If you are open to using a Marketplace app to get a clean, accurate view, you can easily bypass this clutter using Timepiece - Time in Status for Jira. Timepiece includes a highly…

Hey @Corinne Guibert Native Jira dashboard gadgets are great for high-level overviews, but they don't natively calculate the average duration between two specific date fields to display as a dashboard metric. If you are open to using a Marketplace app, you can easily build this exact view using Timepiece - Time in Status…

Hey @joshalexandre Native Jira's metrics are great for a quick pulse check, but they generally rely on fixed rolling windows and don't allow you to easily "zoom out" to analyze historical trends over custom periods. If you are open to using a marketplace app, and if your pull request and review process is mapped to your…

Hey @Harry Foreman First, welcome to the Community! To get a reliable, historical per-status breakdown for individual tickets without complex workarounds, the most effective approach is to use a dedicated reporting app. Timepiece - Time in Status for Jira by OBSS is one of the most established and reliable tools in the…

Hey @Soma Rohit Welcome to the Community. If you are open to using 3rd party apps you can use Timepiece- Time in Status for Jira You can track the real-time running age of an open issue using the Duration Between Statuses report in Timepiece. You can easily select the Duration Between Statuses report type. Click the…

Hey @Placid Cardoz Native Jira tracks these changes in the issue history, but as you've experienced, exporting that granular transition data into spreadsheets usually results in empty or unparseable columns. For this exact metric, a dedicated reporting app is the most reliable solution. Full disclosure, I'm on the team…

Hey @Alex Cook To answer your first question: natively, yes! Jira has a built-in "Date Time Picker" custom field type. You can create your Start Time and End Time fields using this specific type to capture both the date and the exact time for your RFCs. However, if your goal in "tracking" is to calculate the actual…

Hey @Babar Brohi While Jira Automation is a common workaround, it can hit execution limits and require significant maintenance for every field you want to track. If you are open to using a marketplace app, a more direct, real-time solution is SearchMate - Advanced JQL Search for Linked Issues. I work for the team that…

Hey @mr john You have 3 options. However, for full precision and ease of use, a dedicated marketplace application is the most effective solution. Native Jira Native Jira reporting, such as the Control Chart or the Time Tracking Report, provides basic insights into issue lifecycles. However, these tools generally operate on…

Hey @Nathan Parfitt There are many different Time in Status apps available in the Atlassian Marketplace, and from your question it’s not clear which one you are using. Each app is developed by a different vendor, so troubleshooting steps can vary. If the app you are referring to is Timepiece - Time in Status for Jira, you…

Hey @ckopanon Native Jira cannot easily give you a report of every single update made by a user, nor can it filter out specific types of updates (like Tempo time logs) directly from your search results. If you are open to using a 3rd party app, Historian - History Explorer for Jira can help you achieve this. Here is how…

Hello @Jairo Monteiro , You can build a custom solution using the Jira REST APIs, but it can become a lengthy and time-consuming project. You’d need to pull issue changelogs and parse them to extract the data you need, which can be complex and error-prone. If you prefer a faster and more reliable option, you might consider…

Hey @Mary Doherty Native JQL is great for searching, but it cannot calculate the elapsed time between status transitions. Getting a straightforward list of individual issues with their specific cycle times natively usually requires complex automation workarounds or manually exporting data to Excel. For a simple,…

Hey @Lira Martynenko First, welcome to the Community! You are definitely not alone in this. Trying to calculate Time in Status and roll it up to the Epic level using Jira Automation is notoriously difficult and unreliable. For this specific use case, a dedicated reporting app is a much simpler approach. Full disclosure,…

Hey @Agustin Etman First, welcome to the Community! For this exact requirement, a dedicated reporting app is a much simpler solution. Timepiece - Time in Status for Jira handles this calculation automatically without any automation rules. Instead of trying to force calculated values into a custom field, you can use our…

Hey @Ashwin Kurundkar To see the time a bug issue spends in each workflow status and the exact transition timestamps directly in Jira, you would normally need to review each issue’s history. However, doing this manually is time-consuming and error-prone. Instead, you can use Timepiece - Time in Status for Jira. To…

Hi @Lira Martynenko First of all, welcome to the Community. You’ve hit on a major challenge. Native Jira reports often feel like they’re designed for Scrum Masters rather than the leadership team. To get the executive-level visibility you need, I highly recommend Timepiece - Time in Status for Jira. It’s built to provide…

Hey @omid sh Welcome to the Community! For this exact scenario, using a dedicated app that calculates the data and feeds it directly into eazyBI might be the best approach. Timepiece - Time in Status for Jira handles this exact calculation seamlessly. Here is how Timepiece solves your specific requirements: Accurate Cycle…

Hey @Deepali Dabholkar If you are open to using a marketplace app, Timepiece - Time in Status for Jira can help you achieve this. To track Sprint and PI performance without using story points, focus on duration-based metrics that identify how work flows through your iterations. Tracking Sprint Performance For individual…

Hey @Urmila Ghosh Welcome to the Community! Checking the history tab for every single issue to count status changes manually is exhausting. While JQL can find issues that were in a status, it doesn't easily give you a count of how many times it happened. If you are open to using a 3rd party app, Timepiece - Time in Status…