DataToRAGDocs
Sign in

Jira

Search issues with JQL, create, update, transition, and comment on tickets.

The Jira tools let your AI assistant search, create, update, and move issues through their workflow, plus add, edit and delete comments, look up an attachment's details, and add a file from another connected service as an attachment.

Available operations

Tool Description
jira_search Search issues using JQL (Jira Query Language). Supports pagination via next_page_token
jira_get_issue Get full details for an issue by key (e.g. PROJ-123): summary, status, priority, assignee, reporter, description, labels, dates, comments count, attachments
jira_create_issue Create a new issue in a specified project. Returns the issue key and URL
jira_update_issue Update an issue's summary, description, or arbitrary fields via additional_fields
jira_get_transitions Get available workflow transitions for an issue. Use returned IDs with jira_transition_issue
jira_transition_issue Move an issue to a new workflow status
jira_get_comments Get all comments on an issue
jira_add_comment Add a comment to an issue
jira_edit_comment Edit an existing comment
jira_delete_comment Delete a comment
jira_get_attachment Get attachment metadata by ID: filename, size, MIME type, content URL
jira_add_attachment Attach a file to an issue from a file reference: a Gmail message as its original .eml, or one of its attachments by part id, under the sender's file name. The file never passes through the conversation; the answer is a receipt with the name, size and SHA-256 of what was sent. See Moving files between services
jira_list_fields List all available fields (system + custom) to discover field IDs for creates/updates
jira_search_users Search users by name, username, or email. Returns display names and account IDs
jira_delete_issue Permanently delete an issue. See the warning below before using it

Required scopes

  • read:jira-work, write:jira-work, read:jira-user

Deleting an issue

jira_delete_issue cannot be undone through the API. Deleted issues do not go to a trash or an archive, and Jira does not reuse the key, so every link, branch name and comment pointing at it breaks permanently.

Prefer transitioning the issue to Done or Won't Do, which keeps its history and leaves the key resolvable.

If you do delete: an issue with subtasks is rejected outright unless delete_subtasks is true, and passing that destroys the subtasks along with the parent. Linked issues are not deleted, only subtasks.

Multiple accounts

Every tool on this page takes an optional account argument: the email address of the connected Atlassian account to act on. Omit it and the default account is used. Connect more than one Atlassian account and a single request can reach whichever one the work belongs to. An account that can reach several sites acts on the first site Atlassian lists for it.

Example prompts

  • "Find all Jira tickets assigned to me that are in progress, sorted by priority"
  • "Create a bug ticket in PROJ from the error in this email with steps to reproduce"
  • "Transition JIRA-456 to 'In Review' and add a comment linking the PR"
  • "What Jira tickets did I close this week? Summarize them for the standup"
  • "Update JIRA-789 with the new ETA and add a comment saying why it moved"

Frequently asked questions

Can I undo deleting a Jira issue? #

No. Deleting an issue cannot be undone through the Jira API. Deleted issues do not go to a trash or an archive, and Jira does not reuse the key, so every link, branch name and comment pointing at it breaks permanently. Transitioning the issue to Done or Won't Do instead keeps its history and leaves the key resolvable.

What happens to subtasks when a Jira issue is deleted? #

An issue with subtasks is rejected outright unless the delete call passes delete_subtasks, and passing it destroys the subtasks along with the parent. Linked issues are not deleted, only subtasks.

Can DataToRAG move a Jira issue through its workflow? #

Yes. One tool lists the transitions available on an issue and returns their IDs, and a second moves the issue to a new workflow status using one of those IDs. Comments can be added, edited and deleted in the same session.

How do I find the ID of a Jira custom field? #

There is a tool for it. The Jira fields tool lists every available field, system and custom, so you can discover the field IDs that creates and updates take.

Can I use more than one Atlassian site? #

Yes. Every Jira tool takes an optional account argument naming the connected Atlassian account to act on, and omitting it uses the default account. Connect more than one Atlassian account and a single request can reach whichever one the work belongs to. An account that can reach several sites acts on the first site Atlassian lists for it.

What Jira permissions does DataToRAG ask for? #

Three classic Atlassian scopes, covering reading and writing Jira work and reading Jira users. Confluence is separate on the same connection and uses granular scopes instead.

Try this on your own account

Connect Atlassian once and your assistant can run every tool on this page against your real data. Free to start, no card.

Get started free

By continuing you agree to our Terms of Service and Privacy Policy.

PreviousAtlassianNextConfluence