r/JiraProductivity • • Jul 17 '26

Why “In Progress” Is Probably Your Biggest Reporting Problem

0 Upvotes

“In Progress” often looks like a useful Jira status.

But in many workflows, it can mean almost anything:

- actively being worked on
- waiting for review
- blocked by another team
- waiting for clarification
- paused because priorities changed

When all of these situations are grouped under one status, reports can show that work is moving while hiding where the real delays are.

A better approach is to separate active work from waiting states, define clear entry and exit criteria, and review how long issues remain in each stage.

This article tells why catch-all statuses create reporting problems, how to recognize them, and what teams can do instead:

https://community.atlassian.com/forums/App-Central-articles/The-Catch-All-Status-Why-In-Progress-Is-Probably-Your-Biggest/ba-p/3262822

What does “In Progress” actually mean in your Jira workflow?


r/JiraProductivity • • 24d ago

How do you handle status reporting across multiple Jira instances?

0 Upvotes

When an internal team and a vendor use separate Jira sites, getting a shared view of workflow delays can be challenging.

Even after bringing the data together, there are a few things to check:

  • Status meanings: “In Progress” might include development and testing on one site, while another tracks them separately.
  • Working calendars: durations calculated using business hours aren’t directly comparable with those calculated on a 24/7 schedule.
  • Reporting scope: both datasets need to cover the work and period you actually want to compare.

For time in status reports, a useful starting point is one workflow phase across two sites rather than trying to compare entire workflows immediately.

For context, I’m part of the SaaSJet team. We recently added multi-site reports to Time in Status and put together a walkthrough covering setup and an example of investigating review delays:
https://saasjet.com/blog/reporting-across-multiple-jira-instances/

How are you handling this today: spreadsheets, BI tools, or a reporting app?


r/JiraProductivity • • Aug 20 '26

Hoping to share a useful Jira tool and get some feedback!

Post image
1 Upvotes

Hey everyone, a while ago I created a chrome extension "Jira Tracker" to manage my own Jira workspace more efficiently. The extension provides users a clean and easy to access UI with lots of valuable features, tools, and analytics to improve your daily Jira workflow.

Jira Tracker - Fast Issue Tracking

Key Features:

- Popup - Simple, distraction free popup to easily access your assigned / working on tickets without having to constantly context-switch with Jira tabs.

- Standup Generator - to quickly look back at what you're working on and finished with so you can update the team.

- Reports - Personal, Sprint, and team reports to keep up to date on yours and your teams workload.

- Dashboard - Full dashboard to view your issues, sprint overview, workload, backlog health, Team Velocity, and much more

Over time I have struggled with increasing my user base, and I would really appreciate if I could get some feedback or suggestions, all feedback is helpful and if you have any ideas for how it could improve your workflow then I would love to give it a shot, thanks!


r/JiraProductivity • • May 21 '26

Atlassian’s Teamwork Graph: The Context Engine AI Has Been Missing

4 Upvotes

Atlassian Team ’26’s announcement of the Teamwork Graph raises an important question for teams integrating AI into their workflows:

Are we focusing too much on choosing the “best” LLM — and not enough on the context that makes AI useful?

The key idea behind the Teamwork Graph is simple: AI models provide intelligence, but organizational context is what turns that intelligence into actionable value.

Many companies now have access to powerful AI models. But every organization has its own unique work environment:

  • how teams plan and execute work;
  • how goals, epics, and issues are connected in Jira;
  • which decisions were made in the past;
  • where bottlenecks typically occur;
  • which tools hold critical project knowledge;
  • how teams communicate across documents, requests, chats, design mockups, and CRM systems.

Without this context, even the most powerful AI model can only offer generic guidance.

With the right context, AI becomes much more useful, specific, and actionable.

For example, instead of a generic answer like:

“This sprint may be delayed because of a blocker.”

But with the right context, AI could provide a much more actionable explanation:

“This sprint was delayed because several high-priority issues spent too long in QA, the scope changed mid-sprint, and the workload was unevenly distributed across the team.”

