Comments
-
Great question @Rebekka Heilmann (viadee)! To give you the direct answer for Claude: yes, an Org Admin needs to set this up centrally. Connecting your personal Claude client to the Atlassian MCP gives Claude access to your Jira/Confluence tools, but it does not automatically enable a Claude agent inside Jira. To get the…
-
Hi @Nikola Perisic - really sorry to hear this. Losing communication with your Rovo and Slack agents is not the experience we want you to have at all. This isn't something we've seen broadly and rather than guess at what might be going on with your specific site configuration, I'd recommend raising a support ticket at…
-
We're also really keen to hear how you're finding the new experience so far. What's working, what's not, what's confusing — all of it helps. A few ways to share: * In-product: hit "Give Feedback" inside Studio help menu or use the 👍👎 in chat * Right here: drop a comment on this thread * Chat with us directly: we'd love to…
-
Great questions, @Brian Taylor & @Dirk Ronsmans! The Studio beta is an org-level opt-in, so there isn't a way to enable it for just a pilot group or test it on a sandbox site first — once an admin opts in, the new Studio experience replaces the old across the org. That said, the core agent platform is unchanged — your…
-
You’re reading it right @Jordan Wilkinson — you can create Forge apps directly from Studio without writing code and kick off deployments from the Studio UI, no terminal required for the common flows. We’re really excited about this too!
