Rovo Agent actions
Actions are what Agents use to take their responses and do something with them like post a comment, draft and publish a Confluence page, or create a Jira issue.
There are dozens of different actions that Agents can perform, you can see the full list of Actions while you’re creating or editing an Agent of your own. Otherwise, you’ll see the actions a particular Agent can perform by viewing its profile page.
While there are many actions to choose from when you’re creating or editing an Agent, try creating your Agent for a very specific use case. We recommend selecting fewer than 5 actions for each Agent.
To give your Agent actions when you’re creating or editing:
Select Add actions.
From the actions window, you can browse the actions, search for them by name, or filter the actions by product.
Select the actions you want for your Agent via the checkboxes, then hit Save.
Actions will appear in your Agent's profile so people browsing for Agents can find the one best suited for their needs.
Use actions while chatting to an Agent
Simply ask the Agent the same way you might ask your teammate. For example:
“Create an issue in Jira about writing a research summary”
“Create a Confluence page named “My week in summary”
“Create a PIR confluence page for this incident”
“Suggest epics for issues in this project”
“Move this issue to the “In progress” status”
“Comment on this issue with some suggested improvements to the description”
“Find requests with a similar summary in this project”
Some actions have limitations or required fields a user will need to provide the agent. For example:
Bulk actions in Jira are currently limited to 20 issues at a time.
Creating issues in Jira will sometimes require additional input from you if there are required fields.
Calendar invites created with an Agent are limited to 4 attendees at once.
The Agent will respond asking for confirmation. No matter the action, you’ll be asked to confirm. Sometimes, for things like deleting information, you’ll be asked to confirm again.
Third-party actions for Agents
Third-party Agent actions are currently in beta.
Actions that allow an Agent to act outside of an Atlassian app require that you connect your Atlassian account with the third-party product the first time you use it. Doing so ensures that that Agent can’t access information or do anything that you wouldn’t normally be able to do. In other words, it ensures the agent has the access required to work on your behalf and no additional access.
During the connection process, you'll be redirected to the third-party authentication page where you can grant access. Once you’ve granted access, you can continue using that action in future chats and won’t need to authenticate again.
Any third-party actions taken by an Agent will appear as if taken by you, the user of the agent. For example, if you ask an Agent to send a Slack message, the message will appear as if you sent it.
To revoke access:
Go to the Account menu via your profile avatar in the top navigation bar
Select Manage account
Navigate to the Connected apps tab
Select the third-party app for which you’d like to Revoke access.
You can re-authenticate later if you change your mind and want the agent to perform third-party actions again in the future.
Was this helpful?