Ayça Erdem_OBSS_ Atlassian Partner

Hello @Amrik Birdi The next step for our product team is to port this feature to the Data Center edition of Timepiece. You can send an e-mail to appsupport@obss.tech to get more information on the subject and also be notified when the capability is ready for the DC edition. Just let me know if you have any additional…

Hello @Rupendra Vengurlekar Welcome to the community That’s a great question. Jira doesn't provide built-in support for tracking metrics like Cycle Time, Lead Time, or Time in Status out of the box especially not in a visual dashboard context with flexible x-axis configurations. If you're open to using a third-party app,…

Hello @Gaurav Chandra Tiwari Welcome to the community If you're looking to get a list of all tickets that were reopened at least once, regardless of their current status or position in the workflow, I'd recommend checking out Timepiece - Time in Status for Jira, developed by our team at OBSS. With the Status Count Report…

Hello @Lareb Umer Welcome to the community Thanks for bringing this up. If you're open to using a third-party app, I’d recommend Timepiece – Time in Status for Jira, developed by our team at OBSS. It helps you analyze metrics like task completion time, workload by assignee, and issue reopen patterns in a flexible and…

Hello @Mohith Tummala You're right the Jira Cloud REST API doesn’t provide a direct way to retrieve the timestamp of a specific status transition without expanding the changelog. If you’re open to using a third-party app, I’d recommend checking out Timepiece - Time in Status for Jira, developed by our team at OBSS. It…

Hello @Olivia Reed Welcome to the community Great to hear that you're exploring ways to track time and attendance more effectively, especially in remote or hybrid setups where visibility is key. If you're open to exploring issue-based time tracking within Jira, I’d recommend checking out Timepiece - Time in Status for…

Hello @Rick Love We assume you're referring to a time in status Jira dashboard gadget. If you're open to using a third-party app, I can recommend the Timepiece gadget from the Timepiece - Time in Status for Jira app, developed by our team at OBSS. While there isn’t a separate “exclude statuses” setting in the gadget, you…

