Integrations · Playbook

What an AI coworker
can do in Jira.

The Jira integration exposes 14 actions — 8 read,6 write — that any agent, team or AI employee can use once Jira is connected at the organization level. Every write can be gated behindhuman approval, and every call lands in theaudit trail.

Read actions (8)

Safe to run freely — they observe, fetch and search.

ActionFunctionKey params
Get epic issuesjira_get_epic_issuesepic_key
Get issuejira_get_issueissue_key
Get link typesjira_get_link_types
Get project issuesjira_get_project_issuesproject_key
Get sprint issuesjira_get_sprint_issuessprint_id
Get sprints from boardjira_get_sprints_from_board
Searchjira_searchjql
Search fieldsjira_search_fields

Write actions (6)

They change things. Gate the sensitive ones with approval policies; approvals are single-use.

ActionFunctionKey params
Add commentjira_add_commentissue_key, comment
Create issuejira_create_issueproject_key, summary, issue_type
Create sprintjira_create_sprintboard_id, sprint_name, start_date, end_date
Delete issuejira_delete_issueissue_key
Update issuejira_update_issueissue_key, fields
Update sprintjira_update_sprintsprint_id

Put Jira in an AI coworker's hands.

Browse templates and solution packs that work with Jira, or start from the problem you're trying to fix.

Browse templates