Valeriia_Havrylenko_SaaSJet Atlassian Partner

Hi @Kashif Rahman To effectively create a per-agent performance dashboard for your service desk, you can use a combination of Jira’s built-in reports and add-ons for enhanced insights. Here’s how you can approach it: 1. Dashboard Configuration Use Jira’s Built-in Reports: Velocity charts, SLA reports, and custom dashboards…

Hi @Jayanth Jira Automation has some limitations when it comes to calculating time spent in a status while considering only business hours and days. While you can track status entry and exit times using automation rules, Jira doesn’t natively support excluding weekends or non-working hours from these calculations. I…

Hi @Randy O'Neal 👋 You're right that Jira doesn’t allow direct edits to the historical start time for an issue’s status transitions. However, if you're open to using an add-on, Time Metrics Tracker | Time Between Statuses can help by calculating time spent in each status based on actual transitions, rather than Jira’s…

Hi mohsen.nasiri@xentral.com Welcome to the community! If you're open to trying another app, I’d recommend Time Metrics Tracker | Time Between Statuses . It’s specifically designed to measure time metrics like Resolution Time—from issue creation to resolution—without requiring custom fields or complex JQL. With Time…

Hi @Anas Mughal Welcome to the Community! I suggest you to try Time Metrics Tracker | Time Between Statuses that specially build to log time spent when the task goes from one status to another. In add-on you can calculate time between metrics precisely by choosing firs or last transitions and exclude statuses you do not…

Hi @Khai Ha 👋 Also solution can be Time in Status add-on. Which allows you to view the entire duration of an issue, from the time it was opened until it was closed, with the Time in Status report. You can also book a live demo - we'll show you the application inside out and answer all your questions. Add-on created by my…

Hello @Digvijay Singh Gehlot , Since Jira’s native JQL does not support exact duration conditions (e.g., "status = Open for exactly 90 days"), we need a workaround. Your current JQL query: project = TEST AND issuetype = Story AND status = Open AND NOT status CHANGED AFTER -90d This query returns all issues that have been…

Hi @Nguyen Le Thanh_Candylio Welcome to the community! Jira natively does not provide a way to track SLA breaches per user, however, you can achieve this with the Time Metrics Tracker | Time Between Statuses add-on. It allows you to measure how long each user has worked on a ticket and identify who contributed to an SLA…

Вітаю, @Вікторія Краснова Вітаю на Atlassian Community! Як вже зазначали нижче, у Jira всі користувачі в межах однієї підписки мають один і той самий план. Щоб зрізати кости, поширений варіант - створення окремих Jira з різними планами. Також, якщо вам треба мати всі дані в одний Jira, можливовам підійте варіант…

Hi @Myles Boyd You're correct—Jira’s "Time to Resolution" SLA field counts backwards from the goal, rather than giving you the actual time an issue spent in the workflow. Unfortunately, Jira doesn’t provide a built-in way to calculate true resolution time (i.e., the total time an issue was in an active state).…

Hi @Pablo Gómez Justicia You're on the right track with your query, but Jira’s SLA fields behave differently depending on whether the SLA is ongoing, paused, or completed. The issue likely arises because Jira doesn't expose SLA completion times in JQL natively—only elapsed time for active SLAs. Since JQL does not allow…

Hi @GCushnahan and great question! Option 1: Check Issue History Manually * Open an issue → Go to the History tab under the Activity section. * Look for the timestamp when the status changed from Backlog (or To Do) → In Progress. Option 2: JQL to Find Issues That Recently Moved to In Progress status CHANGED TO "In…

@Farid H. Nia happy to help!

Hi @Michael Ryan 👋 Welcome to the Community! If you're looking for a way to analyze sprint performance over multiple sprints and Sprint Report from Time in Status can be a great solution. How Time in Status Sprint Report Can Help: Multi-Sprint Analysis – View trends over the past 6 sprints (or more) to identify peaks and…

Hi @Dheeraj.Kottapalli 👋 Welcome to the Community! If you're looking for a way to track and visualize issues from both completed and ongoing sprints on a single dashboard and open to the add-ons, you might find the Sprint Report from Time in Status useful. Sprint Report provides insights into sprint performance, including:…

