Jira and Linear tickets

Open Settings in Strays

What you get

On any finding, Create ticket makes an issue in your Jira Cloud project or Linear team. The ticket holds what was found, where, its owner, its cost or severity, a link back to Strays, and the ready-to-run fix: the safety checks, the commands and the Terraform change. It is made once: afterwards the finding shows a link to the ticket instead of the button. Strays changes nothing in your AWS account; whoever picks up the ticket runs the steps.

Anyone who can keep or snooze findings (members and admins) can create tickets. Viewers can follow the links. Jira and Linear tickets are on the Business plan, and during the trial. If you move to Team, tickets already made stay linked on their findings but no new ones are made, automatic ones included.

Connect Jira Cloud (an admin, once)

1. At id.atlassian.com, under Security, make an API token. It acts as your account, so use an account (or a bot account) that can create issues in one project and nothing more.
2. In Settings, enter your Jira address (https://yourcompany.atlassian.net), the account's email, the token, the project key (like OPS) and the issue type (Task unless you want Bug or another type that exists in that project).
3. Strays checks the token and project before saving. Only atlassian.net addresses are accepted.

Connect Linear (an admin, once)

1. In Linear, under Settings, Security and access, make a personal API key.
2. In Settings, enter the key and your team's key (the letters before the number in its issue IDs, like ENG).

If something is missing or not in the right form, nothing is saved and Settings says what to fix just above that form, with the field marked and the cursor in it. What you typed is kept, except the token or key, which you enter again.

One tracker is connected at a time; connecting the other replaces it. The credentials are stored encrypted and are never shown again. To stop, choose Disconnect, and delete the token or key in Atlassian or Linear.

Automatic tickets for new high risks

Turn on Make a ticket automatically for each new high-severity risk and Strays makes a ticket for each high risk first seen after you switched it on, when the hourly check or a scan finds it (up to 10 at a time). Risks already open when you switch it on, and anything you have kept or snoozed, are left alone: use Create ticket on those.

If it doesn't work

• "The tracker refused those credentials": the token was mistyped, was revoked, or the account can't see the project. Make a new one.
• "Can't find that project or team": check the key's spelling.
• "Didn't accept that": for Jira, the issue type probably doesn't exist in the project, or a required field is set that Strays doesn't fill in. Try Task, or make the extra fields optional.
• If a ticket was deleted in the tracker, the finding still shows the old link. Strays doesn't check.