Jira

Issue logging, bug tracking, and sprint management.

What it does

Creates and updates Jira issues. For clients running delivery work through Jira, an agent can open, comment on and move tickets like any other team member.

What you need

An account with Jira that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Jira's own sign-in and consent screen, and what comes back is an authorisation rather than a password. RAiN never sees your password, and the authorisation is held by our integration provider on our instructions — see the Integrations & Connected Accounts notice for what that means.

Connecting it

Connections belong to one project. A system built for one client never acts on another client's account, and a package handed to a business runs on theirs — so the same integration is connected again, separately, for each project that needs it.

Open the project and stay on the Visual Editor tab.
Open the Tools & Integrations rail on the right.
Find Jira and press Connect.
Authorise in the window that opens, then come back. The rail will show it as connected.

The consent link is good for about twenty minutes. If you leave it and come back tomorrow, press Connect again rather than reusing the old tab.

To stop it, press Disconnect. That ends this project's access immediately. You can also revoke it from Jira's own security settings, which works even if you never open RAiN again.

What an agent can do with it

59 actions are available once connected, 3 of which delete things and are marked where they appear. They appear in the tool list for this project only — a project that has not connected Jira is never offered them.

Action	What it does
`jira_add_attachment`	Add Attachment
`jira_add_comment`	Add Comment
`jira_add_user_to_group`	Add User to Group
`jira_add_users_to_project_role`	Add Users to Project Role
`jira_add_watcher_to_issue`	Add Watcher to Issue
`jira_add_worklog`	Add Worklog
`jira_assign_issue`	Assign Issue
`jira_bulk_create_issue`	Bulk Create Issues
`jira_fetch_bulk_issues`	Bulk Fetch Issues
`jira_create_board`	Create Board
`jira_create_group`	Create Group
`jira_create_issue`	Create Issue
`jira_create_project`	Create Project
`jira_create_sprint`	Create Sprint
…	and 45 more, all listed in the rail

Tick the ones an agent may use, or choose one in an Action step to run it exactly as written with no model involved.

A worked example

A support agent turns a recurring customer complaint into a Jira bug with the reproduction steps already written, rather than a human retyping the thread.

When it goes wrong

Required fields refuse the create. Jira projects often mandate fields the API call does not send. Check the project's screen configuration.