Birkan Yildiz _OBSS_ Atlassian Partner

The epic was planned for 3 sprints but it took 5. In the retrospective, someone asks three simple questions: When did the scope grow? Who moved the due date? Which stories changed hands mid-sprint? Jira recorded every one of those changes. Getting them back out, across a whole epic, is the hard part. This article is for…

Timepiece - Time in Status for Jira has a new report type: the SLA Report. It measures how long each work item takes between two points in your workflow and checks the result against a target you set. Every item shows up as met, breached, or still in progress. The new report covers all the ground that Jira Service…

Cycle Time and Lead Time are two of the clearest signals of process health. The problem is that neither number is a native Jira field. Plain JQL can't filter, sort, or automate on either one, no matter how the query is written. This article explains why there is a gap, how to close it once, and three JQL searches that are…

Jira's Control Chart is a built-in report that tracks Cycle Time and Lead Time for a sprint or product. It answers one question well: how long. Time in Status answers the same question, but with a big difference. The Control Chart gives you a single number per issue, and that number hides what you usually need to know:…

A ticket's single duration rarely tells you what you need to know. A report showing 20 hours total for a field value doesn't prove whether that number is improving or worsening; all you have to go on is your gut. Two new report types in Timepiece – Time in Status for Jira close that gap: Any Field Duration Per Time-Period…

Create an Any Field report on any Jira field that has dozens or more values, such as Vendor, Rejection Reason, Device Type, or anything else your team monitors. You used to receive a column for each value that appeared in the field, regardless of whether you were interested in it or not. The report extends beyond your…

Audit logs and issue history in Jira record many types of changes and answer various inquiries. As each answers different kinds of questions, knowing the difference saves time. Knowing where both run out of road helps you determine whether a specialized reporting tool is worthwhile. In Jira, audit logs and issue history…

A stakeholder asks why an issue is late. "It's stuck In Review" isn't an answer, and neither is a status label from 3 weeks ago. What actually helps is a number: this issue has been in deployment for 4 days, against a 1-day average. That number is Time Between Statuses: how long it takes an issue to move from one point in…

A Time in Status report usually gets built for one purpose and one audience. Then 3 other teams ask for "the same thing, but just for us," and you end up cloning the report or editing the dashboard gadget every time someone needs a narrower view. Quick Filters in Timepiece removes that back-and-forth. The person who builds…

If you run projects in Jira, you already know how much depends on how long issues sit in a given status. The problem is getting to that number. It usually means leaving the issue, opening a report, and coming back. Timepiece - Time in Status for Jira Custom Fields remove that trip. Timepiece calculates the time issues…

Every Jira admin has seen it: a simple workflow that somehow turns into a mess. Tickets get stuck, dashboards show the wrong numbers, and velocity drops. Usually, the real problem is a mix-up with Jira’s basic building blocks: statuses, status categories, and resolutions. Let's break down how to fix your workflow so it…

For Scrum Masters, Jira Admins, and Engineering Leads, predictable delivery relies on workflow velocity. When sprints roll over, or bottlenecks pile up, you don't need guesses; you need exact, empirical durations. To find these delays, teams naturally start by tracking how long issues sit in specific workflow stages. In…

Maintaining a flexible Jira hierarchy is key to aligning high-level business goals with daily engineering tasks. However, tracking exact status times across these structural tiers is a common roadblock for many delivery teams. Standard Jira metrics often fail to capture the true active duration of parent issues, leading to…

Meeting compliance frameworks like SOC 2 or ISO 27001, troubleshooting regressions, and running sprint retrospectives require deep visibility into Jira's history. While Jira records every issue update to its backend changelog, extracting this data at scale is a major administrative headache. Depending on your deployment…

Have you ever needed to access Confluence page history to a specific date for an audit, a past release, or compliance? If so, you've probably noticed that native Confluence is built for fast-paced daily collaboration, not strict version control. Relying on the native "Restore this version" feature to reconstruct a past…

Everyone is talking about how AI is transforming engineering and speeding up development. But as Jira Admins, Product Managers, and Agile Leaders, we face a very specific challenge: How do you actually prove those productivity gains with hard data? If your new AI tools and agents are truly working, the numbers should…

Jira Automation allows us to focus on the work that matters by removing the need to perform manual, repetitive tasks. Using a simple no-code builder, teams can automate their processes using triggers that kick off a rule, conditions that refine the scope, and actions that actually perform the tasks. But what if your…

On February 25, 2026, Atlassian officially shifted the paradigm of how we work in Jira. With the announcement of agentic AI and autonomous workflows, AI agents are no longer just background tools; they are teammates. We can now assign them tasks, mention them for research, and embed them directly into our engineering…

If you manage Jira dashboards, you know the friction of static date filters. Updating a "Last Month" or "Last Week" report shouldn't require you to manually change calendar parameters on the 1st of every month. That’s why we’ve developed the Dynamic Date Picker for Timepiece - Time in Status for Jira. It completely…

Every Jira user knows the struggle of tracking down a specific issue update. As projects scale, the native Jira changelog quickly becomes a crowded logbook. Finding out who changed a requirement or when a ticket status shifted requires too much manual scrolling. We developed Historian - Issue History for Jira to turn that…

In the Atlassian ecosystem, Jira performance analytics serves as the critical bridge connecting raw issue tracking with actionable process intelligence. Instead of guessing why a specific sprint fell behind schedule, high-performing teams must track core Agile metrics, specifically Cycle Time, Throughput, and Lead Time,…

Timepiece - Time in Status for Jira has officially migrated from Atlassian Connect to Atlassian Forge. Because of this architectural upgrade, Jira administrators are required to perform a manual update to approve new permission scopes. This guide explains what the Forge migration means for your Jira instance, why you are…

Staring at a green SLA timer in Jira Service Management (JSM) that tells us we’re "on time," while knowing the actual business relationship is under strain. In modern ITSM, an SLA is more than just a timer on a screen; it’s a measurable commitment of trust between you and your customers. However, as many Jira admins are…

Imagine if you had a time machine for your Jira backlog. Instead of just seeing the "now," you could turn a dial and see exactly how your project looked on any given Tuesday three months ago. Currently, most of us use Jira to track the immediate present. But when a manager asks, "What did our priority list look like on day…

Every team is unique, with its own workflows, structures, priorities, and specific custom fields that make Jira function effectively. When it comes to time tracking, there is no exception. While many teams follow Agile metrics like Cycle Time and Lead Time to measure efficiency, no two teams define that data in quite the…