Jira Cloud

Smoketest works in Jira as its own app. Comments and status changes it makes show Smoketest as the author in the ticket and its history, not a teammate, and the connection keeps working when the person who set it up leaves your company.

Connect a siteCopy Anchor Link

You need an organization Owner or Admin in Smoketest and a Jira admin for the site. They can be the same person.

1. In Smoketest, open Project Settings → Integrations and choose Connect Jira. Smoketest shows an install link and a one-time code.
2. A Jira admin follows the install link and adds Smoketest for Jira to the site. This is needed once per site. Jira confirms the install and stays on that page, so return to Smoketest afterwards.
3. Enter your Jira site in the dialog, for example your-site.atlassian.net, and choose Open in Jira. This opens the Smoketest page on that site. You can also reach it in Jira from Settings → Marketplace apps → Smoketest.
4. On that page, the admin enters the code. The code works once and expires after 15 minutes; choose New code in Smoketest if you need another.
5. Back in Smoketest, choose Done. The site appears under Jira with a healthy status.

To connect the same Jira site to another Smoketest workspace, repeat steps 1, 3, 4, and 5 with a new code.

Smoketest can see and change the issues the app is allowed to. Jira gives installed apps access to your spaces by default; if a Jira admin has restricted app access to a space, Smoketest cannot read or update tickets there.

If you connected Jira before the appCopy Anchor Link

Earlier Jira connections signed in as one of your teammates. Those connections were disconnected when Smoketest moved to the app, and their Test Sources stopped listening. The dashboard shows a Reconnect Jira notice until this is done:

1. Follow Connect a site above for the same Jira site. Your existing Test Sources and their history are kept.
2. Open each Test Source and select Retry validation. A successful retry scans the tickets currently in QA.

Create a Test SourceCopy Anchor Link

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.

Connection healthCopy Anchor Link

The app checks in with Smoketest whenever a ticket changes and at least once an hour. If it stops, for example because it was uninstalled from Jira, the Connection shows as degraded within a few hours rather than silently dropping work. Reinstalling the app restores it.

Disconnecting in Smoketest stops Smoketest from listening and deletes its stored access. It does not remove the app from Jira; a Jira admin can uninstall it from Manage apps.

Sprint accessCopy Anchor Link

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, a Jira admin needs to approve the latest version of the Smoketest app in Manage apps. 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 for the complete setup and safety model.