Dr Valeri Colon (Connect Centric) Community Champion

@Drag Me this is a bit of a gray area. Trial access to Rovo Dev CLI/IDE is limited and not consistently enabled, so some users need a paid plan to use it—but it’s not a formally announced blanket removal.

@Habib ZOUARI this isn’t just a “token limit” issue—what you’re hitting is a mix of LLM output limits + Rovo action payload constraints, and there’s no documented hard limit or truncation signal today. Large single-turn JSON outputs aren’t reliable. The current pattern is to generate in chunks or stages, then pass smaller,…

@raj13 welcome to the community. There’s been some confusion around this. What you’re seeing is generally expected—not a billing bug. On the Rovo Dev Standard trial, CLI and IDE access (VS Code) are often not included, so you can hit entitlement errors even after adding payment details. Access can also vary based on…

@Bhavana Sesha Sai adding to @Arkadiusz Wroblewski’s point—this also shows up quite a bit with Rovo’s Create work item skill today. Even if the error says “set,” it’s usually a field mapping or validation issue (required fields, custom fields, or unsupported fields). If you’re using an Epic as a template, try simplifying…

@nick welcome to the community! Today, Rovo external MCP connections are typically configured at the org level, so they use shared/service account auth, not per-user OAuth by default. Per-user delegated auth is only possible if the MCP server itself is built to handle that flow. Rovo doesn’t natively prompt each user to…

I do enjoy a good screenshot! Thanks @Tomislav Tobijas This still looks like a real gap rather than missing config. Atlassian’s MCP docs now support read/write operations in general, but I’m not seeing issue properties documented as an exposed MCP capability yet. So your GitHub issue + feedback path makes sense, and today…

Great responses @Barbara Szczesniak and @Evgenii and welcome @Ahmed Boghdady. Only this left to add is: it’s not just “size”—also structure, headings, and relevance scoring affect retrieval.

@Mario you’re not missing anything—this is expected today. Those messages (like “Your action… executed”) are part of Rovo’s built-in system response for actions and aren’t configurable in Studio. Agent instructions won’t override them. What you can control is the follow-up message after the action, but the system…

@Prashant Sarwal welcome to the community. Adding to what @Fabio Racobaldo _Catworkx_ shared—after activation, a few other things can affect visibility. Make sure AI features are enabled in Atlassian Admin (Apps → AI settings), and that your org email uses a company domain (not Gmail), as that can block access. Also, Rovo…

@MariaKolesnikova welcome to the community. This is a common ask. Today, model selection and “reasoning effort” aren’t exposed in Studio—those are managed behind the scenes, while CLI has more flexibility. Rovo is designed to balance performance, cost, and safety automatically, which is why it feels like a one-size setup.…

@Vera Diaz to add to @Kai Krause ’s point—today Atlassian provides high-level info on models and controls, but not specific model versions or version history in a way that supports audit-level traceability. Rovo uses a mix of LLMs that can change over time. For regulated use cases, most teams rely on Trust Center docs +…

Hi @Harsh Raval there’s no supported public Rovo API for this internal gateway response, so I wouldn’t rely on studio.atlassian.com/gateway/api/assist/rovo/v1/agents/{id} for automation. Atlassian hasn’t documented an expand=actions parameter or replacement endpoint. If actions is now empty, it’s most likely an internal…

@Mario adding to what @Andy Rusnak shared—this is also a known limitation with Rovo today. When request types have strict validation (required fields, formats, assets, etc.), the agent doesn’t always populate them reliably, which leads to these 400 errors. A common workaround is to create a simplified request type for the…

@김도형 welcome to the community. I’d add one nuance to @Peter_DevSamurai’s solid answer—Rovo isn’t directly “reading everything,” it’s acting as an AI interface over Microsoft Graph + your permissions model. The connector uses app-level access, but results are still filtered at query time based on the user’s access. That…

@Josh Thanks for the support. @Darryl Lee has a habit of asking a thought provoking question then bringing the Champions community to a mic dropping moment.

@Fabio Genovese _ArtigianoDelSoftware_ you inspired it all. @Josh makes me happy the timing was right to make this post helpful.

@Habib ZOUARI —this is where things get tricky today. For batching, there’s no fine control over when the agent asks for confirmation—that’s part of Rovo’s interaction model. Keeping steps small and clearly scoped helps reduce interruptions. On large content, no firm timeline, but this is an area Atlassian is actively…

Thank you for the support @Josh and the Champions that keep asking the hard questions.

Welcome to the community @Maurice Adams Today, those options are limited. You can set branding (like agent icon) in some places, but full chat UI customization across the portal isn’t supported yet. Also, Rovo/VSA flows don’t allow a true “bot-only first, then portal” switch—portal behavior and request flows are still…

The great @Jimmy Seddon this is most likely a UI/display issue, not an access problem. Rovo can still index and use the pages, but sometimes the titles don’t render correctly in the agent config, so you see blank lines. It can vary by user due to permissions, caching, or indexing state. I’d confirm the user has access,…

@Habib ZOUARI again great questions—this is a real limitation people are running into. There isn’t a clearly documented hard token/character limit for Rovo action inputs. Limits come from the underlying LLM + platform, and truncation can happen without warning. There’s currently no structured truncation signal exposed to…

Hi @daften! I second much of what @Arkadiusz Wroblewski has said. What you’re seeing lines up with how Rovo works today. One key thing: Rovo isn’t the AI itself. It’s an interface that connects to underlying LLMs + Atlassian data/tools, so behavior depends on how well those models, tools, and permissions line up. Rovo = AI…

@Maniteja Varanasi that’s helpful context—if new users can authenticate but existing ones can’t, that points more to a session/OAuth issue or partial rollout/regression, not just config. For API token auth: this has to be enabled at the org level under Atlassian Admin → Security → API tokens / MCP settings (exact naming…

Welcome to the community Harshit @JIRA ADMIN This usually isn’t just a permission issue. With the Rovo MCP/Claude setup, if you’re only seeing read-only tools or failed creates, it’s often due to auth method or scope limitations, not Jira permissions. A few things to check: Ensure you’re using Basic auth (email + API…

Hey @Mario This is expected behavior today. Rovo Slack agents often use the identity of the connected/service account for context, so greetings can default to that instead of the Slack user. Even if you instruct it otherwise, identity handling isn’t fully customizable yet. There’s no reliable way to override this…

Greetings @serge calderara Rovo isn’t deeply integrated with Xray today. It can help suggest or draft test cases based on requirements, but it can’t reliably handle full lifecycle actions like creating, executing, or reporting tests directly in Xray. Think of it as assistive (ideas, drafts, summaries), not a full test…

@Nayan Korat welcome to the community. Today, Rovo Dev expects the .rovodev folder at the repo root and doesn’t support configuring a custom path. It won’t reliably read instructions if the folder is nested elsewhere. If your repo structure can’t accommodate it, the common workaround is to keep .rovodev at root in a…

@Mariono worries—this part can be confusing Think of it like this: The 👍👎 buttons = fixed by Atlassian (you can’t change them) The agent = what the bot says and how it behaves Workflows = what happens next (like creating a ticket) So: You can guide how the agent responds, but not control it exactly You can’t change the…

@Iain Phillips thanks for checking all that—that helps narrow it down. If none are showing (even the smaller repos), it’s likely not size-related. Backfill completing just means indexing worked, but Generate Code depends on the GitHub org being explicitly linked to the Jira site used by Rovo Dev, not just the connector.…

Major thanks to you this round @Rebekka Heilmann _viadee_ for asking Atlassian to jump in on the Rovo Dev issue. The intervention kept things from snowballing.