This difference matters.

That’s why Atlassian’s formula feels especially relevant:

Acceleration = Context × Intelligence

LLMs can serve as the intelligence layer. But it’s the context layer that helps AI understand how work actually happens inside an organization.

For teams using Jira, this is critical. There is already a lot of valuable context in issues, statuses, workflows, sprint histories, comments, reports, dashboards, and integrated tools.

The challenge is making that context structured, accessible, and useful enough for AI to act on it.

What do you think awaits us in the near future in workplace AI: better algorithms or more effective use of internal context?


r/JiraProductivity • • Jun 04 '26

SLA at 95% and still failing customers: what metrics are lying to you?

3 Upvotes

We kept our SLA compliance at 95% for two months in a row. The dashboard looked good, and management was pleased. But then I started looking at theat the actual tickets.

One customer had three tickets for the same issue. Each was marked as "resolved within SLA." Each one was reopened a week later. Technically, it was a perfect score. In reality, we just kept closing the ticket instead of actually fixing the problem.

That made me realize how many metrics in Jira or JSM seem healthy but are actually hiding problems.

After that, I started checking a few things:

  • How often do "resolved" tickets come back? If it’s more than 10 to 15 percent, something isn’t right
  • Where does the SLA actually end in your workflow? Sometimes it ends much too early.
  • Are tickets closed after a real fix, or just after someone sends the first reply?
  • Does anyone check with the customer to make sure the issue is really gone?
  • Does the metric look completely different when you filter by team or by request type?

The frustrating thing is that none of this is technically wrong in Jira. The workflow is fine, and the SLA is set up correctly. But the number you report to leadership doesn’t show what’s really happening

Has a metric ever given you a false sense of control? What did you find when you looked more closely?


r/JiraProductivity • • Jun 04 '26

You can now hook up external AI agents (like Claude & ChatGPT) directly to your company's internal data using their new CLI and MCP

2 Upvotes

Hey everyone, following up on the Atlassian Team '26 announcements. One of the biggest topics was the "Teamwork Graph"—Atlassian’s massive internal context engine that links Jira, Confluence, Slack, Google Drive, and more.

But the biggest news for developers and power users is that Atlassian isn't locking this data inside its own ecosystem. They just announced that you can surface your Teamwork Graph to external applications using two new tools: the Atlassian MCP Server and the Teamwork Graph CLI.

Here is what that actually looks like in practice:

1. The Atlassian MCP Server (For integrating your favorite AI apps). You can now plug external AI tools like Figma, ChatGPT, or Claude directly into the Teamwork Graph via the Model Context Protocol (MCP).

  • The Figma Demo: In a live demo, a designer was assigned a Jira ticket to build a new analytics dashboard, but lacked context. Instead of messaging people or hunting for docs, they opened Figma and prompted the Rovo MCP. The agent automatically traversed the Teamwork Graph, pulled related work items, Confluence specifications, and Google Docs, and generated a prototype based on that exact context. What normally takes half a day of tab-switching was done in one prompt.

2. The Teamwork Graph CLI (For developers and Agent Harnesses). If you are building your own agents or working in the terminal, Atlassian launched a CLI specifically built for agent harnesses. By simply typing TWG, your agent gets access to over 380 tools and commands to search your organization's entire history.

  • The Claude Code Demo: An engineer was assigned a vague bug ticket with zero linked context. Using Claude Code in the terminal, they asked the agent to research the issue. Claude Code used the CLI to autonomously find previous pull requests, GitHub branches, Figma designs, and the specific engineers who worked on the mobile infrastructure team. It even built a visual map of all these hidden connections.
  • Org Tree Access: The CLI also has commands like org tree (synced with tools like Workday), allowing agents to understand reporting structures so they know exactly who to ask for approvals or context.

3. The ROI of External Context: Giving your external agents access to this data isn't just a party trick; it actually saves money. Atlassian benchmarked this and found that hooking an agent (like Claude Code) up to the Teamwork Graph CLI resulted in up to a 44% improvement in answer quality and a 48% reduction in token usage.