Hello @Ronald Lam When you configure an SLA like "Time to Resolution," Jira will only calculate that metric for issues that are still within the SLA timeline at the time of configuration. Tickets that were already closed before the SLA was added will not have this field populated. If you want to measure SLA metrics (such…

Hello @Ajay thirth Welcome to the community. If you'd like to report on how many times issues have moved backwards from QA or UAT to a status like "Fix needed", I recommend using a third-party app like Timepiece - Time in Status for Jira developed by our team at OBSS. Timepiece offers a Transition Count Report, which shows…

Hello @Pavan Thota iGTB Welcome to the community You can get both the time a defect spent in a specific status (e.g. “Resolved”) and its overall Issue Age using Timepiece - Time in Status for Jira, the oldest and leading "Time in Status" app in the Atlassian Marketplace, which is developed by my team at OBSS. It is…

Hello @Phil If you're looking to display the Issue Age the total time an issue has been open since its creation you can easily do this using Timepiece - Time in Status for Jira, developed by our team at OBSS. Using the Duration Between status, you can define a metric that includes all statuses an issue can go through while…

Hello @Julio Martinez Prieto You can get a basic count of how many times tickets transitioned from “ UNDER REVIEW to IN PROGRESS using an app. If you're open to using a third-party app, I can recommend Timepiece - Time in Status for Jira, developed by our team at OBSS. For a detailed report showing how many times each…

Hello @Sharon Robinson Welcome to the community If you're seeing an unexpected gap in your cycle time trend chart especially when working with a large dataset across many projects I would recommend trying Timepiece - Time in Status for Jira, developed by our team at OBSS. It allows you to explore these kinds of gaps in a…

Hello @Raunak Maskay There is no built-in SLA feature in regular Jira – SLA metrics like response and resolution time tracking are only available in Jira Service Management.However, with Timepiece - Time in Status for Jira, developed by our team at OBSS, you can bring SLA-like tracking into any Jira project. Using the…

Hello @Jeniffer Kamaraj I understand that Jira's built-in JQL does not allow filtering based on SLA fields like “Time to Resolution”. If you're looking for a way to analyze or replicate resolution time metrics outside the SLA framework or JQL, I can recommend Timepiece - Time in Status for Jira, the oldest and leading…

Hello @Bhuvaneswari Vasudevan If you're looking to track how much time is spent on product discovery ideas in a JPD project — but don’t want your product managers to manually log hours — here’s a helpful workaround: Use “Status Duration Times” instead of time logging Timepiece - Time in Status for Jira, the oldest and…

Hello @Nicola Biagi Welcome to the community I understand you're looking to track how multiple people contribute to a single Jira task a common need when issues are handed off between teammates, but Jira allows only one assignee per issue at a time. To solve this, I’d recommend using a third-party app, as Jira doesn’t…

Hello @Claire Abt Welcome to the community It sounds like you're trying to monitor how your work items move through the workflow, particularly how often they enter the Input Required status and how long they stay there — especially in cases where tickets go back and forth multiple times. Jira’s issue history does contain…

Hello @ranjanajindal I understand that you are not looking for a paid solution right now. However, if you ever need it I can recommend Timepiece - Time in Status for Jira, the oldest and leading "Time in Status" app in Atlassian Marketplace, which is built by my team at OBSS. It is available for Jira Server, Cloud, and…

Hello @Sherwin Soriano There is no built-in SLA feature in regular Jira – SLA metrics like response and resolution time tracking are only available in Jira Service Management. However, with Timepiece - Time in Status for Jira, developed by our team at OBSS, you can bring SLA-like tracking into any Jira project. Using…

Hello @Sherwin Soriano There is no built-in SLA feature in regular Jira – SLA metrics like response and resolution time tracking are only available in Jira Service Management. However, with Timepiece - Time in Status for Jira, developed by our team at OBSS, you can bring SLA-like tracking into any Jira project. Using the…

Hello @Alison Files Jira's native JQL has limitations when it comes to calculating dynamic durations, such as determining if an incident took more than "x days" to close. However, if you're open to using a third-party app, I highly recommend Timepiece - Time in Status for Jira, developed by my team at OBSS. With Timepiece,…

Hello @Amy Chamberlain Many apps offer cycle time tracking, but often with rigid definitions that don’t fit all use cases. If you're looking for maximum flexibility to define what Cycle Time means for your team, I’d strongly recommend taking a look at Timepiece - Time in Status for Jira, developed by our team at OBSS.…

Hello @Saidamir Kobiljonov Welcome to the community! There is no built in solution in Jira for this. So in order to track the time spent on each status & each assignee I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is…

Hello @Amit Mohide Welcome to the community! Jira doesn’t offer a built-in way to track how much time each issue spends in different statuses. To get this kind of insight, I recommend using a marketplace app. Timepiece - Time in Status a, developed by my team at OBSS, is the oldest in the Atlassian Marketplace for this…

Hello @Miriam Grühn For your questions, Jira Cloud, unfortunately, doesn’t offer a built-in way to customize when time tracking should start or pause based on status transitions. The default “Time to resolution” or “Control Chart” reports will count from when the issue is created until it's resolved, regardless of your…

Hello @Peter Neuhaus Welcome to the community You can use a JQL query like the following to filter issues based on their creation date: <span>created >= -7d</span> This will return issues that were created in the last 7 days.If you're looking to identify when an issue transitioned to a certain status, you might want to…

Hello @Daniel Hill Welcome to the community Tracking support KPIs like First Response Time or Time to Resolution in Jira alone can be quite challenging. However, if you ever need it I can recommend Timepiece -Time in Status for Jira , the oldest and leading "Time in Status" app in Atlassian Marketplace, which is built by…

Hello @Sara Naddaf it’s a common issue, especially in team-managed projects. So, in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report…

Hello @Moheb Hedayat Welcome to the community What kind of data are you trying to report on, and how do you like to visualize it? I can offer a solution. Timepiece - Time in Status for Jira, developed by our team at OBSS, retrieves data directly from Jira issue history. This means you can generate reports for your entire…