Feature Request: Bulk import and API management for Rovo sub-agents and instructions

[Yuvie Naidoo]

Hey Atlassian Community,

I have been migrating a large set of intents from a legacy chatbot tool over to Rovo sub-agents this week and one of the biggest pain points has been that there is no way to bulk-create or bulk-update sub-agents, instructions, or triggers. Everything has to be done one by one through the Rovo Studio UI.

What would help:

• An API or file-based import to create or update sub-agents, instructions, and triggers in bulk
• Even a simple CSV or JSON import in the Studio UI would be a big improvement
• The ability to export, version, and restore agent configurations for backup and environment promotion

What we tried:

We also toggled on the new V2 agent model to see if it changed anything on this front. No visible impact on the build experience. If V2 is meant to address this, it is not surfaced to builders yet.

Why it matters:

If you are migrating from an existing intent-based system at any kind of scale, the one-by-one UI approach is a real bottleneck. It also makes it impossible to manage agents as code, which is a standard expectation for enterprise tooling.

Would love to know if others are hitting this and if there is anything already in the roadmap.

[Rebekka Heilmann _viadee_]

Hi @Yuvie Naidoo - welcome to the Community,

Studio doesn't have any public APIs yet and also no import/export functionality. I am actually waiting for similar features as well, although I'd be happy with Read access to begin with.

You can check existing feature requests/suggestions in JAC: Rovo - Issues - Create and track feature requests for Atlassian products.

See https://jira.atlassian.com/browse/ROVO-516 for example.

You can vote and comment. If you want something added, it's easiest to go through support.atlassian.com

They can create new suggestions on there. The Atlassian Team doesn't regularly check the questions on here unless prompted to, so a direct conversion from this post to JAC is unlikely.

---

Changing the Agent model doesn't do anything feature-wise. It only switches the used LLM for the Agent.

You can switch to the new Studio version if you haven't already. The new, unified AI building experience for Rovo S... - Atlassian Community That will give you a different UI and more capabilites, but doesn't include any import/export feature either.