Dr Valeri Colon (Connect Centric) Community Champion

Love your disclaimer @Trudy P Claspill yet your guidance is still accurate. This isn’t expected trial behavior. There was a known issue where users were incorrectly shown “credit limit reached” even with little or no usage, especially during recent changes to Rovo Dev credits. So this is likely a backend bug, not your…

I've missed you @Trudy P Claspill @Jaderson This looks less like a generic Rovo failure and more like how the issue link is being sent during creation. In Jira, issuelinks usually needs an add operation or a separate Create issue link call, rather than outwardIssue directly in the create payload. So the Story can be…

@Maarten Knaepen welcome to the community. @Jovana Dunisijevic ’s guidance is solid, especially on re-auth and checking site access. One thing to add: a 403 on the credits/check endpoint can also mean your Rovo Dev credits are exhausted or your site no longer has active Rovo Dev access, not just stale auth. So in addition…

Hey ya'll hey, This has come up in the Champions internal Slack as an FAQ @Crimsalytics @Tomislav Tobijas @Laura Campbell @Bryan Guffey please help spread the good word... There are a couple things happening here. First, Rovo is still being rolled out to Standard plans, so even if docs say it’s included, your site may not…

Hi @Putri This type of error (with a Trace ID) is usually a backend provisioning issue, not something caused by your browser or cache—so incognito/different browsers typically won’t fix it. If it persists, the best step is to contact Atlassian support and include the Trace ID so they can investigate on their side.

@sidnei_barcelos Welcome to the community. I think the main blocker here is that Rovo doesn’t reliably handle recursive cross-project hierarchy queries or nested JQL the way Plans/Jira do. So even a clearer prompt may still fail. This looks more like a current Rovo limitation than just prompt structure.

Hey ya'll hey! Great thread. Welcome to the community @Jon-Paul Sun @Stavros_Rougas_EasyApps & @Kris Klima _K15t_ offer useful alternatives, but don’t address whether Rovo can do it @Rebekka Heilmann _viadee_is closest technically, but suggests chunking without confirming limitations clearly The key point is that this is a…

Thanks @Florian Bonniec and welcome to the community @created 5th This is the right approach—Trace ID errors like this are backend provisioning failures, so only Atlassian support can investigate them. One thing to add: sometimes the site actually gets created despite the error, so check your email and existing sites…

Hi @ElEscarabajo If you’re referring to Rovo Dev, model availability (like Gemini variants) isn’t user-configurable and there’s no public roadmap confirming when specific models will be available. Rovo typically exposes a curated set of models, and new ones roll out gradually. So there’s no way to enable Gemini 3 Pro…

Hey ya'll hey—this wasn’t expected trial behavior. Atlassian recently changed how Rovo Dev access and credits work, and there was also a bug during rollout that caused users to be blocked early (even below 2,000 credits). So this isn’t normal usage. @dangertest if it’s still happening, raise a support ticket with your…

Yes to what @swat swat mentioned. And remember—Rovo-created whiteboards can exist in a temporary “Create with Rovo” state before being added to Confluence. In that state, they won’t appear in search, history, or space content. As @Jasmine Kaczmarek noticed, if something seems missing, check “Create with Rovo”—you may need…

Hey ya'll hey — adding some clarity here as there are a few different issues being mixed together. @asd @Peppe Iodice @Grafeeti 282 — this behavior wasn’t actually a real credit limit being reached. Atlassian confirmed this was a bug during recent changes to Rovo Dev credit handling, especially affecting users with a…

Cheers to @Marc -Devoteam- and @Rebekka Heilmann _viadee_ 's support. This type of error is usually a backend provisioning issue, not something you can fix locally. The Trace ID is key—support can use it to investigate. Also worth checking your email, as sometimes the site is actually created despite the error. If not,…

Hey @Heather Barnes I second @Rebekka Heilmann _viadee_ response. In automations, a Use agent step can’t run the agent’s own skills/actions—it only returns text, which you then use in later automation steps like Edit issue to update your custom field. The “Invalid Use agent action” error is usually a configuration issue in…

The billing page is a good first place to check, but for Rovo/Rovo Dev, there typically isn’t a working self-service cancel option yet—even if you can access billing. In most cases, you’ll still need to go through Atlassian support to fully cancel or remove it from your site.