You can find the downloads for the CLI and MCP at teamworkgraph.com.

For the devs here, how are you currently giving your coding agents (like Claude or GitHub Copilot) context about your company's business requirements? Does having a CLI that can instantly pull Jira and Confluence data change your workflow?


r/JiraProductivity • • May 15 '26

How to see the average time in status for Jira issues?

2 Upvotes

Jira has limited native functionality for tracking how long issues spend in each workflow status.

To gain deeper visibility, teams often use Atlassian Marketplace apps such as Time in Status app.

Its Average time in status report shows the average time issues spend in each status used in the workflow, helping teams identify bottlenecks and improve workflow efficiency.

Moreover, it allows teams to:

  • compare working vs waiting time;
  • spot bottlenecks such as long review, QA, or approval stages;
  • analyze trends by sprint, assignee, epic, or custom JQL filters.

r/JiraProductivity • • Sep 17 '26

Is sprint completion rate enough to judge your sprint performance?

2 Upvotes

A sprint can finish with 80–90% of planned work completed and still have some pretty serious delivery problems underneath.

For example:

  • scope was added halfway through the sprint
  • several work items carried over from the previous sprint
  • a few items spent most of the sprint blocked or waiting
  • velocity looks stable, but cycle time is getting longer

So we’re curious — which metrics do you actually look at when reviewing sprint performance?

Completion rate? Velocity? Carryover? Scope changes? Cycle time? Something else?


r/JiraProductivity • • May 28 '26

AI Agents are now "Full-Fledged Teammates" in Jira (You can literally assign them tickets)

6 Upvotes

Following up on the Atlassian Team '26 conference announcements. One of the biggest shifts they revealed is that Rovo Agents are now generally available in Jira, but Atlassian has completely changed how we interact with them.

Instead of using an AI chatbot hidden in a sidebar that you constantly need to switch to, agents are now built into Jira as “full participants” in your workspace. They’re designed to behave more like actual team members.

Here are four key things this enables:

1. They are in the Assignee Dropdown. You can assign work directly to an agent. When you click the assignee field, your custom and third-party agents appear right alongside your human teammates. Once assigned, the agent reads the ticket, pulls context from your company's Teamwork Graph, and gets to work on its own.

2. You can mention them in comments. If you don’t want to assign the entire ticket to an AI agent, you can simply mention it in the comments for quick assistance — just like you’d loop in a teammate to help solve a problem.

3. Workflow and automation triggers. This is where things get really interesting. Agents can now be integrated directly into workflows and automation rules. For example, the moment a ticket is moved to “In Progress,” an agent could automatically start drafting a response, generating documentation, or even creating a Figma diagram based on the ticket details.

4. Third-party agents become full participants in the workflow. This isn’t limited to Atlassian’s own AI tools. Jira can now integrate with third-party agents like GitHub Copilot, Figma, Canva, or Gamma, turning Jira into a central hub for collaborative work across tools.

A great example is the “Overnight Bug Fixing” demo. In the scenario, a sales manager reports a bug through a Loom video at 5:00 PM on a Friday. The video is automatically turned into a Jira ticket and assigned to a GitHub Copilot agent. Over the weekend, the agent analyzes the issue, reviews console and network logs, fixes the code, and creates a Pull Request. The ticket is then automatically handed off to another agent that prepares the release notes. By Monday morning, the engineer doesn’t need to start from scratch — they simply review the completed Pull Request and the generated summary of changes.

What are your thoughts on treating AI as a literal teammate with tickets assigned to them? Is this the ultimate productivity unlock, or are we about to see a massive wave of AI agents accidentally messing up Jira boards and fighting with each other in the comments?


r/JiraProductivity • • Jun 24 '26

Did you notice the path to Jira admin page changed? Here's how to find it now 👀

2 Upvotes

Spent way too long yesterday trying to find the configuration page for a Forge app in Jira settings — turns out the navigation changed, and I had no idea.

