Integration
Sitejar Jira integration
The Sitejar Jira integration turns website scan findings into Jira issues in the project you choose, one issue per finding and never a duplicate: sending a finding again adds a comment to the issue it already has. Each issue carries the rule, the severity, the pages it was found on and the suggested fix, its status shows on the finding in Sitejar, and only a scan that no longer detects the problem marks it fixed.
On Agency and above.
What the Sitejar Jira integration does
Sitejar scans a site in a real browser for accessibility (WCAG 2.1 AA), security, privacy, deceptive design, technical quality and SEO, and tracks each problem from scan to scan. This integration carries those findings to where your team plans its work, written so whoever picks one up can start without opening Sitejar.
- One issue per finding. Sending it again adds a comment instead of a second issue.
- The issue's status, read back from Jira, shows on the finding.
- A default project for the workspace, and its own project for any site that needs one.
- Whole reports in one send: a Jira issue for the report whose description lists every finding's issue key.
Who the Jira integration is for
Teams that already plan their work in Jira and want website problems in the same queue as everything else. If your team runs sprints in Jira Software or tracks work in a Jira project, findings arrive as ordinary Jira issues that fit your boards, filters and dashboards. It suits agencies handing client fixes to a delivery team, and developers who would rather get an issue with a selector and a fix than a PDF.
Send accessibility issues to Jira
Accessibility is the most common reason teams send findings, but any finding can go: a missing security header, a tracker that loads before consent, a broken link.
Turn a new scan into a backlog
Send a whole report and Sitejar creates a Jira issue for the report whose description lists every finding's issue key, most severe first, filtered by severity and with or without Needs review findings. Send the same report again later and only the findings not yet sent are added.
Send just what fits this sprint
Select a handful of findings on the Findings page, or open one finding, and send only those. The rest stay in Sitejar until you are ready.
Keep each client's work in its own project
Give a site its own destination, and its findings go to that project while everything else goes to the default. On Agency Plus, a client can have a destination too: a site's own wins over its client's, and its client's over the default.
How to connect Jira to Sitejar
- Sign in to Sitejar as an Owner or Admin of the workspace and open Settings, then Integrations.
- On the Jira card, choose "Connect Jira". If your plan does not include Jira, the card says "Not on your plan" instead.
- Atlassian opens its consent screen. Approve access. Atlassian then tells Sitejar which Jira Cloud sites your account can reach.
- If it reaches more than one site, a "Jira site" choice appears on the Jira card. Pick the site to use. Changing it later clears the saved destinations, because projects belong to a site.
- Back in Sitejar, the card says "Connected to" followed by the Jira site's name. Under "Tasks go to", choose the project new issues go to by default.
- Optional: under "Give a site its own destination", pick a site and a project, then choose "Add".
A workspace has one Jira connection, and connecting again replaces it.
How to send findings to Jira
Anyone whose role can manage findings (Owner, Admin or Editor) can send them, three ways:
- On the Findings page, select findings and choose "Send to Jira" in the bulk actions bar, or choose "Create tasks" and pick Jira under "Send to". Up to 50 at a time.
- On one finding, use "Send to Jira" in its Task section, which then links to the issue.
- On a report, choose "Send report to Jira" in the Next steps panel ("Send report to a task tool" when more than one is connected), pick the severities, and send. Up to 100 issues at a time.
What Sitejar sends to Jira, and what it stores
What a Jira issue from Sitejar contains
The title names the dimension, the severity, the rule, the page count and the site: [Accessibility][High] Form field missing a label (12 pages) | example.com.
The body carries the confidence label (Confirmed, Likely or Needs review), how many instances on how many pages and the scan date, a CSS selector, the WCAG success criterion where one applies, the first 20 page urls, the suggested fix and its code when one exists (or "No AI fix yet"), and a link back to the finding. It never contains evidence captured from your pages or their content. Jira does not accept Markdown, so Sitejar converts the body to Atlassian Document Format: paragraphs, bullet lists and code blocks. Bold markers stay in the text as asterisks rather than turning bold.
Permissions Sitejar asks for in Jira
Sitejar connects through Atlassian's OAuth 2.0 (3LO) and asks for three scopes: read:jira-work and write:jira-work, to list projects, create issues, comment and move an issue through your workflow, and offline_access, so it can renew the access token without asking you to sign in again.
Jira access tokens last about an hour. Sitejar renews them with the refresh token and saves the new pair after each call.
What Sitejar stores about your Jira connection
Sitejar stores the Atlassian access token and refresh token, the Jira site's name for the card, the chosen site's cloud id and url, the issue type, and the name and url of each site the grant reaches, and the last error Jira returned. Credentials are encrypted with AES-256-GCM and never sent to your browser. For each issue it created, Sitejar keeps the issue's id, url, last status and when it last checked. Sitejar keeps no personal data from Jira. The label on the card is the site's name, and Sitejar never reads users, comments or issues it did not create.
Disconnecting empties the stored credentials at once, and the issues already created stay in Jira. To revoke the grant on the Jira side too, remove Sitejar in Jira's own settings.
What happens in Jira after the next scan
The sync runs one way: a scan can move an issue, but closing an issue never marks a finding fixed. Only a scan that no longer detects the problem does, so a issue closed by mistake or before the deploy cannot flatter your scores.
When a linked issue is shown in Sitejar, Sitejar reads its status from Jira, at most once every 10 minutes. The finding shows the issue's status by name, such as In Progress, and treats it as closed when the status is in Jira's Done category. If Jira answers with an error, the last known status stays. Issues deleted in Jira show as Removed, and one closed while the latest scan still finds the problem shows "Reopened: closed in the tool, still detected in the latest scan."
On Business and above, each completed scan adds one comment to every linked issue: "Still detected in the Sitejar scan of 3 November 2026." or "Not detected in the Sitejar scan of 3 November 2026. A scan, not this task, confirms a fix."
On Agency Plus, you can turn on "Move tasks after each scan" on the Jira card. Issues whose finding is not detected then move to a status in the Done category, using the first such transition your workflow offers, and those whose finding comes back move to a status in the To Do category, the same way. It is off until you turn it on.
Which plans include the Jira integration, and its limits
Jira is on Agency and above. Whole-report sends and after-scan comments are on Business and above, and automatic moves and per-client destinations are on Agency Plus. To see everything each plan includes, compare plans on the pricing page.
- One Jira connection per workspace.
- Up to 50 findings per send from the findings list, and up to 100 issues per whole-report send. Send the report again for the rest.
- The first 100 projects on the chosen site are offered as destinations.
- Jira Cloud only. Jira Data Center and Server are not supported.
- Issues are created with the Task issue type, so the project needs one.
- The summary is cut at 250 characters, under Jira's own limit.
- Dedupe belongs to the connection: findings sent through a connection you have since replaced go out as new issues.
Troubleshooting the Jira integration
"That connection link expired or was already used"
The link Jira sends you back with works once, within 10 minutes of choosing Connect. Choose "Connect Jira" again and finish without a long pause.
"Choose where Jira tasks go for this site first"
No destination applies to that site yet. Choose a default under "Tasks go to", or give the site its own.
The card shows "Last attempt" with an error from Jira
That is what Jira answered on the last call. "Jira answered 401" or "403" usually means the access was revoked or the connected account lost access to that project: connect again, or choose another project. "Jira answered 404" usually means it was deleted.
Sending fails with "Jira answered 400"
The most common cause is a project with no Task issue type, which is the type Sitejar creates. Add Task to the project's issue types in Jira, or send to another project.
The connection fails because "Jira granted no site"
The Atlassian account that approved access has no Jira Cloud site it can use. Sign in to Atlassian with an account that belongs to your Jira site, then choose "Connect Jira" again.
Moving issues fails with "The Jira workflow has no transition to a done status"
Sitejar moves an issue only through transitions your workflow already has. If an issue's current status has no transition to a Done-category status, add one in Jira, or turn "Move tasks after each scan" off.
Jira integration FAQ
Does sending a finding to Jira twice create two issues?
No. Sitejar links each finding to the issue it created. Sending the same finding again through the same connection adds a dated comment with its current details to that issue.
Does closing the Jira issue mark the finding fixed in Sitejar?
No. Sitejar shows the issue's status, but a finding counts as fixed only when a scan no longer detects the problem. If the issue is closed while the latest scan still finds it, the finding says it was reopened.
What does Sitejar store from Jira?
The credentials for the connection, encrypted with AES-256-GCM, the Jira site's name, and for each issue it created, its id, url and last known status. Disconnecting deletes the credentials at once.
Which plan do I need for the Jira integration?
Jira is on Agency and above. Whole-report sends and after-scan comments are on Business and above, and moving issues automatically after a scan is on Agency Plus.
Does the Sitejar Jira integration work with Jira Data Center or Server?
No. It works with Jira Cloud only, through Atlassian's cloud API. For a self-hosted Jira, the CSV for a task tool export in a report's Next steps panel produces a file shaped for Jira's CSV import.
Can I use Jira with more than one Atlassian site?
One Jira connection uses one site at a time. When your Atlassian grant reaches several sites, choose which one on the Jira card. Changing the site clears the saved projects, because each project belongs to one site.
Related integrations
Last updated . Jira and the Jira logo are trademarks of Atlassian. Sitejar is not affiliated with or endorsed by Atlassian.