Jira Integration

The Jira integration lets agents create, update, search, and manage issues in your Jira projects. Use it to log bugs from support calls, track feature requests, manage sprint work, or give teams real-time issue visibility through conversations.

Authentication

Jira uses API token authentication.

Field	Description
Subdomain	Your Jira subdomain — for yourcompany.atlassian.net, enter yourcompany
Email	Your Atlassian account email address
API Token	Generated from your Atlassian account settings

To generate an API token: id.atlassian.com/manage-profile/security/api-tokens → Create API token.

Installing

1. Go to your project → Integrations → Browse
2. Find Jira and click Install
3. Enter your Subdomain, Email, and API Token
4. Select the actions you want to enable
5. Click Install

Actions

create_issue — Create Issue

Creates a new issue in a Jira project.

Tool reference: {{tool:jira_create_issue}}

Parameter	Required	Description
project_key	Yes	Jira project key (e.g. ENG, SUPPORT)
summary	Yes	One-line issue title
description	No	Detailed description
issue_type	No	Bug, Story, Task, Epic (default: Task)
priority	No	Highest, High, Medium, Low, Lowest
assignee_id	No	Jira user account ID to assign the issue to

Returns: issue_key, issue_id, url

---

get_issue — Get Issue

Retrieves an issue by its key.

Tool reference: {{tool:jira_get_issue}}

Parameter	Required	Description
issue_key	Yes	Jira issue key (e.g. ENG-123)

Returns: issue_key, summary, status, priority, assignee, description, created, updated

---

update_issue — Update Issue

Updates an existing issue.

Tool reference: {{tool:jira_update_issue}}

Parameter	Required	Description
issue_key	Yes	Issue key to update
summary	No	New title
description	No	New description
priority	No	New priority
assignee_id	No	New assignee account ID

---

add_comment — Add Comment

Adds a comment to an issue.

Tool reference: {{tool:jira_add_comment}}

Parameter	Required	Description
issue_key	Yes	Issue to comment on
comment	Yes	Comment text

Returns: comment_id, created

---

transition_issue — Transition Issue

Moves an issue to a different status.

Tool reference: {{tool:jira_transition_issue}}

Parameter	Required	Description
issue_key	Yes	Issue to transition
transition_id	Yes	ID of the target transition — get these with get_issue or the Jira API

Common transition IDs (vary by project workflow):

• 11 — To Do
• 21 — In Progress
• 31 — Done

---

assign_issue — Assign Issue

Assigns an issue to a Jira user.

Tool reference: {{tool:jira_assign_issue}}

Parameter	Required	Description
issue_key	Yes	Issue key
assignee_id	Yes	Jira user account ID

---

search_issues — Search Issues

Searches issues using JQL (Jira Query Language).

Tool reference: {{tool:jira_search_issues}}

Parameter	Required	Description
jql	Yes	JQL query string — e.g. project = ENG AND status = "In Progress" ORDER BY updated DESC
max_results	No	Number of results to return (default 10, max 50)

Returns: Array of issues with issue_key, summary, status, assignee

---

get_projects — Get Projects

Lists all accessible Jira projects.

Tool reference: {{tool:jira_get_projects}}

No parameters required.

Returns: Array of project_key, name, project_type

---

Using Jira in an agent

Bug reporting from support calls

When a user reports a technical bug:
1. Collect: a summary of what's broken, what they expected, and any error messages.
2. Use {{tool:jira_create_issue}} to log the bug:
   - project_key: SUPPORT
   - issue_type: Bug
   - summary: one-line description of what's broken
   - description: full details including steps to reproduce and expected behaviour
3. Tell the user the issue key: "I've logged this as SUPPORT-[N] and the engineering team will investigate."

When a user asks for the status of an issue they've already reported:
- Ask for the issue key (e.g. SUPPORT-42)
- Use {{tool:jira_get_issue}} and summarise the status and assignee in plain language

Troubleshooting

401 Unauthorized

The email and API token combination is incorrect, or the API token has been revoked. Regenerate the token and reinstall.

404 Project not found

The project_key doesn't exist or this account doesn't have access to it. Project keys are case-sensitive (always uppercase).

400 Invalid transition

The transition_id doesn't apply to the current issue status. Transition IDs are workflow-specific — verify them in your Jira project's workflow settings.

Issue created but assignee is wrong

Jira uses account IDs, not display names or emails. Find an account ID: search for the user in Jira → view their profile → the ID is in the URL.