Dr Valeri Colon (Connect Centric) Community Champion

@Karen West thanks for tagging me- I appreciate the update. Unfortunately, it seems Rovo is still inconsistent with wiki-markup tables, especially when scenarios are involved. This isn’t a Skills issue; it’s a rendering limitation in the model layer. Even with an exact template, it can fall back to markdown or reinterpret…

@Patricia Modispacher _K15t_ thank you for your continued support as a community champion and partner.

Another great question from our internal Slack channel is the difference between the Rovo and Teamwork Graph connectors: Teamwork Graph connectors feed data into Atlassian’s unified graph so Jira/Confluence/Rovo can search and reason over it. Rovo Connectors are scoped to Rovo and optimized for chat-style retrieval. Some…

@Rebekka Heilmann _viadee_ Skills didn’t replace Actions. A Skill is a packaged capability (a module or modularized actions)—built from two or more Actions plus the logic that ties them together. Actions remain the individual trigger or task- which, I suspect, is the source of the confusion. So yes, a Skill can be executed…

@Jhon Pereda Rovo Dev runs commands inside its own sandboxed process, not your interactive PowerShell session, so it can’t see PATH entries you’ve set globally. If git isn’t on the system PATH (or installed in a standard location), the CLI won’t find it. Add Git’s bin folder to the system PATH and restart the CLI. After…

@刘宇哲 Rovo Dev 的 token 不是只按你看到的 500 行代码算的。每次命令都会把上下文、相关文件片段、系统提示、多轮对话等一起发送给模型，所以一次“任务”可能触发多次调用、累计很多 token。你看到的 800 万是总消耗上限里的累计值。如果确实异常，截屏日志后提工单，请他们核对账单与配额。

Those entries are unmanaged “shadow IT” app installs created when users connect Power BI or Salesforce without admin oversight. To see who’s using them, go to Admin Hub → Products → Connected apps and review the audit logs. I agree with @Valerie Knappapproach, deletion isn’t self-service for these autogenerated app…

@Anugrah Sharma This happens when VS Code still has a stale MCP auth record, even after reinstalling. The MCP server won’t show the OAuth prompt until that entry is cleared. Fully delete the folder:~/.config/Atlassian/mcp (mac/Linux) or%AppData%\Atlassian\mcp (Windows),then restart VS Code. If the callback URL still fails,…

@Mujahid Maqsood to add to @Ciara - _Eficode_ response: There’s no telemetry or “decision log” exposed for agent runs triggered by Automation. When an Automation rule calls a Rovo agent, the LLM’s reasoning and action history aren’t surfaced anywhere in Jira or Rovo Studio. Only direct chats show traces. If you need…

@Mark W_ Bell Acronym Definitions can’t be disabled org-wide today. Each user can turn it off individually, but admins don’t have a global switch yet. If incorrect definitions are creating risk, the best path is to submit feedback through Admin Hub → Rovo → Feedback—Atlassian is tracking requests for admin-level control…

@Anthony France and @Julien Rovo Dev no longer supports personal API keys—OAuth is the only option now. The frequent re-auth you’re seeing happens when the local token cache breaks or the site mapping changes. Clearing the .rovodev folder and re-logging in usually stabilizes it. If token drops continue, share your logs…

@venkatasai.pulluri to add to @Rebekka Heilmann _viadee_ and @Nikola Perisic resources: The agent output is valid, but Automation treats it as a string with hidden whitespace. Wrap the raw value in a trim before…

@Gong Rzhe The Atlassian MCP server only exposes SSE today. There’s no announced timeline for Streamable HTTP or other transport formats. If your use case needs it, the best path is to log it through the Developer Community so Atlassian can factor it into the MCP roadmap.

@Michael Nentwich @Chris McDaniel Rovo can’t be removed self-service—it’s tied to the org. Atlassian confirms in ROVO-144 that only Support can disable it so the org can be deleted. If you’re stuck in a loop, submit a ticket through admin.atlassian.com → Support → Billing & org management; that path reaches a human.…

@Marinela Boyadzhieva @Pilar, Vagner Those 400s usually mean Rovo can’t see the full create/transition schema for that project. Even in Rovo Chat, if a required field isn’t on the project’s Create/Transition screen, the action fails and the MCP tools show as “disabled.” Check the project’s issue type config and make sure…

