MeghnaP_LogicLemur Labs Atlassian Partner

I think the biggest shift for me has been moving from asking “Can AI do this?” to “How do I know it did this well?” AI has genuinely saved me time on things like summarising information, finding patterns across Jira data, and getting a first draft of something that would otherwise take much longer. Where I’ve become more…

One question I’m particularly interested in: If your team is already using AI agents in Jira, what metric are you using to prove they are actually creating value? Tokens? Issues completed? Time saved? Quality? Something else? I suspect most teams are still measuring AI consumption rather than actual engineering outcomes.

Thanks @__ Jimi Wikman for your kind words, I really appreciate the encouragement. As more teams start adopting Rovo and other AI Agents, we felt there was a growing need for better visibility into what these agents are actually doing and how much value they're delivering. I'm curious, are you seeing more teams asking…

Curious to hear how other teams are approaching AI governance. Are you already measuring your AI agents, or is the focus still mainly on prompts and token usage? I'd love to learn what metrics matter most in your organization.

P.S Curious to know how are you preparing your Jira instance for Atlassian's Data Limits? Have you started monitoring your guardrails, or are you planning your first governance review? I'd love to hear how your team is approaching it.

This hits close to home with documentation too. A Confluence page can look perfectly fine — formatted, in the right space, technically "complete" — and still be wrong, because the only thing that knew it was outdated was a person who happened to remember. The page doesn't know it's stale. It just sits there looking as…

Timing note on the September 2026 enforcement: Worth flagging for anyone reading this in the next few weeks: the second wave of Jira Cloud hard limits takes effect this September. Unlike the March 2026 wave (fields, work types), this one covers a broader set of configuration objects: * Workflows: 150 per space * Workflow…

For Jira Standard admins specifically, this closes a real gap. Site Optimizer's governance view is a Premium-only feature, and the alternative — pulling field/workflow/status counts via the REST API on a scheduled script — means building and maintaining your own polling job, error handling, and threshold alerting from…

We deliberately designed the Site Health Score to support recurring customer engagements rather than one-time health checks. Imagine showing: 📈 Q1: 68/100 📈 Q2: 81/100 📈 Q3: 89/100 That's a simple way to demonstrate the impact of governance and optimisation work over time. One area we're especially interested in is how…

Great article! I think one challenge many Jira administrators and Solution Partners face isn't just understanding Atlassian's Data Limits, it's knowing when it's actually time to take action. A full optimisation review is incredibly valuable, but customers don't necessarily need one every month. What they often need is a…

Hi @Petru Simion _Simitech Ltd__ , Thanks for the thoughtful comment. I completely agree with you. Finding a problem is one thing, but knowing what can be safely cleaned up is often the hardest part. Our goal with QuotaWatch is to help administrators answer questions like: Is my Jira instance healthy? Which area needs…

We'd Love Your Feedback If you're an Atlassian Solution Partner, how do you currently measure the health of a customer's Jira environment? Would a continuously tracked Site Health Score help you demonstrate the value of your managed services, quarterly reviews or optimisation programmes? We're keen to hear how you'd…

We've spoken with several Jira admins who initially built automation rules for dependency notifications because it seemed like the quickest solution. Over time, the challenge wasn't creating the rules, it was maintaining them as workflows evolved. Has anyone else experienced this?

I'm curious how your teams handle this. Have you ever opened a Confluence page from a direct link and only later realized it belonged to an archived project? Would a clear visual indicator help reduce that confusion?

Curious how everyone is solving this today. Are customers generally using: • Jira Automation? • ScriptRunner? • JMWE? • Forge/Connect apps? • Something completely custom? It would be interesting to understand which approach has become the de facto standard.

One interesting scenario I didn't include in the post is how often QA gets blocked waiting for multiple bug fixes before testing can begin. The challenge isn't knowing that an issue is blocked. It's knowing exactly when it's no longer blocked. While building Unblocked, I found that evaluating dependencies wasn't the…

One thing I'm still curious about: How many Jira admins are solving dependency notifications with Automation today versus relying on Watchers or Slack? I'd love to hear what has worked (or not worked) for your teams. You may check also check Unblocked: Blocker Resolved Notifications for Jira on marketplace. 

Curious how other teams handle blocked work today. Do you use: • Flags? • A dedicated "Blocked" status? • JQL filters? • Automation? I'd love to learn what has worked (or hasn't) for your team.

This article was inspired by a recent Atlassian Community discussion started by @Mirek on whether old Confluence pages should be archived or retained for Rovo. Reading through the different perspectives, including @Anwesha Pan 's thoughtful counterpoints, made me realize that the bigger question isn't whether we keep or…

I completely agree. I don't think the challenge is the amount of content, it's knowing which content can be trusted. Historical pages are still valuable, but they shouldn't compete with the current source of truth. Simple signals like when a page was last reviewed, whether it has an owner, or if it's been superseded could…

I don't think the question is whether we should keep or delete old pages anymore. It's whether people (and AI) can tell which content they should trust. We've found that older pages still have a lot of value because they explain why decisions were made, even if they're no longer the current way of doing things. That…

Several people asked how FreshPage fully solves this problem. FreshPage addresses it by providing capabilities such as: • Content verification • Ownership visibility • Review schedules • Trust indicators The goal isn't to create more documentation. It's to help teams clearly understand which documentation can still be…

Interesting perspective from several people who reached out privately also The concern isn't that Rovo will generate incorrect answers. The concern is that employees may trust answers from content that hasn't been reviewed in years. That feels like a very different challenge from AI hallucination generated from invalid…

I completely agree @Anwesha Pan . I don't think technology replaces human oversight. It makes that oversight visible and scalable. For example, a subject matter expert can verify a confluence page, validate the page in defined review schedule, and establish clear ownership. Those trust signals then help every employee and…

One Question I'm Curious About As more organizations adopt Rovo, do you think knowledge trust will become as important as knowledge discovery? I'd love to hear how others are approaching this challenge.

This is exactly why many organizations are nervous about AI assistants. A status rename breaks a filter. A space key change breaks a dashboard. The impact is visible because something stops working. The bigger problem is when nothing breaks. A Confluence page written 3 years ago still appears in search results. A process…

Curious to hear thoughts from @Mark Cruth @Bill Sheboy are approaching this. If an employee asks Rovo: "What's our security exception process?" Should Rovo also indicate: • Last verified date • Content owner • Review status Or is search relevance enough? I'd love to hear how others are thinking about trusted knowledge.

One thing worth highlighting: IdleIssues() respects StatusClock's business-day configuration. That means weekends, holidays, and custom working calendars can be excluded from calculations. For teams using Jira to manage SLAs, support queues, sprint commitments, or operational workflows, this often produces far more…

For anyone interested in trying the StatusBounces() function, it's available as part of StatusClock for Jira Cloud. StatusClock provides several workflow analytics and JQL capabilities, including: ✅ StatusBounces() - Find issues repeatedly returning to the same status ✅ BusinessDaysInStatus() - Query issues based on…

Great explanation by @Aron Gombas _Midori_ ! Just adding a bit more context that might help. The X-RateLimit-Limit: 0 you're seeing is actually a known behaviour — a value of 0 doesn't mean "zero allowed", it typically means the limit is being enforced at the org/tenant level rather than per-endpoint, and the header is…