Cookie settings

Send bugs to Jira

Connect Atlassian Jira once. After that, one click sends a bug, and the status, the person, and the wording stay the same in both places.

Plans. Plus, Business, and Pro. See Plus.

Do you use Jira (Atlassian)? Manage your bugs in both SiteScan and Jira with one-click synchronisation.

You need a Jira Cloud site and a project your team already uses. The person who connects signs in to that Jira site and approves SiteScan. Use a Jira account that can create issues in the project.

Connect Jira

  1. Open Settings → Extensions.
  2. Press Connect Jira.
  3. Sign in to Jira and allow SiteScan to create and update issues on that site.
  4. Choose the Jira project.
  5. Match every SiteScan column to a Jira status. The columns are Backlog, Up next, In progress, Testing, Done, and Archive. Choose statuses your Jira workflow can move between. When Jira has no path between two statuses, that move stays in SiteScan and the Jira story stays where it is.
  6. Under Match people, choose each teammate's Jira user. Do this once. Leave No Jira user for anyone who does not have a Jira account yet. You can match them later.
  7. Press Save Jira match.

Done looks like this: the page says the match is saved, and it names the Jira site and the project.

Send a bug

Create the bug in SiteScan first. That can be a Scan Bug or a My Bug.

  1. Open the bug.
  2. Press Send to Jira. It sits between Page view and Copy as Markdown.
  3. Wait until the button becomes a link with the Jira key, such as Jira SCRUM-8. Press that link to open the story.

Press Send to Jira again and the same story opens. SiteScan keeps one story for that bug.

The story lands in the Jira backlog. Drag it into a sprint in Jira when the team is ready to work on it. SiteScan sets the status to the Jira status you matched to that bug's column.

A picture or video you added on the SiteScan ticket is added to the Jira story. On a Scan Bug with no file of your own, SiteScan adds the screenshot from the scan when it has one.

SiteScan files the issue as a Bug when the project has that type. When the project has no Bug type, it files a Story.

What stays in step

After the bug is in Jira, these stay the same on both sides.

  • Status. Move the bug in SiteScan and the Jira story moves. Move the story in Jira and the SiteScan bug moves. The Jira workflow has to allow that move.
  • Assignee. Change the person in either place and the other place updates. When the SiteScan person has no matched Jira user, SiteScan keeps the assignment, the Jira story stays unassigned, and the ticket says why. When Jira assigns someone who is not in the match list, the SiteScan ticket names them. Match that person in Settings and save again.
  • Wording on a My Bug. The title, description, HTML code, and recommendation stay the same. Edit them in SiteScan or in the Jira story. The other copy updates.
  • Wording on a Scan Bug. SiteScan writes this from the check. You leave that text as it is in SiteScan. When someone edits the Jira story, the Scan Bug ticket shows that wording. A later scan leaves the Jira story as your team last edited it.
  • A new scan. When a new scan no longer finds a Scan Bug, it stays Done in SiteScan and in Jira. When the scan still finds it, both go back to Up next. A My Bug that a later scan can check moves to Testing in both places. It moves to Done when someone marks it Done.

Messages stay in SiteScan. A review with AccessUX stays on the bug in SiteScan.

About once a month, open Settings → Extensions and press Save Jira match again. Do the same any time a change you made in Jira does not show on the bug. Saving again keeps the same connection. Stories already sent stay as they are.

Disconnect

On the same settings page, press Disconnect Jira when this company should stop sending bugs. Stories already in Jira stay there. Sending starts again after you connect and save the match.