Alexander Nilsson Specialist

Great Overview! Thanks for sharing. 

Hi there, your read on this is correct, and it is a Windows-specific quirk in how the auto-upgrade swaps the plugin folder rather than an actual permission problem. On Windows the upgrader downloads the new build into rovodev-temp-... and then renames that folder onto the existing rovodev folder. Windows refuses to let a…

Hello Hongxu, before treating this as a phantom close, the one place that will tell you exactly what happened is the alert's Activity Log, so start there. Open the alert and go to the Activity Log tab on the Alert Details window. It records every state change together with its source, so it will show whether the close came…

Hi Frank, fair callout, and you are right. The wording was looser than it should have been. Rovo Dev is its own agent harness. It does not run Claude Code or the Codex CLI. What you choose is the underlying LLM via the /models command in the CLI or IDE, today Anthropic Claude (Haiku, Sonnet, Opus) and OpenAI (GPT-5.x and…

Hello Ezhumalai, the sequence you described, where initialize and tools/list succeed but every tools/call fails while the same query works over REST, narrows this down well, and the exact error string you are hitting is actually documented. "We are having trouble completing this action. Please try again shortly." is one of…

Hello Sameer, thanks for your great questions. The answer depens whether the agent was built in the Rovo Studio UI or as a Forge app, because only one of those two paths supports configuration as code today. If you build the agent as a Forge app using the rovo:agent module, you already get the workflow you described. The…

Hello Radu, good, this narrows it down a lot. The resource parameter and code_challenge_method=S256 are both on the authorize URL now, so the client side is doing the right thing. The useful part of your update is the other detail: the same client works for a colleague on a fresh free site and fails for you. That tells us…

Hello Radu, good news first: your config file does not need a new field. The part that has to change is one parameter in the OAuth requests your client builds. The JSON stays exactly as it is: { "servers": { "atlassian": { "type": "http", "url": "https://mcp.atlassian.com/v1/mcp/authv2" } }} The missing piece is the…

Hello Marissa, raising the ticket is the right call here, especially since you have cleanly ruled out the permission cause as a system admin with explicit admin on both the Jira and the Confluence side. Furthermore what you are describing is an exact match to a bug Atlassian already logged and closed. Since that fix…

That's a great overview! Thanks for sharing it with us.

Hello Ajith, your plan is solid and aligns almost exactly with what Atlassian documents as "Method Two" for instances with a high volume of attachments. This is a well-established path, not something you'd be improvising. The documented method is: take the site XML export with attachments excluded, make a separate copy of…

Hello Marissa, the symptom you describe, where the space connects fine and is then gone again after a refresh, is a known one. Two separate things can cause it, so it is worth ruling out the permission cause before assuming a defect. Per Atlassian's documentation, the documented cause of this exact symptom is a permission…

Hi Fazila, Great question, and thanks for reading so closely. The structure is actually the other way around, so let me clarify. The twg ... part is the real command. You run it yourself in your shell, it queries the Teamwork Graph and returns the json. It is not just a reference to something the AI calls internally. The…

Hello Febin, good use case to share, and the limits you ran into are exactly the ones that show up when chat-driven Rovo gets pushed into recurring reporting. The fix is to flip the architecture: stop prompting from Chat, invoke the agent from Jira Automation instead. Atlassian supports this directly. You can wire a "Use…

Hello Tom, good catch, you found the right line. The reason only one team comes through is that queue_message["alert"]["team"] is the legacy single-team field and only ever holds one value, even when the alert routes to multiple teams. The full team list lives in queue_message["alert"]["responders"], which you can see in…

Hello Pierre, the issue is how you're reading the field values inside a Simple Scripted Validator on a create transition. The issue binding at create time does not yet reflect what the user is typing into the create screen, so issue.customfield_14690.value is reading from an issue that essentially does not exist yet. The…

Hello Fatima, thanks for sharing the log lines, they pin down what is going on. To your first question: yes, this confirms a proxy or firewall problem on the outbound path from your Confluence node to Atlassian Cloud. The smoking gun is the combination of ProxyTunnelEventListener connectFailed and SocketTimeoutException:…

Hello Bhanu, this one comes up often and the good news is that for your sales rollout, the cost picture today is mostly zero. Let me go through your points one by one. On 1 and 2: there is no separate licence and no per-call charge from Atlassian for the MCP server itself. Rovo is bundled into all paid Jira, Confluence,…

Hello Fatima, those generic messages are by design, not a bug. The CCMA UI never shows the real cause, it always points at the troubleshooting page. Atlassian acknowledges this gap in their own public issue tracker, ticket MIG-2440, currently with status "Gathering Interest", and the documented workaround there is exactly…

Hello, the Rovo agent gave you outdated information. Tags on Atlassian Home goals and projects are accessible through a public API, just not the one the agent is reaching for. The "Topic" UI in Atlassian Home is now called Tags, and it is fully queryable. In January 2026, Atlassian released GraphQL APIs for Goals and…

Hello Jarryd, you are right that the in-product Rovo agent skill catalog is thin on the Bitbucket side. The official Rovo Chat capabilities page only lists one Bitbucket skill today, "Comment on PR", and there is no documented read skill for PRs, reviewer approvals, or comments yet. So your Scrum Master Agent really cannot…

Hello Deepak, thanks for your feedback. Can you share with us the used endpoint (without sensitve Data) and the exact error message? Thank you and greetings, Alex

Hello Deepak, the symptom you described is a near textbook case of the difference between regular API tokens and service account tokens, and it is documented as such by Atlassian. Service accounts can only create scoped API tokens, and scoped tokens do not work against the https://<your-domain>.atlassian.net/... base URL…

Hello Fariah, thanks for your question. "connection failed" with a Jira API token is almost always one of three things on the Jira side. First, the username field. For Jira Cloud the basic auth credential pair is your Atlassian account email address plus the API token, not your Jira username, not your display name, not the…

Great to hear. Thanks for your feedback :)

Hello Danielle, the issue almost certainly comes down to how the smart value resolves for a select-list field. When you use issue.Change rating inside an equals() call, the smart value does not return the plain option label "Low" as a string. It returns an object. The equals() function then compares that object against the…

Hello Engy, there are two ways to do this in Jira Service Management Cloud, and the better fit depends on whether the priority question in each form can be linked directly to Jira's Priority field. The cleanest option, if it works for your setup, is to link the form question directly to the Jira Priority field. In that…

Hallo Deepak, good question for ACP-620 prep. Short answer: yes, team-managed scrum projects in Jira Cloud do support parallel sprints today. The note you remember reading ("only company-managed") is outdated. The difference is in how you turn it on. In company-managed projects, parallel sprints is a global Jira Software…

Hallo Amar, good catch on posting the full safety check output, that points the answer in two directions at once. Bitbucket 10 ships with UPM 8.0, where app signing is enabled by default but no certificates are bundled with the product. So after the upgrade, the truststore folder exists but is empty, which is exactly the…

Hello Vitheya, thanks for your question which is important for anyone offering AI-based Forge apps through the Marketplace. Unfortunately I haven’t tried implementing detailed token usage tracking myself yet, but I found some relevant information in the official Atlassian Forge documentation that may help point you in the…