Comments
-
Hi @Dhruti Shah You can track the duration between onboarding steps in Jira, but it might take a bit of setup. Since your data already includes timestamps for when companies enter each stage, you could use Jira Automation to calculate and store the time spent between statuses. This would involve setting up rules to capture…
-
Hello @Christopher Curio welcome to the community! If you're looking to track and control the total time spent on a project rather than at the ticket level, many time-tracking tools primarily focus on individual worklogs, making it challenging to get a project-level overview with predefined limits. While Timepiece - Time…
-
Hello @Akhand Pratap Singh Normally, JQL does not support the use of business days, which makes it challenging to set up automation based on working days alone. However, Timepiece - Time in Status for Jira, developed by our team at OBSS, provides a solution for this. By configuring your company calendar in the system, you…
-
Hello @Khai Ha To track how long issues have spent in the In Review status , I’d recommend considering Timepiece - Time in Status for Jira, developed by our team at OBSS. While your automation idea is great, Timepiece can serve as an essential input source for your automation by accurately tracking and reporting the time…
-
additonally i would like to add
-
Hello @L Thank you for reaching out and for providing the details about your issue. It seems like the Average Time in Status report may not be delivering the insights you need, and we understand how critical such metrics can be for your workflows. Our Timepiece - Time in Status for Jira app, developed by our team at OBSS,…
-
Hello @Ryan Peck You’ve already found the solution to your issue, but I wanted to share an alternative option that could also help address this challenge. Thank you for sharing your question and update! It seems like you encountered a common challenge with calculating accurate time durations for statuses that a ticket has…
-
Hello @Pablo Gómez Justicia Unfortunately, Jira's built-in SLA counters do not allow for retrospective calculations. SLA timers start when the SLA is triggered for an issue and only track durations moving forward. This means it is not possible to query or report on SLA breaches or durations for issues whose SLA endpoint…
-
Merhaba Aylin Tüzel Yücel, Welcome to the community! To find the total time spent on a project in Jira, I recommend using a third-party app since Jira’s native reporting tools have limited capabilities for comprehensive time tracking. My suggestion is Timepiece - Time in Status for Jira, the oldest and leading time in…
