nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rovo as a Jira Admin?

Shai Gilboa_8ate5r

As Rovo is being rolled out into the different Atlassian tools, allowing users to ease work, finding information for them, creating work items and pages sections etc, how about it being also developed to help the Jira Admin side of things?

Jira administration is mostly a click-ops mess. Most definitely when there is no or little central management of the the tool, and when Team spaces are involved.

The existing API for administrating Jira, is complex, full of inconsistencies, documentation errors, and even errors on how the API behaves, thus using the API for limiting down click-ops is also frustrating, more over if one is looking for a generic solution which can support a IaaC approach with proper CI/CD to modify Jira's configuration (personally working on such python package - internal to the company).

Doesn't it make sense to have Rovo also broaden to support administration tasks (adding fields/contexts, creating workflows, updating screens, etc,) based on well provided prompt?
Obviously this will need to be supported first in a sandbox with the ability to promote what ever Rovo did, once reviewed, to production. This too should be supported by Rovo.

WDYT?

Accepted answers

Nikola Perisic

Hello @Shai Gilboa

I was planning to do the similar thing, which was adding users to the project and assigning them roles as and admin to reduce the repetitive process and automate it with Rovo. Rovo cannot do such things because it doesn't have permissions to do these operations. Same thing goes for screens and fields. Workflows though on the other hand do work, you have the Workflow builder agent that does this for you and this was released by Atlassian.

Rovo was designed for easier navigation, better data collection in one source of truth with teamwork graph.You can at any time experiment with Forge agents, but this also leads to the question will Rovo be able to do these things.

All comments

Nikola Perisic

Hello @Shai Gilboa

Shai Gilboa_8ate5r

Thank you @Nikola Perisic ,

I'll check about the workflow builder, however what I meant in the above, is to ask, what actually is stopping Atlassian from developing an Admin Rovo (or name it differently) which based on prompt, uses the complex APIs and does the heavy lifting for us?

I know and understand the main and initial reasoning behind Rovo, and there are many tools out there, which when given access to Jira, do the same (see glean for example).

One could of course go and try and develop an external LLM agent that utilizes the APIs, but it seems this is something that can give a great boost for Atlassian to do (might even get them to fix some APIs on the way).

Nikola Perisic

@Shai Gilboa

Rovo is limited doing this for security reasons. This was the response from the agent itself:

For privacy and security, assistants like me don’t have direct access to your Jira instance or its API.
All actions that change permissions, users, or project settings must be performed by a human admin within your organization’s Jira environment.

Shai Gilboa_8ate5r

@Nikola Perisic

I understand and know the current limitations.

I'm not speaking of the present. I'm saying why not in the future.

These actions can be controlled and secured, let alone limited.
And of course be part of a bigger process of doing them in a sandbox, have human to review and approve and only then promote to production.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-cloud

jira-administration

rovo-atlassian-intelligence

rovo