Apps › Developer Tools

Jira automation with Bizomate

Bugs and requests reach your team through email, support and the repository long before anyone files them in Jira. Bizomate creates the issue with your project's own fields, moves it through your workflow, comments and attaches files, and starts a workflow when an issue is created, updated or reaches a status. Every run leaves a record of what it changed.

Start free See the templates

◇ Publishing a workflow that uses it asks for a paid plan. Build and test on any plan.

At a glance

Label	Value
Plans	◇ Paid plans — on Free you can build and test; publishing needs a paid plan
Connect	Site address, email and API token
Starts runs	Every 5 minutes
Kind	Connected app · Developer Tools

What can start a workflow

New issue ◇
When an issue is created in a project — checked every 5 minutes

In a project, of one issue type or every type, and only issues an optional JQL filter also finds. Checked every 5 minutes.

Issue updated ◇
When an issue in a project changes — checked every 5 minutes

Any change to an issue in the project. Checked every 5 minutes.

Issue moved to a status ◇
When an issue moves to the status you choose — checked every 5 minutes

Choose the status — Done, In review. Checked every 5 minutes.

New comment ◇
When someone comments on an issue in a project — checked every 5 minutes

A comment on any issue in the project. Checked every 5 minutes.

What a workflow can do with it

Create an issue ◇
Opens an issue in a project, with the fields you fill in

Choose the project and the issue type, and the type's own fields appear, required ones first. A sprint goes in Other fields, as its id.

Update an issue ◇
Changes the fields you fill in on an issue

Transition an issue ◇
Moves an issue along its workflow — To Do to In Progress

Through the moves open to the issue from where it is, with a comment if you like.

Add a comment ◇
Comments on an issue

Assign an issue ◇
Gives an issue to someone, or unassigns it

Left empty, it unassigns the issue.

Find issues ◇
Issues a JQL search finds, or by project, status, assignee and date

With JQL, or by project, status, assignee and updated since; up to 1,000.

Get an issue ◇
An issue's fields, by its key

Add an attachment ◇
Attaches files from earlier steps to an issue

Files from earlier steps, each attached to the issue.

Link issues ◇
Links two issues — CON-142 blocks CON-120

How you connect it

Make an API token for your Atlassian account at id.atlassian.com › Security › API tokens. In Bizomate, type your site's name in Site address, before the fixed .atlassian.net — pasting the whole address works too — the email you sign in to Atlassian with in Email, and the token in API token. Steps act as you, with your Jira permissions, so they see the projects you see. Bizomate asks Jira who you are on that site before saving, and Test answers "Reached Sam Carter · {your site}.atlassian.net".

Jira Cloud only: Jira Data Center and Server, on your own servers, are not supported. One connection reaches one site. Atlassian API tokens expire; add the end date to the connection and the workspace's admins are reminded 30, 7 and 1 days before. Signing in with Atlassian, instead of a token, is not offered yet.

The token is encrypted before it is saved, used only when a step runs, a trigger checks or a test calls Jira, and never shown again — not to you, your colleagues or Bizomate support. It belongs to one workspace, the Code step cannot read it, and revoking the connection wipes it at once.

In the help centre: Connect Jira, Create, update or find Jira issues, Start a workflow from Jira issue events and Premium connections on the Free plan.

Questions about Jira

Which plan do I need?

Jira is a premium connection. On any plan, Free included, you can add it and build and test workflows that use it; publishing one of those workflows needs a paid plan.

Does it work with Jira Data Center or Server?

No. It connects to Jira Cloud sites, the ones at an address ending .atlassian.net. Jira on your own servers is not supported.

Do the triggers start a run straight away?

No. They check the project every 5 minutes, and each issue created, changed, moved to the status or commented on starts one run. Issues already there when you publish never start a run, and a JQL filter narrows what counts.

Can it fill in my custom fields?

Yes. Create an issue and Update an issue read the issue type's own fields from your site under Other fields, required ones first: a person takes an email or account id, a sprint its id, a date 2026-10-09.

Templates with Jira

OperationsFree

Jira issue done, told in Slack

When an issue moves to Done, the channel hears who closed it, with a link.

Jira → Slack BBy Bizomate