How can a Rovo Agent read Jira Automation Rules natively without manual JSON export?

[Henrique Bittencourt]

Hi everyone,

I am building a Rovo Agent to analyze Jira Automation rules for performance bottlenecks and risks.

Standard Rovo Agents can't read administrative configurations natively because they aren't indexed in the Teamwork Graph. The only out-of-the-box workaround is to manually export the rule as a JSON and paste it into the chat.

If I build a custom Forge app to give the Rovo Agent this ability, the Automation REST API explicitly blocks it. As noted in the docs: "Forge and OAuth2 apps cannot access this REST resource." I want to avoid building a Basic Auth / Service Account workaround just to fetch the rules.

Is there any native way for a Rovo Agent (or custom Forge Action) to access Jira Automation rules directly without manual JSON inputs or external API tokens?

Thanks!

[Ajay _view26_]

Hi @Henrique Bittencourt 

This is a known gap and there are existing feature requests on the Atlassian developer community forum asking for Forge access to the Automation API. Adding your voice there is the best way to push for a native solution.

[Rebekka Heilmann _viadee_]

To say it in Rovo's words:

I can see you're currently viewing an existing automation rule in Studio. However, I'm not able to review or analyze existing automation rules at this time - this functionality is currently limited to creating new automation rules from scratch.