Developer tools
Give your agents access to Jira.
Agents file issues from alerts and bug reports, search with JQL, move work through your workflow, plan sprints, and answer service desk requests. Jira events can start an agent when an issue is created or changes status, someone comments, a sprint starts, or a version is released.
5,000 free credits to start.
Agent reach
Jira Cloud platform REST API v3, Jira Software REST API, Jira Service Management REST API, Assets REST API, Forms REST API, and Jira Service Management operations and incident REST APIs
The full surface, searched at run time.
Connect with
- API key
- Your own OAuth app
Connect with an Atlassian API token and your site URL, or with your own Atlassian OAuth app with every scope in the docs turned on. Helios registers the webhooks for triggers. The API token's account needs the Administer Jira global permission for that, and an OAuth app receives issue, comment, issue property, sprint, and version events only.
Event triggers
Yes · 5 events
Plus manual, schedule, and signed webhook.
What the agent can do
What agents do with Jira
Helios searches the Jira Cloud platform REST API v3, Jira Software REST API, Jira Service Management REST API, Assets REST API, Forms REST API, and Jira Service Management operations and incident REST APIs at run time. The agent finds the endpoint the task needs and calls it.
- Use the Jira platform, Jira Software, Jira Service Management, Assets, Forms, and Jira Service Management operations and incident APIs, subject to the connection's permissions.
- Create issues with a project, issue type, labels, priority, and assignee.
- Run JQL searches and summarize a sprint, a project, or a saved filter.
- Transition issues through your workflow, assign them, log work, and attach files.
- Read boards and backlogs, move issues into sprints, and start or close a sprint.
- Answer service desk requests, add participants, and handle approvals.
- Start a run on issue, comment, worklog, sprint, board, version, project, and other Jira events.
Examples
Tasks you can hand to a Jira agent
Triage every new bug
The agent reads the report, looks for duplicates with JQL, checks recent changes, then sets labels, priority, and an assignee.
On each new Bug in the PAY project: find duplicates, set priority, and assign an owner.
- jira·read the issue and its fields
- jira·search open bugs with JQL for duplicates
- github·find recent commits in the affected code
- jira·set labels, priority, and assignee
PAY-1182 triaged
- Labeled `checkout` · priority High
- Linked to PAY-1170, which reports the same error
- Assigned to the author of the last change to the refund service
File an issue when CI fails
When a GitHub Actions run fails on main, the agent opens a Jira issue with the failing job and its error, unless one is already open.
When CI fails on main, open a Jira issue in OPS with the failing job, unless one is already open.
- github·read the failed job and its log
- jira·search OPS with JQL for an open issue on this job
- jira·create a Bug with the error and a link to the run
- slack·post the issue link to #oncall
OPS-311 opened
- Bug · priority High
- `checkout.spec.ts` fails on main since run 91422
- Posted to #oncall
Brief the assignee when work starts
When an issue moves to In Progress, the agent gathers the code, docs, and related issues the assignee needs and posts them as a comment.
When an issue moves to In Progress, comment with the related code, issues, and docs.
- jira·read the issue and its links
- github·search the code it mentions
- notion·find the design doc
- jira·comment with a starting brief
Brief posted on PAY-1190
- Two files that handle refund retries
- The design doc section on idempotency
- PAY-1043, closed with the same root cause
Summarize the sprint
A scheduled agent reads the active sprint with JQL and tells the team what shipped, what slipped, and what is blocked.
Every Friday, summarize the active sprint and post it to Slack.
- jira·search issues in the open sprint with JQL
- code·group by status and assignee
- slack·post the summary to #payments
Sprint 37 summary
- 21 of 27 issues done
- 4 carried over to the next sprint
- 2 blocked on the ledger migration
Event triggers
Start a run on Jira events
Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too.
| Event | What it means |
|---|---|
issue.created | An issue was created in a project. |
issue.updated | An issue changes. Filter on the status it moved to, such as In Progress or Done. |
comment.created | Someone comments on an issue, so an agent can answer or pick up the follow-up. |
sprint.started | A sprint starts on a board, so an agent can post the plan or check the scope. |
version.released | A version is released, so an agent can write the release notes from its issues. |
Works with
Jira works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
FAQ
Questions, answered
Put an agent on Jira.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.