Welcome to the community @Kristina Belanger and cheers to @Florian Bonniec for the support. Keep in mind - the Figma connector is supported, but Rovo’s ability to analyze file content is still limited. Simply installing the app or using Smart Links doesn’t give full access—Figma must be connected and indexed, and even…

Welcome to the community @Tran Khanh Vinh An @Rebekka Heilmann _viadee_ is right that this likely isn’t due to hitting a quota—Rovo usage limits aren’t currently enforced in a way that would stop a response mid-generation. That said, the behavior you’re seeing is more commonly related to timeouts, long responses, or a…

Hi @ines_barradas @Rebekka Heilmann _viadee_ is right about complexity, but one key addition: the issue isn’t just LLM limits—it’s also that Rovo agents don’t reliably execute multi-step JQL/data retrieval across hierarchies or APIs like that prompt assumes. A better approach is to break this into smaller agents or steps…

Adding to @Dave Mathijs ’s explanation @Jürgen Höfs —the confusion comes from seeing two separate credit systems side by side. Rovo (Chat, agents, search) and Rovo Dev (CLI, code tasks) track usage independently, but only Rovo Dev credits are tied to your current billing cap. The other usage is still shown for visibility,…

Adding to @Rebekka Heilmann _viadee_’s points—Rovo doesn’t always execute JQL queries the same way Jira does. Instead, it relies on indexed data and context, so even valid JQL may return no results if the data isn’t indexed yet or not included in the agent’s scope. Also double-check you’re in the correct environment (prod…

Hey ya'll. Rovo can modify Jira fields like description, but failures like “network error” are typically transient service issues, timeouts, or permission/scope limits, not a general capability gap. If it works sometimes (e.g., realtime translation), it’s likely a stability issue, not misconfiguration.

ROVO-512 doesn’t apply here because that ticket relates to specific limitations or bugs in how Rovo retrieves certain Jira fields, whereas this question is about access/configuration and indexing of Story Points. In this case, Rovo can work with Story Points (a standard field), so the issue is more likely permissions,…

Hey @Lukas Kovac Rovo can access standard Jira fields like Story Points, but only if they’re properly indexed and visible in your instance. If it says it has no access, it’s usually due to permissions, field context (e.g., not on those issue types), or indexing delays. Also, results can vary by rollout. Make sure the field…

Welcome to the community @René Herzog and @Altin Rovo Dev doesn’t currently have a standard self-service “cancel subscription” option in the UI. To stop billing, you’ll need to remove all users/licensing and/or let the trial expire. If you want it fully removed, the recommended approach is to contact Atlassian support to…

@jules1 welcome to the community. This looks less like a terminal issue and more like a Rovo Dev CLI input handling bug. A few users have seen similar behavior where Ctrl+C doesn’t properly release the input state, leaving the prompt unresponsive. Restarting the CLI is the only reliable workaround right now. If you can,…

I'd add you can control who can create agents and who can use specific custom agents. So you can limit parts of Rovo, but not overall access to Rovo itself.

Hi @Bowen Ji This happens because Atlassian’s MCP server uses OAuth 2.1 and does not support Dynamic Client Registration (DCR). Some Copilot CLI setups expect DCR or manual client credentials, which aren’t compatible here. So the failure isn’t your config—it’s a current compatibility gap. For now, this flow may not work…

Good question—this comes up a lot @jules1 welcome to the community. Setting DISABLE_TELEMETRY=true only stops usage data from being sent to Atlassian, but it doesn’t disable local CLI logging. Right now, there’s no built-in way to fully turn off Rovo Dev logs. The only real options are managing or redirecting logs at the…

I'd add to @Rebekka Heilmann _viadee_ by saying Rovo can index and surface Zendesk ticket data in search, which explains why you see results. However, summaries may not always generate—this can depend on indexing completeness, permissions, or how the query is phrased, and behavior can be inconsistent. So what you’re seeing…

Welcome @Sowmya Both @Rebekka Heilmann _viadee_ and @Ugnius Aušra responses are partially correct. Rovo can summarize sprint data and metrics, but it does not natively generate or embed Jira sprint reports (like burndown charts) into Confluence. Charts created in chat are temporary and not suitable for embedding. The…