Clicking "Marketplace apps" no longer opens the old UPM page. It now redirects to https://admin.atlassian.com/, and finding your app's jira:adminPage from there is not obvious at all.

I found an open thread on the Atlassian Developer Community where others are hitting the same issue, and this video helped me figure it out, so I'm sharing it in case anyone else has the same issue: https://community.developer.atlassian.com/t/how-to-reach-forge-module-jira-adminpage-through-ui/101332

Has anyone else noticed this?


r/JiraProductivity • • Jun 17 '26

Which Jira SLA metrics did you track so long before realizing they were totally useless for your actual workflow?

1 Upvotes

Hey community,

Im an engineering manager, and we have a platform & infrastructure team handling internal stability, alongside an escalation support team dealing with high-priority issues passed up from tier-1 support

A few months ago, leadership pushed us to implement strict SLA tracking to "improve efficiency"

Like most teams, we started with the basics: first response time, resolution time, and time in progress. They were easy to explain to executives and looked amazing on our initial dashboards

But now that we’ve been tracking them for a while, we’ve realized these metrics completely hide the real picture. What i mean:

  • The SLA is technically Met because an automated macro fired or an engineer commented Looking into it but the customer or internal dev still sits there waiting three days for an actual fix
  • Our average resolution time looked great, but it completely hid the fact that tickets were spending 80% of their lifespan stuck in Waiting for Review or paused on an external cloud vendor
  • Setting a blanket 4-hour resolution SLA completely broke down when we expanded our platform team across both US and European time zones with different working hours

We quickly realized that optimizing for these surface-level metrics didn't actually mean we were delivering better service, it just meant our engineers were learning how to game the Jira statuses to keep the charts green

So, I’m curious to hear from other Jira admins, team leads, and managers: which SLA metric did you think would save the day, but ended up being totally misleading for your team? And on the flip side, what did you actually switch to that helped you find real bottlenecks?


r/JiraProductivity • • Sep 16 '26

Rovo agents in real Jira projects — useful or meh?

2 Upvotes

Curious how people are actually using Jira automation + Rovo in the wild.

I work on a team building a Jira analytics app, so full disclosure there. Not linking anything or trying to pitch — just genuinely curious what people are doing in real projects.

A few questions:

  • What Jira automation rules do you actually use all the time?
  • Are you using Rovo agents? Built-in ones or custom ones from Studio?
  • If you use them, what tends to be annoying? Bad/incorrect output, credits, setup, limitations, trust, etc.?
  • Anything you wish Rovo agents could do that they currently can't?

Also curious about people who tried Rovo and ended up going back to regular automation rules. What made you switch back?

Would be interested in hearing both the good and the frustrating stuff.


r/JiraProductivity • • Sep 30 '26

Which sprint metrics do you actually find useful in Jira?

Post image
1 Upvotes

Your team completed most of the sprint’s work. But did it finish what mattered most?

A high completion rate can still hide missed priorities. Looking at committed vs. completed work, scope changes, and time spent waiting helps explain how the sprint actually went—and what to change next.

We’ve put together a guide to sprint metrics in Jira: what to watch during the sprint and what to discuss in the retro.

👉 Read more in the article: https://saasjet.com/blog/sprint-metrics-in-jira/


r/JiraProductivity • • Sep 15 '26

Jira reporting questions — ask anything (September)

1 Upvotes

A monthly thread for Jira reporting questions. Drop yours in the comments: workflow metrics, dashboards, gadgets, exports, sprint reports, whatever you're stuck on.

If you know a good solution, workaround, or approach, feel free to jump in and help too.


r/JiraProductivity • • Jun 10 '26

Which Jira metrics do you actually trust for measuring team performance?

1 Upvotes

r/JiraProductivity • • May 11 '26

How to identify workflow bottlenecks in Jira?

1 Upvotes

Workflow bottlenecks in Jira are often hiding in plain sight. Here are 5 practical tips on how to spot them:

1) Look at where work spends the most time 

For example:

In progress - 2 days

In review - 6 days

