Get to know Rovo
Knowledge sources for Rovo Agents
Aside from being able to read and sumamrize via URLs from some connected products (Google and SharePoint), Rovo Agents currently doesn’t support connected products. Were actively working on enabling support for connected products in Agents.
Knowledge, in the context of Agents, is the information and resources that you provide to an Agent to help improve the accuracy and helpfulness of its responses. Knowledge can include links to Confluence spaces, specific pages, Jira projects, Google Drive workspaces, and other relevant resources.
It’s important to remember all Agents will have default knowledge, which is essentially everything the user who’s interacting with the Agent has access to at the time they’re using it.
By electing to provide an Agent with custom knowledge your Agent will only be able to reference the knowledge sources you provide (whether it’s a specific link, a full Jira project, or a collection of projects and spaces across your organization’s tools) along with it’s training material to ensure it’s ability to accurately read and write. Even with custom knowledge sources the Agent is always subject to the user’s permissions.
Providing knowledge to an Agent
When creating or editing an Agent, you can specify various sources of knowledge.
For each knowledge type, search and select the desired knowledge from the dropdown, or directly paste a link.
When using Confluence as a knowledge source, you can choose to either provide an entire space, or you can select “Content under” which includes the content on the page and on any of its child pages.
Plugins and Knowledge
Agents use plugins to retrieve and process information. They’re tied to knowledge because, when you provide custom knowledge to your Agent, we’ll customize the plugins your Agent uses to fit. When you create an Agent, you’re unable to configure the plugins your Agent can use.
Plug-ins allow Agents to access data from your other Atlassian products and connected third-party products in order to provide their full functionality. For example, while you may use the Issue Organizer in Jira, it will be able to leverage information based on user permissions from Confluence pages to create a new epic in Jira.
Name | Relevant knowledge | Description |
Content read | NA (always on) | Retrieve the contents from certain URLs (including Confluence, Jira, Atlas, Google, SharePoint, and Slack). This also includes the current browser URL. |
People plugin | NA (Always on) | Fetches the account id, email, name, location, and profile picture based on a user's name. Do not call this function with a job title or team. |
Search QA | Any | Finds answers from Confluence data sources. It returns answer and sources that were used to find the question. |
Activity Plugin | Any | Fetches the most recent activities of a user on Jira and Confluence. |
Next best task | Any | Finds the next best task for a user to work on. |
Page search | Confluence | Finds a given Confluence page or blog post based on certain search filters |
Jira JQL | Jira | Find all Jira issues for the user using a JQL query. |
Jira Software | Jira | Provides information about an active Jira Software project's boards and backlogs. Used when directly referencing a Jira project's boards and backlogs. |
During the creation process, if you select certain actions or knowledge sources for your Agent, we’ll customize the Agent’s plugins to suit its knowledge sources and actions. For example, if you create an Agent that can make Jira issues, or give it a Jira project as a knowledge source, we'll enable the JQL plugin for that Agent, so it can retrieve information from Jira efficiently. The reason we do this is to improve the performance of your Agent, if the Agent is attempting to use too many plugins to respond to a prompt, it can cause performance issues.
Was this helpful?
Still need help?
The Atlassian Community is here for you.