Skip to main content

Qase for Rovo

Ask Rovo in Jira Cloud about your Qase test data — coverage gaps, flaky tests, failed runs and release readiness.

Qase for Rovo brings your Qase test data into Rovo, the AI assistant in Jira Cloud. Once it is connected, anyone on your Jira site can ask the Qase Quality Supervisor agent where test coverage is thin, which tests are flaky, why a test run failed, or whether a release is ready to ship — without leaving Jira.

​

Qase stays the system of record. The agent only reads your Qase data; it never creates, changes or deletes anything in Qase, and it does not read your Jira data.

​

Qase for Rovo is a free app on the Atlassian Marketplace.

​

​

Before you start

You need all of the following:

​

What

Why

A Jira Cloud site with Rovo enabled

The agent runs inside Rovo

A Jira site administrator

To install the app, connect it to Qase and choose which projects Rovo can read

A Qase workspace on any plan other than Free

Connecting Rovo uses Qase integrations, which the Free plan does not include

A Qase user who can install integrations in that workspace

To approve the connection in Qase. Owners and Administrators can

​

The Jira administrator and the Qase user can be the same person or two different people.

​

One Jira site connects to one Qase workspace.

​

​

Installing and connecting Qase for Rovo

1. Install the app. In Jira, go to Apps → Explore more apps, search for Qase for Rovo, and install it. If you are not a Jira administrator, select Get it now to send a request to your administrator.

​

Jira's Explore more apps search with Qase for Rovo in the results

​

2. Open the Qase for Rovo settings page. Go to Jira Settings → MarketPlace Apps, and select Qase for Rovo in the left sidebar. Only Jira administrators can see this page.

​

The Qase for Rovo page in Jira admin settings with the Qase instance URL and Connect with Qase

​

3. Connect to Qase. In Qase instance URL, keep https://app.qase.io, then click Connect with Qase. Qase opens in a new browser tab.

​

4. Approve the connection in Qase. Make sure you are signed in to the Qase workspace you want to connect — the connection goes to the workspace that is active in that tab. Qase shows that the Rovo app is requesting access to your workspace, with your Jira site address. Click Authorize.

​

The Qase page saying the Rovo app is requesting access to your workspace, with the Authorize button

The approval link is valid for one hour. If it has expired, go back to Jira and click Connect with Qase again.

5. Return to Jira. After you approve, Qase stays on its own page. Switch back to the Jira tab. It updates on its own within a couple of minutes; if it still shows the connect form, reload the page. When the connection is complete, the page shows Connected to Qase.

​

The Qase for Rovo settings page showing Connected to Qase and the Projects Rovo can read list

​

6. Choose the projects Rovo can read. Under Projects Rovo can read, tick each Qase project you want the agent to answer about, then save. Changes apply from the next question anyone asks.

​

Ticking Qase projects under Projects Rovo can read

​

The Save button at the end of the project list, with the Saved confirmation

No projects are selected after you connect, so Rovo can read nothing until you tick at least one. Access is set for the whole Jira site: everyone on the site can ask the agent about the projects you tick, whether or not they can open those projects in Qase. Tick only projects whose test data everyone on your Jira site may see.

New Qase projects are not added automatically. Come back to this page and tick them when you want Rovo to read them.

​

​

Asking the Qase Quality Supervisor

In Rovo, open Agents, search for Qase, and select Qase Quality Supervisor. Search for it by name — it may not appear on the first page of the agent list.

​

Rovo's agent list searched for Qase, showing the Qase Quality Supervisor agent

​

Include your Qase project code in your question, for example DEMO. If you leave it out, the agent asks for it.

​

Qase Quality Supervisor answering how many test cases in a project have never been executed

​

Every user on your Jira site can also open the Qase for Rovo page in Jira to see whether the site is connected and which Qase projects the agent can read.

​

If your team builds its own agents in Rovo Studio, you can add the Qase tools to them too.

​

​

What you can ask

The agent runs four analyses.

​

Coverage gaps. Which cases have never been run, how much of the project is automated, manual or still to be automated, and which suites are empty or thin.

  • "Where are the coverage gaps in DEMO?"

  • "How many cases in DEMO are still manual?"

​

Flaky versus broken tests. A test that both passed and failed over the same period is flaky — fix the test. A test that only ever failed is a regression — fix the product. The agent keeps the two apart, because the fixes are opposite.

  • "Which tests are flaky in DEMO, and which are just broken?"

​

Why a run failed. The agent reads the results of one test run and groups the failures by their underlying cause, so forty failures can turn out to be three problems.

  • "Why did run 42 in DEMO fail?"

​

Release readiness. The agent gives a verdict on a release you name: GO, NO-GO or INSUFFICIENT EVIDENCE. Name the milestone, test plan or runs that make up the release — without a scope it will not answer GO. It reports untested work first, so a run where nothing was executed is never mistaken for a green one.

  • "Are we ready to ship milestone Release 2.4 in DEMO?"

​

​

What the agent cannot do

  • Create or change anything in Qase — no new test cases, defects or test runs, and no marking tests as flaky. It tells you what to do in Qase instead.

  • Read Jira, or link Jira issues to Qase test cases.

  • Answer questions about "my" cases or runs. The agent does not know who is asking, so name the person instead.

  • Show which requirements have no linked test cases.

  • Read shared steps, attachments or test case history.

​

​

Troubleshooting

The agent says the site is not connected to Qase. The connection was not completed or has been removed. A Jira administrator connects it again on the Qase for Rovo settings page.

​

The agent says a project is not shared with Rovo. The project exists but is not ticked. A Jira administrator ticks it under Projects Rovo can read.

​

The agent finds no data for a project you know has data. Check that the project is ticked under Projects Rovo can read. A search over a project that is not ticked returns no results rather than an error.

​

The agent cannot find a project or record. Check the project code and the number. The number is the one Qase shows after the project code — in DEMO-12, the project code is DEMO and the number is 12.

​

Approving the connection in Qase fails. Make sure your Qase workspace is on a plan other than Free, and that your Qase role allows installing integrations.

​

The agent asks you to try again. Qase did not answer in time. Wait a moment and ask again; if it keeps happening, contact support.

​

​

Disconnecting Qase for Rovo

To stop Rovo reading your Qase data, either untick every project under Projects Rovo can read, or uninstall the app from Jira Settings → Apps → Manage apps. Uninstalling removes the connection to Qase.

​

If you reinstall the app later, the agent is new to Rovo, so links to earlier Rovo conversations with it no longer work.

​

​

FAQ

Does Qase for Rovo cost anything?

​

The app is free on the Atlassian Marketplace. Your Qase workspace needs a plan other than Free.

​

Can Rovo change my test data?

​

No. The agent only reads Qase data and cannot create, edit or delete anything.

​

Does Qase read my Jira data?

​

No. The app does not request access to your Jira data.

​

Who can see the answers?

​

Everyone on your Jira site who uses Rovo can ask about the projects a Jira administrator has ticked. Choose those projects with that in mind.

​

Can the agent create test cases from a Jira issue?

​

Not today. The agent analyses existing test data only.

Did this answer your question?