The Rovo agents don't complete the action, but say they do.

[Tricia Savage]

I am walking through the training and learning more about Rovo Agents. They are (sort of) good at answering my question and search. But they are not good at taking the action, and say they did. Using the Issue Organizer,

I asked: can you remove the issues in the CUAT project from the release: Portfolio Template Config v1.0 that are not resolved as done?

I get: 

I've successfully removed the "Portfolio Template Config v1.0" fix version from the issues in the CUAT project that are not resolved as "Done". You can view the updated list of issues 9 Issues.  

But the Release/Fix Version field is still populated. Is it because the fix version is not a listed action?  can I edit the provided Agent to provide a response that the requested action is not something they can do? 

[Tricia Savage · Accepted solution]

Another example I build the service triage OTB agent into an automation that supposedly is well within the abilities of the agent. when email request created, use agent to suggest better request type (success), update request type (fail), comment with request type change (success). again, it says it is successful, but it is NOT successfully completing the field edit change I want. I tried to use https://support.atlassian.com/rovo/docs/agents-in-automations/ and what I am trying to do is right on the page...help a sister out please! 

[Dr Valeri Colon _Connect Centric_]

First and foremost #WOMENINTECH 

Rovo agents can only perform actions explicitly enabled during their configuration. If the "edit fix version" or "update request type" actions aren't selected, the agent will simulate success without making actual changes. Edit the agent to include the necessary actions and adjust its instructions to handle unsupported requests appropriately. 

Original prompt behavior:

"I've successfully removed the fix version..."

Improved instruction:

“If a user asks to remove or change the Fix Version field, respond:
‘This action isn’t supported by this agent. Please use Jira’s bulk edit or ask an admin for help.’”

Original behavior:

"Successfully updated the request type to 'Access Issue'"

Improved instruction:

“Before claiming any field update, confirm the agent has that permission. If not, respond:
‘I can suggest the correct request type, but I don’t have permission to update it. Please update manually or use automation.’”

General safeguard:

“If an action is requested that you’re not explicitly configured to perform (e.g., change project, delete issue), respond with:
‘Sorry, I’m not set up to perform that action. I can help with X, Y, and Z.’”

https://support.atlassian.com/rovo/docs/agent-actions/