Inconsistent “Confirm” Button for Updating Description Field via Rovo Agent in Different Scenarios

[Sven Odermatt]

We have developed a Rovo Agent that currently supports two scenarios. In both scenarios, the agent is supposed to record the result of its analysis by updating the “Description” field of the work item.

In one of the scenarios, this works reliably: at the end of the analysis output, the agent displays a “Confirm” button. When this button is clicked, the “Description” field is updated as expected.

However, in the other scenario, the agent usually only outputs the analysis result, and the “Confirm” button for transferring the result to the “Description” field is frequently missing (although it does appear occasionally).

The “edit work item” capability is configured in both scenarios. The instructions for saving the analysis result to the “Description” field are identical in both cases.

Has anyone experienced similar behavior or can suggest what might be causing this inconsistency? Any advice or troubleshooting tips would be greatly appreciated.

Thank you!

[Tomislav Tobijas]

Hey @Sven Odermatt ,

I think, as this is quite new functionality, that this is due to how scenarios and triggers are interpreted in each scenario. There's an open feature request to improve how Agents handle confirmations: ROVO-261: Enable Rovo Agents actions with confirmations through Jira Automation 

As for scenarios, the agent will only use the instructions for the default one when no other scenario is triggered. I guess that if scenario logic or triggers are not set up consistently, that will lead to different behaviors. 👀

You could try to simplify your agent's skills and scenarios (together with double-checking scenario triggers and instructions) to see if that improves consistency. 🤔

I guess the best thing is to vote and leave a comment on the linked feature suggestion.

Cheers,
Tobi