---
title: "ai agent for jira: pick up the issue and do the work behind it"
description: "connect jira to a room and its agents search with jql, create and edit issues, move them through the workflow, comment, log work, and build the change."
url: "https://aldena.ai/integrations/jira"
---

# ai agent for jira: pick up the issue and do the work behind it

the pages that rank for this query fall into two groups: assistants that rewrite a ticket, and plugins that summarise a sprint. neither of them can do the work the ticket describes, because neither has a server. a room does. connect jira and the same agent that reads the issue can clone the repository onto the room's machine, write the change, run the test suite, and open the pull request, then come back and move the issue.

## reading jira properly

`jira_search` takes real jql, so an agent can ask for everything unresolved in a project ordered by priority rather than guessing from a list. `jira_get_issue` reads one issue, `jira_get_visible_projects`, `jira_get_project_issue_types` and `jira_get_issue_type_fields` describe the shape of a project before an agent tries to write into it, and `jira_lookup_account_id` turns a name into the account id an assignment needs.

## writing back

`jira_create_issue` files new work, `jira_edit_issue` changes fields, `jira_transition_issue` moves an issue through its workflow, `jira_add_comment` posts an update, `jira_add_worklog` logs time, and `jira_create_issue_link` relates two issues. every one of those pauses for approval before it runs, which is the answer to the usual worry about an agent quietly reshaping a board overnight.

## example tasks

- **triage everything unresolved in the mobile project and comment with what you find.**

  the agent runs a jql query, reads the issues that match, and leaves a comment on each one. the comments are held for your approval as a batch rather than posted silently.

  tools: `jira_search` -> `jira_get_issue` -> `jira_add_comment`

- **take ALD-142, build it, and move it to in review when the pr is up.**

  it reads the issue, does the work on the room server, opens the pull request, links it back on the issue, and then transitions the ticket once the pr exists.

  tools: `jira_get_issue` -> `bash` -> `github_create_pull_request` -> `jira_add_comment` -> `jira_transition_issue`

- **when anything lands in ready for dev, tell me and draft the plan.**

  the project subscription wakes the agent in this chat on every update, and it reads the new issue and its fields before proposing an approach.

  tools: `jira_subscribe` -> `jira_get_issue` -> `jira_get_issue_type_fields`

## what it will not do

board configuration, workflow schemes, permission schemes, and project administration are outside the tool set. an agent cannot delete an issue, and it cannot reach a project the connected account was never given. attachments are not written from here.

## faq

### can ai agents be used in jira?

yes. a room that has jira connected gives every agent in it a set of jira tools: jira_search runs jql, jira_get_issue reads one issue, and jira_create_issue, jira_edit_issue, jira_transition_issue and jira_add_comment change it. the write tools stop for your approval before they run.

### is there an ai tool for jira that also does the engineering work?

that is the point of connecting jira to a room rather than installing a ticket assistant. the room has its own server, so the same agent that transitions an issue can clone the repository, write the change, run the tests, and open the pull request that closes it.

### which jira permissions does the agent actually get?

three scopes. read issues and projects covers search and metadata, create and edit issues covers writing, and look up users resolves account ids for assignments and mentions. jira scopes are fixed once the connection exists, so widening them means reconnecting the room.

### can an agent move an issue to done on its own?

jira_transition_issue is a mutating tool, so by default the run pauses and asks you first. jira_list_transitions is read only, which means an agent can always tell you which transitions are available without being able to take one.

### how does an agent know when a jira issue changes?

jira_subscribe attaches it to an issue or a whole project. updates and comments then wake the agent in the chat where it subscribed, which is how a ticket moving into ready for dev can start the work without anyone poking the agent by hand.