@Dang Quang Yes—Rovo Chat and Rovo Agents don’t have identical data access. Rovo Chat uses built-in org search, including Atlassian Teams. Custom agents only see the data you expose through knowledge sources or skills, so they can’t fetch team members unless you add a Skill that calls the Teams API. Once that’s added, the…

@Fabio Santos A 401 on an Assets field means Rovo can see the issue but not the linked object. Assets permissions are separate from Jira’s, so adding atlassian-addons-admin isn’t enough. Make sure the object type and its attributes are readable by atlassian-addons-project-access in the Assets schema. Once the object type…

@Oliver Christie That message means the Slack app isn’t linked to your Atlassian cloud site yet. In Slack, open the Rovo app → Settings and complete the onboarding to pick the site you want Rovo to use. If you don’t see your site, your admin must enable Rovo and allow Slack as a connected channel in Admin Hub → Rovo. Once…

@Dayanand Biradar Rovo can disappear if the org-level entitlement is disabled, a trial expires, or Atlassian rolls out a backend change that temporarily removes access. It can happen even if nothing changed on your side. Check Admin Hub → Rovo to confirm the feature is still enabled for your org. If it’s missing there too,…

@Thomas Pedersen Ljungstrom Rovo can’t query Assets in Automation today. The built-in “Rovo Expert” ignores prompts outside its scope, and Assets data isn’t exposed to Rovo as a searchable source. To automate lookups, you’ll need the Assets REST API or an Automation action that queries objects directly. Once Atlassian adds…

@Eshwar Sachidananda Rovo only supports GitLab cloud today. Self-hosted GitLab isn’t available yet, and Atlassian hasn’t announced a rollout date. The connector depends on hosted-API scopes that self-managed instances don’t expose in a consistent way. If your team needs this, it’s worth sending feedback through the Rovo…

@王晋鹏 That message is a generic Rovo/Jira error that appears when the agent can’t read the issue schema or a required field fails validation. It’s usually caused by a missing required field on the project’s Create/Edit screen. Check the project’s issue configuration, make sure all required fields are visible, then retry. If…

@Adam Tumidalski I read that you solved your own question by checking your configuration. For those that are following along, a 400 on jira-issue-create-bulk usually means the Create Issue skill isn’t fully configured. Rovo won’t show “Create issue” unless the project’s issue types and required fields are exposed to the…

@Roger Zhen Wang Rovo can read fields, but it won’t reliably audit custom fields unless the Jira schema is fully exposed through the skill. Even if you provide customfield_10067, the agent may not see it if the field isn’t on the project’s screen or the skill isn’t mapped to it. Check that the field is on the…

@Katie Pruess and @Fazila Ashraf Rovo can’t access Velocity Reports today. Those reports are rendered through authenticated, JavaScript-loaded pages, and Rovo can’t log in or execute scripts. Giving atlassian-addons-project-access admin rights won’t change that. The only workaround is exposing the underlying data through a…

@HunterWang A 403 on the credits check means the org you’re hitting isn’t entitled for Rovo Dev, even if auth succeeds. The fix Mack shared only works when your site actually has the SKU. Adding atlassianBillingSite won’t bypass entitlement and will throw the “unknown field” warning you saw. Verify the exact site URL in…

@Matt P, @Rebekka Heilmann _viadee_, @Ciara - _Eficode_ @Val Knapp and I had a whole Slack discussion on your question. Here's my add: Credits and tokens don’t convert 1:1. The old 5M daily tokens were part of the beta and aren’t comparable. In paid plans, 2,000 credits/month covers normal usage for chat, agents, and…

@arwaz shaikh That message means the org you’re logged into doesn’t have Rovo Dev enabled, even if your personal account shows the feature. Make sure you’re signed in with the same Atlassian org the CLI is targeting (--site-url). If the org has multiple directories, re-auth with acli auth login and try again. If it still…

@Jacob Antoine As of now Rovo is supported in Microsoft Teams via its Teams Connector, but that support is for indexing Teams content (chats, channels) and making it searchable—not for live Rovo Chat or Agent interactions inside Teams. If you’d like real-time agent chats in Teams, you’ll need to wait until Atlassian…

@Sam Ben-David Rovo agents don’t store long-term memory from chats. Anything you tell the agent during a conversation is temporary and won’t persist. If you need the agent to “remember” rules, facts, or preferences, add them to the scenario or a knowledge source. That’s the supported way to make the behavior consistent…