Docs · Connect your tools
Connect Jira Cloud
StackWeaver reads, and never changes, the issues of one Jira project that you have labelled with a control id, once a day. This guide says what is read, what access it needs, how to connect, and how to remove it.
Last reviewed: 6 November 2026 · Describes what is live in production on that date. A result is evidence of what the provider returned at a time, nothing more.
1. What it collects
Once a day StackWeaver lists the issues of one Jira project that carry a control id such as SWC-14. For each it keeps the issue key, status, priority, dates, whether someone is assigned, and a SHA-256 fingerprint of the title (platform) — never the title, description, comments or people's names themselves.
| Check (as shown in the portal) | What it looks at |
|---|---|
| Issues linked to controls | Which controls have at least one issue labelled with their control id |
| Open issues within their deadline | Whether open, linked issues are past their due date |
| Open issues have an owner | Whether open, linked issues have someone assigned |
2. What it does not do
- It does not store issue titles, descriptions, comments or people's names — only a SHA-256 fingerprint of the title, so a later change can be detected without the title being kept.
- It cannot change, comment on, or transition any issue.
- It does not say a control is met. A result is what Jira returned at a certain time.
3. The access it needs
Read-only, project-scoped access (Atlassian): Browse Projects on the one project you choose. The person approving sees a plain read-only request from StackWeaver's app; create no write, admin or cross-project permission for it.
Who can connect. In StackWeaver, a workspace owner or admin starts the connection. On Atlassian's side, you choose your Jira site and approve on Atlassian's own page; Atlassian does not tell StackWeaver what role the approving person holds in that site.
4. Connect steps
- In StackWeaver, open Evidence, the Jira Cloud section, and press Connect Jira Cloud.
- Choose your Jira site and approve the read-only access Atlassian's page asks for.
- Choose the project you want StackWeaver to read, and label the issues you want tracked with their control id (for example SWC-14) in the issue's title or a custom field, as your workspace settings describe.
- StackWeaver tests the connection and shows the result.
5. Reading the results
| Label | What it means |
|---|---|
| Pass | The provider returned data that meets the threshold at that time |
| Fail | The provider returned data that does not meet the threshold |
| Not enabled | There was nothing to check, or the feature needs a plan StackWeaver could not confirm |
| Could not check | StackWeaver could not read the data, or the check needs a higher plan than the account has |
6. Disconnect and revoke
- In StackWeaver, press Disconnect on the Jira Cloud section. StackWeaver deletes the stored approval.
- Atlassian has no way for StackWeaver to remove the approval itself. To fully remove access, revoke it yourself in your Atlassian account settings, Connected apps.
What remains. Past evidence stays in your workspace as the audit trail. Disconnecting does not delete it.
7. Troubleshooting
| Message | What to do |
|---|---|
| The approval was declined, so nothing was connected | Press Connect again and approve the access |
| This Jira site is already connected to another StackWeaver workspace | Ask StackWeaver support if this is your site |
| Issues linked to controls: none found | Check your issues carry the exact control id StackWeaver is looking for |
Still stuck? Use the contact page.
Sources and method
Statements about GitHub and Okta link to their own documentation. Statements about StackWeaver link to the page that says them, or are recorded in a claims ledger with the file in StackWeaver's repository that they come from. See oureditorial policy. Spotted an error? Use the contact page.