Docs
Connect Jira
Authorize WitnessQA on your Jira Cloud site and pick the projects to watch. When an issue is created or moved to Done, the agent checks its acceptance criteria in your app and reports the result with a screenshot of every step.
Before you start
- A WitnessQA project with at least one environment. See Getting started.
- Jira Cloud. Jira Data Center and Server are not supported yet.
- A Jira user who can browse the projects you want to connect. Results are posted under that user's name.
What WitnessQA can access
Jira shows these permissions on its consent screen. WitnessQA does not ask for admin access.
| Scope | Why |
|---|---|
read:jira-work | Reads issues, their description and fields. |
read:jira-user | Shows who created or closed the issue in the result. |
offline_access | Keeps the connection working without signing in again. |
write:jira-work (optional) | Posts the result as a comment. Jira has no comment-only scope, so this also allows editing issues. WitnessQA only adds comments. Skip it to keep results in the dashboard only. |
Connect in six steps
-
Open Integrations and click Connect Jira
In your project, open Integrations. Choose whether WitnessQA may post results as comments, then click Connect next to Jira Cloud.
Choose comments or read only, then click Connect. -
Pick your Jira site and accept
Atlassian asks you to sign in, then shows the consent screen. Choose the site, for example
acme.atlassian.net, check the permissions and click Accept.The Atlassian consent screen. Pick the site and accept. -
Choose the projects
Back in WitnessQA, select the Jira projects to watch. Issues in other projects are ignored.
Select only the projects you want verified. -
Choose where the criteria live and when runs start
Many teams keep acceptance criteria in a custom field. Pick that field, or keep Description. Then pick the triggers: issue created, and issue moved to a status in the Done category.
Pick the criteria field and the triggers. -
Map each project to an environment
Pick the URL to test for each Jira project. Staging is selected by default.
Each project runs against one environment. -
Read the result
When an issue is moved to Done, the run starts. The result is posted as a comment on the issue, if you allowed it, and always appears in the dashboard.
The result comment on the Jira issue. One criterion failed, with a link to the evidence.
Troubleshooting
- No run started. Check that the project is selected and mapped to an environment, and that the new status is in the Done category.
- No criteria found. Check the criteria field. If it is empty, the agent writes criteria from the description and marks them as suggested.
- No comment on the issue. The connection is read only, or the Jira user cannot comment in that project. The result is still in the dashboard.
Disconnect
Click Disconnect on the Jira integration in WitnessQA. To revoke access from the Atlassian side, open your Atlassian account settings, go to Connected apps and remove WitnessQA.
Failed on staging · 2/3 criteria
14 steps · console and network logs for step 7 in WitnessQA