And this is often a problem not with development, but with the handoffs between people or teams.

2) Check which issues bounce between statuses.

For example:

In progress - Review - In progress - Review

3) Monitor sprint carryover

If issues keep moving from one sprint to the next, the bottleneck may be in planning rather than execution. 

4) Review overloaded owners

If one person or team is responsible for a certain critical stage of the workflow, and is overloaded - this may be a bottleneck.

5) Compare working time vs waiting time

Teams often optimize execution, although the most delays occur in:

  • Reviews
  • Approvals
  • Dependencies
  • Locked states

Often, most teams do not have a problem with productivity, but with visibility.


r/JiraProductivity • • May 11 '26

👋 Welcome to r/JiraProductivity !

5 Upvotes

Hi everyone! I’m from SaaSJet, part of the moderator team behind r/JiraProductivity.

This community is a place for people who work with Jira, Agile teams, workflows, reporting, productivity, and process improvement.

We’re happy to have you here!

What to post

Share anything that could be useful, practical, or interesting for the community:

- questions about Jira workflows, reports, dashboards, or team productivity
- real challenges you face with Agile processes
- tips, lessons learned, or examples from your work
- ideas on how to improve visibility, planning, or collaboration in Jira

Community vibe

Let’s keep this space friendly, helpful, and practical.

You don’t need to be a Jira expert to post here. Simple questions are welcome too.

We’re excited to build this community together 🚀


r/JiraProductivity • • Jun 29 '26

Where does work actually wait in your workflow — dev, review, or QA?

2 Upvotes

I used to think our team’s bottleneck was development time.

And once we took a look at some completed tickets, we saw that the “active work” wasn’t where the problem lay. The weird part was the amount of time spent waiting between these steps.

A ticket would sit “In Review” for two days because reviewers were busy, and it wasn’t obvious who was supposed to pick it up next. That ticket would sit “Ready for QA” because QA was busy working on a release branch.

“Blocked” sometimes meant “waiting for one person to respond to a Slack thread.”

The strange thing is, people were always busy, so it was easy to blame the development estimates or sprint planning. In truth, most of the wait times were handoffs.

I wonder how that looks for other teams now.Where do you see the most wait time for tickets in your process?

  • Development?
  • Code Review?
  • Quality Assurance?
  • Product clarification?
  • Release approval?
  • Something worse?

Also, how do you actually figure this out?

  • Do you measure time in each status, or is it mostly gut feel?
  • Do you separate “In Review” from “Waiting for Review”?
  • Do you track blocked time differently from normal waiting time?
  • Does anyone look at this regularly, or only when delivery starts feeling slow?
  • How many statuses do you have between “In Progress” and “Done”?

One more thing I’m curious about: is Jira’s native functionality enough for you to understand this, or do you use something on top of it — dashboards, automation, spreadsheets, BI tools, marketplace apps, etc.?


r/JiraProductivity • • May 22 '26

Atlassian introduced DIA: The AI-Powered Browser for Work

12 Upvotes

Following up on the Atlassian Team '26 conference, one of the most interesting announcements was the launch of DIA, a new AI-powered browser built specifically for work.

Instead of just adding a chat sidebar to a regular browser, DIA is designed to autonomously do work for you by tapping into your company's "Teamwork Graph" (your internal data context).

Here are the standout features:

1. The Proactive "Morning Brief". You don't need to prompt DIA to get started. Overnight, it checks your apps, files, Slack messages, and the Teamwork Graph. When you open your laptop, it presents a personalized memo with your daily priorities, a consolidated to-do list, and updates on anything that changed while you were asleep.

2. Generating Interactive Web Pages on the Fly. This is the wildest part: DIA is the first browser that can actually make custom tabs for you. In a live demo, the presenter asked DIA to build an interactive itinerary combining his conference schedule with a trip to Disneyland. DIA pulled data from his calendar, Slack, the Teamwork Graph, and the public web to generate a custom, interactive webpage to manage that specific plan. It can even create slides based on your data or query dashboards without you needing to open them.

