---
title: "[Xray] Using Atlassian Rovo and Xray"
canonical: "https://docs.getxray.app/space/ProductKB/470974466/%5BXray%5D%20Using%20Atlassian%20Rovo%20and%20Xray"
format: markdown
---
> Macro (rw-ui-expands-macro)
> 
> > Macro (rw-expand)
> 
> > Macro (toc)

# What is Rovo?

[Atlassian Rovo](https://www.atlassian.com/software/rovo) is an AI-powered knowledge discovery and workflow assistant designed to help teams access, understand, and act on information across Atlassian tools and connected systems.

Rovo operates on three main dimensions:

- **Finding:** provides unified search across Atlassian tools (such as Jira and Confluence) and third-party systems, allowing users to retrieve relevant information without leaving their workspace.
- **Learning:** uses AI to surface insights, display knowledge cards, and enable conversational chat to explore organizational data in context.
- **Acting:** introduces AI agents and automation features capable of performing routine tasks, generating content, and integrating directly into existing workflows.

Rovo is included by default in all Atlassian products. Users can interact with it by:

- **Search:** through the App Store or built-in search bar, ideal for structured, syntax-based queries.
- **Chat:** via a dedicated Rovo chat page or directly within the current workspace. The chat mode offers greater contextual understanding and supports more natural language queries.

# How Rovo Works within Jira

Within Jira, Rovo functions as an advanced search engine. It retrieves information from standard Jira Issue fields - such as **Title**, **Description**, **Labels**, **Assignee**, and **Components** - and can also reference external data sources like Confluence or [Xray Documentation](https://docs.getxray.app/).

However, it’s important to note that **Rovo cannot access data stored within Xray Cloud’s storage**. As a result:

- Rovo may not interpret relationships between **Xray artifacts** and Jira Issue fields accurately.
- Data stored in **Xray’s Cloud Storage**, such as information displayed in the **Coverage Panel**, **Testing Board**, **Test Status**, or detailed Test Plan content, is not accessible to Rovo.

To achieve the best results, users should frame their queries precisely. For example, asking about “Xray Test Plans” instead of “tasks” helps Rovo return more relevant information.

# Using Rovo with Xray Information

Even with these limitations, Rovo can assist Xray users by simplifying information retrieval and documentation tasks.

## Example 1: Finding Test Cases Based on Keywords

Rovo can help locate Testing artifacts without manually writing JQL queries.

**Scenario:** a team member needs to find all existing manual Tests related to a feature.

**Interaction: u**se the chat or search feature and type a descriptive query, such as:

> “Find all manual Tests in the XSP2 project that include Payments.”

**Outcome: **Rovo returns a summary followed by a table listing relevant items (Tests, Test Executions, etc.) containing the keyword in their titles or descriptions (Figure 1).

> ✅ **Tip:** By default, Rovo searches the entire instance. To narrow the scope, include the project key in your query.

![Figure 1 - Rovo chat](media://1be339b3-03a3-45cf-b622-2738816f311b)

## Example 2: Reviewing Team Workload Distribution

Project Managers or Team Leads can use Rovo to check how Testing artifacts are distributed among team members.

**Scenario: **a manager wants to see how Test Plans are assigned across the team.

**Interaction:**

> “Show how many Test Plans are assigned to each team member.”  
> Or  
> “Show Test Plans per assignee and status.”

**Outcome: **Rovo lists the number of Test Plans assigned to each person, grouped by status if requested. This provides quick visibility into workload distribution and project progress (Figure 2).

> ✅ **Tip: **mention the project or sprint board name for more specific results.

![Figure 2 - Rovo chat](media://258c467d-9959-4c8f-badc-5f8f21579048)

## Example 3: Creating Documentation in Confluence

Rovo can help generate documentation by summarizing procedures from existing Xray resources.

**Scenario: ** a team needs a Confluence page detailing how to configure the CI/CD integration with Xray.

**Interaction:**

> “Create a Confluence page explaining the steps to configure CI/CD integration with Xray.”

**Outcome: **Rovo compiles information from official Xray documentation, including prerequisites, setup steps, and API examples. It can then format the information into a Confluence page for internal training or onboarding.

> ✅ **Tip: **specify how you want the content structured (e.g., bullet points, tables, or detailed steps).

# Next Steps for Rovo and Xray

At this stage, Rovo can only access Jira and other Atlassian data, not Xray’s internal Cloud data. The Xray team is working on enabling deeper integration between both platforms.

This upcoming development will allow Rovo Agents to read and act on Xray-specific data, providing intelligent insights and context-aware results directly within the Atlassian ecosystem.

Xray is currently evaluating the most valuable use cases for this integration to ensure that future Rovo Agents deliver meaningful benefits to users.

If you’d like to share suggestions or use cases for Rovo–Xray integration, please participate in our [feedback survey](#).