Hi @Farid H. Nia Welcome to the Community! If you are interested in time reports and ope to add-ons, option for you can be Time in Status. To show report when a user story is moved from "To Do" into "in Progress", just: * Choose Status Entrance Date report * Filter by Project, Assignee, Sprint etc. * Filter issues by Data…

Hi @Abhishek Ashok Dingre Welcome to the Community! If you’re open to using add-ons, it is possible to calculate how much time we took for a user story to move from "Approved by Dev" status to "Completed" with Time Metrics Tracker | Time Between Statuses Here’s how you can achieve this: 1. Create a new metric and name it…

Hi @Naresh Rajak If you’re open to using add-ons, it is possible to show how many days since status was first changed to 'In Progress' with Time Metrics Tracker | Time Between Statuses Here’s how you can achieve this: 1. Create a new metric: Work in Progress Time (from Created to Resolved). 2. Define your work schedule,…

Hi @tara wilding If you’re open to using add-ons, Time Metrics Tracker | Time Between Statuses can be solution for you. You can track SLA like time to first response or time to resolution in the last month easily. Simply configure the metrics in the add-on to see them in the gadget as well. You can also find information in…

Hi @Arnelys 👋 Welcome to the Community! If you’re open to using add-ons, Time in Status can be solution for you. 1. Use Assignee Time Report which shows you how long each assignee has been working on each issue. You can display this data as a table view or chart view (column, area, pie) 2. For Scrum teams we are also…

Hi @Pappu Saha 👋 If you’re open to using add-ons, Time in Status can be solution for you. 1. Use Assignee Time Report which shows you how long each assignee has been working on each issue. Additionally, in the "Total" column, you can find the total time each person has spent on each issue. Also with different filtering…

@Dilan Koyunoğlu Merhaba! And welcome to the Community! It is possible to track the time between issue creation and resolution in Jira, but Jira’s built-in features have limitations when it comes to calculating time in business hours. By default, Jira provides the Created vs Resolved Report, which shows trends but doesn’t…

Hi @JJ Legelis Welcome to the Community! Thank you for your question! Querying for incidents that took longer than 30 days to close, considering the back-and-forth movement between statuses, can indeed be a challenge with standard JQL due to its limitations in date logic and unfortunately simple JQL for resolution time…

Hi @lenka_salacova Thank you for reaching out! The "Average Time in Status" gadget is indeed available in the Time in Status app for Jira Data Center. It allows you to display average time reports directly on your Jira dashboard. To help you quickly resolve this, here are a few steps to check and add the gadget to your…

Hi @Grant Olson Thank you for your kind words and for showing interest in the Mentions Dashboard ! 😊 We’re definitely planning to enhance the gadget's configurability in the future. Based on user feedback and our roadmap, we’ve identified a few key priorities to focus on: * Support for additional Atlassian products,…

@Seenivasan K We’ve received your bug report. Unfortunately, this issue appears to be on Jira’s side, but rest assured that my team and I are doing everything possible within our control to resolve it. We are actively exploring all available options to address the problem. Thank you for your patience!

Hello @cuong_nt1 When you copy production data to a sandbox, the sandbox environment often resets or overwrites its configuration. This could result in third-party apps being removed, as they are not part of the production data being copied. To avoid losing the third-party app, you can try the following steps: * Reinstall…

Hi @Seenivasan K 👋 I'm marketer of Time in Status. We apologize for the inconvenience you're experiencing. It seems there was a temporary issue processing your request. If the problem persists, fill free to contact here, or by SaaSJet Support, or email us at support@saasjet.atlassian.net any time! Thank you for your…

Hi @Jeremiah That’s a great question, and it really comes down to how your team defines and manages work within your workflow. From a general perspective: * Waiting/On Hold statuses are often seen as part of the In Progress category. This is because the issue has typically been started, or is waiting for something specific…

Ola @Tainah / Willian No plano gratuito do Trello, você pode ter até 10 colaboradores por área de trabalho. Ao migrar para o plano Standard, será cobrado US$ 5 por mês para cada membro da área de trabalho, incluindo os 10 colaboradores já existentes. Portanto, se você tiver 10 colaboradores, o custo total será de US$ 50…