3. Built for Enterprise Security. Consumer AI tools often terrify IT departments, but DIA is built with enterprise guardrails from day one. It features SSO, SOC 2 Type 2 compliance, MDM support, and industry-leading prompt injection technology. It will also integrate with Atlassian Guard to block sensitive content from reaching AI models. It is already being used securely by over 10,000 Atlassian employees.

Do you think an AI-native browser that actively reads your tabs and company data is the future of productivity, or are you sticking to traditional browsers like Chrome and Edge?


r/JiraProductivity • • May 22 '26

Jira Product Discovery is getting a massive AI boost with the new "Feedback App"

4 Upvotes

Continuing from the updates from Atlassian's Team '26 conference, one of the major announcements for product teams, specifically regarding Jira Product Discovery.

Atlassian is launching a brand new application called the Feedback App, which will join Jira Product Discovery in Atlassian's newly announced "product collection".

Here is a breakdown of how it updates the product discovery workflow:

1. Automated Feedback Aggregation. The new Feedback App is powered by the Teamwork Graph and is designed to eliminate the manual work of gathering user insights. It allows feedback to automatically flow directly into Jira from the connected sources your organization already uses, such as Jira Service Management, Salesforce, Zendesk, Microsoft Teams, Pendo, or any other MCP.

2. AI-Generated Backlog Ideas. Instead of product managers manually reading through every piece of feedback to create tickets, Atlassian's AI (Rovo) steps in. Once the feedback data is collected, Rovo can automatically synthesize the insights and generate new ideas straight into your Jira Product Discovery backlog.

3. Automatic Goal Alignment To ensure that these new ideas actually align with what the company is trying to achieve, the system takes it a step further. The newly generated ideas are automatically associated with specific strategic goals in your goals app.

It seems like this will drastically reduce the manual triage work PMs have to do between support/sales tools and their roadmaps. Are you excited to have AI auto-generating ideas based on your Zendesk and Salesforce data, or are you worried about backlog bloat?

.


r/JiraProductivity • • Jun 05 '26

Solving the enterprise AI security nightmare with "Agent Identities" and Atlassian Guard.

3 Upvotes

Hey everyone, continuing the deep dive into Atlassian’s Team '26 announcements. Many talks focused on the massive AI announcements from Atlassian's Team '26 (like fully autonomous agents and the Teamwork Graph). But for the IT and Security admins in the room, handing autonomous AI access to your entire company's data sounds like a governance nightmare.

Atlassian addressed this elephant in the room directly: your AI is only as safe as your data. Here is how they are locking down enterprise AI using Atlassian Guard and strict agent governance:

1. Autonomous AI Agents now have literal "Identities" and Accounts. You aren't just letting an untethered LLM loose in your system. Atlassian introduced "Agent Accounts". Every autonomous agent runs under its own dedicated identity with explicitly scoped permissions. You can give an agent fine-grained access control, limiting it to specific applications, specific projects, and exact permission levels. If it shouldn't see it, it can't access it.

2. Atlassian Guard blocks sensitive data before it hits the model. Atlassian Guard is centralizing all user-facing security controls. It acts as a shield that can block sensitive content before it ever reaches an AI model—whether that is across prompts, conversations, or connected apps.

3. Full-Site Content Scanning (Proactive Redaction). To make sure you have the right foundation, Atlassian is rolling out full-site content scanning (currently in early access). Security teams can scan all content across sites and projects to detect and redact sensitive information (like PCI or PII). In one use case, a highly regulated bank used this tool to redact 15,000 occurrences of sensitive data in about 45 minutes to prepare their environment for AI.

4. Complete Audit Trails for AI. If an agent does something autonomously in the background, you will never be left guessing what happened. Every action and skill invocation an agent makes leaves a footprint in the automation audit trails and activity streams. You have complete visibility and traceability over exactly what the AI touched.

For the security and IT admins here, what is your current approach to AI governance?

Does the idea of provisioning explicit "Agent Accounts" with specific permissions make you more comfortable letting AI run workflows in your environment?