Iryna Komarnitska_SaaSJet_ Community Champion

There’s a specific kind of chaos that only Jira can produce. On paper, everything is “In Progress.” In reality, half the work is parked in Review, three items are “Waiting for QA,” and one innocent ticket has been “Blocked” long enough to qualify as a historical landmark. And the worst part? Everyone is working hard. So…

Some companies run recruitment in ATS tools. Some run it in spreadsheets (brave). And some run it in Jira, where every candidate is a work item and every stage of the hiring process is a status. If you’re a recruitment agency or an in-house HR team already living in Jira, this approach is weirdly powerful… until you try to…

Teams don’t need more visibility — they need shared signals Teams rarely struggle to capture work. They struggle to run decisions and delivery on the same truth. Most organizations already have the basics: Jira for plans, tickets, epics, and delivery tracking Confluence for decisions, specs, runbooks, and strategy docs…

Picture the Sprint Retro. Someone asks: “So… why didn’t we finish what we committed to?” Someone else replies: “Because things happened.” And then the room goes quiet while everyone collectively tries to remember which issues were: added mid-sprint removed mid-sprint carried over to the next sprint moved between assignees…

Picture this: you open Jira’s Control Chart, see the rolling average trending down, and think, “Nice — we’re getting faster.” Then someone from Support (or your most patient customer) asks the worst possible question: “Cool. Why do my tickets still take forever?” Both can be true — because Jira’s Control Chart is not…

If you opened a work item in Jira Cloud this week and thought, “where did Status go?”—you’re not alone. Atlassian has relocated the Status control from the right-hand context panel to the area below the Summary in the main content area. The change is rolling out across projects, and reactions range from “finally, more…

Burndown charts answer a familiar question: “Are we on track?” But when a team feels busy and delivery still slows down, a more revealing question appears: “Where is the work getting stuck right now?” Because scope can go down while flow gets worse. Tickets can move while value doesn’t ship. And a sprint can look “healthy”…

If you’ve ever led (or inherited) a codebase that “mostly works,” you know the feeling: You don’t need more activity metrics. You need to know where the risk lives. Not “which files changed a lot,” but: Which files keep collecting bugs and risky changes? Where do work items actually land? If we can only refactor one area…

Jira already captures where work is. The harder question is how it behaves over time: Which steps consume the most time? Is the process improving or quietly drifting? Where, exactly, do items “disappear” inside status groups? That’s where Chart Reports in Time in Status becomes more than “pretty graphs.” Three visual…

There’s a very special place in every Confluence space. You find it by applying the most powerful filter of all: Last updated: 3+ years ago That’s where the darkness dwells. 🕯️ Old release notes. Orphaned how-tos. Specs for a feature that died three product managers ago. Pages that silently whisper, “Please don’t trust…

Most sprint reports fail for one simple reason: they answer the team’s questions, not the leader’s. A delivery lead, Head of Product, or CTO doesn’t wake up thinking, “How many story points did we burn?” They’re thinking: Are we on track to deliver what we promised? If we’re not, when will we know—and what should we do…

“Peace, harmony, and no ‘quick fixes’ before release. Dreams, of course. But it's a holiday.” On the night of December 24th, the office was quiet. Slack was calm. Jira boards stood still. CI pipelines hummed softly in the background. Only one light was still on. Alex (you can replace this name with whoever in your team…

“Thank you for creating tasks without descriptions. Thanks to you, everyone remembers that work is pain.” Somewhere on your Jira board, there’s a ticket called something like: “Fix bug” “Update flow” “Improve performance” No description. No context. No steps. No expected result. Just a title and pure optimism. On paper,…

If 2025 had one theme for Time in Status, it would be this: build for the future without slowing down the improvements you feel today. A lot of our work this year happened behind the scenes (the kind of work you don’t always see immediately—but you definitely benefit from long-term). And at the same time, we shipped…

 “Your tasks have been stuck in ‘In Progress’ for so long that we've already thought about naming the status after you.” We all know that column. The cozy, non-committal space on your Jira board called In Progress. Not “Blocked,” not “Done,” not even “Needs Clarification.” Just… In Progress. Forever. At some point, it…

Most teams don’t hate standups—they hate wasting them. You gather smart people, trade updates, then walk away with the same invisible queues, the same stuck reviews, the same “we’ll pick it up today.” It’s not laziness. It’s a blind spot: we’re discussing stories while the system is quietly optimizing for waiting. This…

When your Jira projects hit five figures in issue count, you start paying a “performance tax.” Boards feel heavy. Filters crawl. Dashboards gasp for air. The hard question shows up: should we split this giant project—or scale it gracefully? This article gives you a pragmatic decision framework, clear signals to watch, and…

Imagine standing in a daily stand-up and asking: “Why is this task still In Progress?” And instead of vague guesses, everyone can see “3d 06h in In Progress” right on the card. That’s precisely what the new Time in Status custom fields by Time in Status app let you do on your Jira board. With this release, you don’t have…

If you’ve ever ended a sprint staring at a half–burned-down chart, a pile of rolled-over issues, and a grumpy team, you already know this: a sprint is not just a date range in Jira. Still, many teams treat it that way. They: Start an empty sprint “just to begin” and fill it later Estimate half the tasks after the sprint is…

AI should shorten the path from question to answer—not add ceremony. That’s exactly why we built FlagFocus, a new Rovo Agent for the Time in Status app for Jira. Instead of yet another lengthy report, you ask a focused question and receive a focused answer: Where do our flagged issues spend their time, and how much of it?…

Busy boards. Moving cards. No outcomes. If that sounds familiar, you’re looking at zombie work—tickets that shuffle between steps without actually getting closer to “Done.” This guide presents a calm, low-friction approach to identifying and reducing zombie work using the Time in Status app for Jira and its new Rovo Agent…

When issues bounce between statuses, the calendar moves but outcomes don’t. Let’s make those loops visible—calmly, and with the tools you already use. Status Churn refers to the avoidable back-and-forth in your workflow—the moments when an issue revisits the same step multiple times. Also known as ticket ping-pong /…

How teams get calmer dashboards and faster flow with a few small changes. Across large projects, the pattern repeats: dashboards disagree, reviews take longer than anyone expects, SLAs blame the wrong people, and “Done” quietly means three different things. From what we see supporting many organizations, the fastest wins…

SaaSJet has been around for over seven years, and as an Atlassian Marketplace vendor, it's clear that Confluence and Jira have been our long-time allies and helpers. Our single source of truth Confluence is where we keep what matters: decisions, docs, insights, and research. It keeps everyone on the same page—literally.…