Share feedback on AI in Atlassian Administration

[Vanessa Lee]

Hi organization admins,

We have an exciting opportunity for you to share direct feedback with the Atlassian Administration team to help shape the admin AI experience. We're developing Rovo skills to handle specific repetitive admin tasks so you can focus on strategic initiatives. Rovo skills are purpose‑built actions in Rovo Chat that help you carry out specific work-based actions. We welcome you to join a call to test out new features and provide live feedback.

What’s involved in the research:

• Sessions are 45 minutes long and conducted over video-conference.

• During the research, we’ll be asking you questions about your role/company, your current workflows, and your experience with AI. We’ll then share some prototypes and ask you to complete some tasks and provide feedback.

• As a token of our appreciation, you'll receive an e-gift card worth $50 USD after completing your session.

If you’re interested in participating, please fill out this form to be considered. If you have any questions, feel free to reply to this post. Thank you!

[Gregory Kneller]

Hi Vanessa,

This looks like a great initiative - I’d be happy to take part.

In my day-to-day work as a Jira/JSM architect, I already use a mix of AI approaches to analyze configurations and spot configuration debt (workflows, schemes, fields, permissions, etc.). This includes working with XML backups, AI-assisted analysis, and generating scripts for bulk changes.

A few things I keep seeing in real projects:

- A lot of admin work isn’t really "repetitive" - it’s about understanding messy, inconsistent configurations
- There’s often a need for bulk or cross-project changes, which are still quite limited by the Jira API and current tooling
- These situations come up often in larger Jira Cloud migrations, where structured AI actions could significantly reduce manual cleanup and standardization work
- For repetitive tasks, AI is already effective via scripting - any capable AI coder can generate automation

Because of that, I see Rovo skills as useful, but as part of a bigger picture:

They can help with structured actions, but the real value is in connecting analysis -> decision -> execution.

What I’d be especially interested in exploring:

- How far Rovo goes beyond simple task execution
- Whether it can help identify patterns (like duplicated workflows or unused configs)
- How it deals with instance-wide context
- What limitations exist compared to API/script-based approaches

Happy to test this and share practical feedback from enterprise environments.

Best,
Gregory

[Rune Rasmussen]

Applying seems to require creating a User Interviews account.
This is not the norm. At least it hasn't been a requirement in the several previous interviews I've participated in.

Is that intended?