Connect Jira

A Jira connection lets workflows create, update, transition, assign, get, find and link issues, comment and attach files — and start a run when an issue is created, changed, moves to a status or gets a comment. It connects to one Jira Cloud site with your email address and an API token from your Atlassian account. Everything the steps do is done as you, with your Jira permissions.

Who can do this

• In Bizomate: workspace Admins and Editors. Viewers see the connection but cannot add or change it.
• In Jira: anyone can make an API token for their own Atlassian account. It reaches the projects that account can, with the same permissions.
• Plan: Jira is a premium connection, marked ◇. You can add it and test its steps and triggers on any plan; publishing a workflow that uses it needs Starter, Pro or Enterprise.

Steps

In Atlassian, make the token:

1. Sign in at id.atlassian.com, then go to Security, and under API tokens select Create and manage API tokens.
2. Select Create API token.
3. In the name box, type Bizomate, and choose when it expires. Note the date.
4. Select Create, then Copy. Atlassian shows the token only once.

In Bizomate, add the connection:

1. Select Connections in the bar at the top, then + Add connection.
2. Under Developer Tools, select Jira — marked ◇, and on the Free plan "Sign in · Paid plans". Until signing in with Atlassian is offered, the window opens on the fields below and reads "Stored credential".
3. In Connection name, type a name — for example Consulace Jira.
4. In Site address, type your site's name — consulace — before the fixed .atlassian.net. Your Jira Cloud site — asked first, because every request goes to it. Pasting the whole address works too.
5. In Email, type the email of the Atlassian account that made the token — rohan@consulace.com. The email you sign in to Atlassian with.
6. Paste the token in API token — Made at id.atlassian.com › Security › API tokens. Steps act as you, with your Jira permissions. Stored encrypted; never shown again.
7. Optional: in This sign-in expires on · optional, the date you chose in Atlassian — If the service gave the sign-in an end date. The workspace’s admins are reminded 30, 7 and 1 days before.
8. Leave Test the connection before saving ticked. Bizomate asks Jira who you are on that site before keeping it.
9. Select Save connection. The button reads Testing while Jira is asked.

The toast "Connection added" says what Jira answered — for example "“Consulace Jira” is ready. Reached Rohan Mehta · consulace.atlassian.net."

What happens next

• The connection appears under Developer Tools. Its panel shows Test and Revoke — and Replace token, once an end date is entered — never the token.
• Test answers with your display name and the site — Reached Rohan Mehta · consulace.atlassian.net.
• Jira steps and triggers list it under Connection. Their Project list shows the projects you can see on that site, each with its key — Consulace Ops · CON.

Good to know

• On the Free plan the window notes: "Jira is on paid plans. You can add it and test the steps that use it now; publishing a workflow that uses it asks for a paid plan."
• One connection, one site. For a second Jira site, add a second connection.
• Atlassian API tokens expire. When yours does, every Jira step fails. With the date in This sign-in expires on, the connection turns amber 30 days before and its panel offers Replace token: make a new token in Atlassian, select Replace token, fill in the fields again and select Replace token. The toast "Token replaced" says "Workflows that use “Consulace Jira” use the new token from their next run."
• Jira Cloud only. Jira Data Center and Server, on your own servers, are not supported.
• Signing in with Atlassian instead of a token is not offered yet. When it comes, it also brings Confluence.

If something goes wrong

Related

• Create, update or find Jira issues
• Start a workflow from Jira issue events
• Premium connections on the Free plan
• Setting an expiry date for a key or password
• Testing a connection