---
title: Jira Cloud
description: Connect a Jira Cloud site and listen to an exact QA workflow status.
---

# Jira Cloud

An organization Owner or Admin authorizes one Jira Cloud site from **Project Settings → Integrations**. Smoketest can only see and change issues allowed by the connected Jira user's permissions, and its comments and transitions appear as that user.

When creating a Test Source, choose the Jira **Board**, optionally narrow it to a **Space**, and select the QA/testing column. **All spaces** includes every space on the selected board. Smoketest uses Jira's space terminology (formerly project); Linear connections use **Team** and **Project**. Because one board column can contain multiple workflow statuses, Smoketest asks for the exact QA status when necessary. Then optionally choose **Passed** and **Rejected** destinations that Jira can reach directly from QA. Choose **Don’t move** for either outcome to leave its ticket status unchanged. Leave both unset to run Tests and post result comments without moving tickets.

Setup checks board access, selected statuses, execution settings, and source ownership. If no ticket is currently in the selected QA status, you can save the Test Source; it shows **Waiting for first QA ticket**. Smoketest checks comment permissions and any configured direct workflow transitions when the first ticket arrives, before starting a Test. An already validated source can have an empty QA queue.

If validation fails, open the Test Source to see the specific reason, correct the Jira permission or workflow, and select **Retry validation**. A successful retry scans the tickets currently in QA. Smoketest does not walk through intermediate statuses or supply transition-screen fields.

Jira dynamic webhooks expire and are refreshed automatically. Permission loss, webhook failure, or expiration appears in Connection/Test Source health rather than silently dropping work.

## Sprint access

Smoketest checks for sprints on every connected Jira board, including Kanban and team-managed boards. Active sprints returned by Jira appear in Overview and the Board's sprint filter.

If a source shows **Sprints unavailable** with a missing-permissions message, open **Project Settings → Integrations** and **Reauthorize** Jira to approve sprint access. Existing connections need this once after sprint permissions are added; restarting Smoketest does not expand an existing grant. The next sync checks for sprints again.

Some boards have sprints in Jira's interface that Jira's API cannot expose. In that case, Smoketest shows them as unavailable and continues to display tickets from the configured board statuses.

See the [Quickstart](/get-started) for the complete setup and safety model.