Jira integration

Project & Task Management · 38 actions · OAuth auth

Atlassian Jira Cloud project tracking and issue management platform

Put Jira to work View Jira integration docs

Overview

The ModuleX Jira integration lets a ModuleX agent operate Jira on your behalf — running create, update and remove actions across attachment to issues, comment to issues and multiple attachments to issues — directly from a plain-English request, using your organization's own Jira credentials. No pre-built workflow is required: the agent picks the right Jira action for the task.

Jira is a project & task management platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Jira action — or, when you want a repeatable process, the composer assembles a Jira workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Jira in plain English

Type what you want. A ModuleX agent picks the right Jira action — or chains several — and runs it. No workflow to build.

Adds an attachment to an issue
resolves toadd_attachment_to_issue
Find the issue I describe and assign it
resolves toget_issueassign_issue
Deletes a project
resolves todelete_project
Show me the all projects that match what I describe
resolves toget_all_projects

Use cases

What you can automate with Jira

Find the right issue and assign it in one promptget_issueassign_issue
Add an attachment to issue on the flyadd_attachment_to_issue
Create a custom field options context straight from a requestcreate_custom_field_options_context
Remove a project you no longer needdelete_project
Look up an all project on demandget_all_projects
Pull a list of board issues for a reportlist_board_issues

At a glance

Jira integration at a glance

VendorJira

CategoryProject & Task Management

Actions available38

AuthenticationOAuth

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 38 Jira actions

Attachment to Issues1

add_attachment_to_issue

Adds an attachment to an issue

Comment to Issues1

add_comment_to_issue

Adds a new comment to an issue

Multiple Attachments to Issues1

add_multiple_attachments_to_issue

Adds multiple attachments to an issue

Watcher to Issues1

add_watcher_to_issue

Adds a user as a watcher of an issue by passing the account ID of the user

Issues4

assign_issue

Assigns an issue to a user

create_issue

Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask

get_issue

Gets the details for an issue

update_issue

Updates an issue. A transition may be applied and issue properties updated as part of the update

Issues Against Jqls1

check_issues_against_jql

Checks whether one or more issues would be returned by one or more JQL queries

Issues Using Jqls1

count_issues_using_jql

Provides an estimated count of the issues that match a JQL query

Custom Field Options Contexts1

create_custom_field_options_context

Creates a context for custom field options

Future Sprints1

create_future_sprint

Creates a future sprint

Versions1

create_version

Creates a project version

Projects1

delete_project

Deletes a project

All Projects1

get_all_projects

Gets metadata on all projects

Boards2

get_board

Returns the board for the given board ID

list_boards

Returns all boards

Cloud Ids1

get_cloud_id

Gets the cloud ID and details of all accessible Jira Cloud sites

Current Users1

get_current_user

Returns the authenticated Jira user's account ID, display name, email, and active status

Issue Picker Suggestions1

get_issue_picker_suggestions

Returns lists of issues matching a query string

Issue Types1

get_issue_types

Gets the available issue types, optionally filtered by project

Sprints2

get_sprint

Returns the sprint for a given sprint ID

list_sprints

Returns all sprints from a board, for the given board ID

Tasks1

get_task

Gets the status of a long-running asynchronous task

Transitions1

get_transitions

Gets either all transitions or a transition that can be performed by the user on an issue

Users2

get_user

Gets details of a user

get_users

Gets the details for a list of users

Board Issues1

list_board_issues

Returns all issues from a board, for the given board ID

Epic Issues1

list_epic_issues

Returns all issues that belong to an epic on the given board

Epics1

list_epics

Returns all epics from a board, for the given board ID

Issue Comments1

list_issue_comments

Lists all comments for an issue

Labels Options1

list_labels_options

Retrieves available options for the Labels field

Sprint Issues1

list_sprint_issues

Returns all issues in a sprint

Issues to Sprints1

move_issues_to_sprint

Moves issues to a sprint, for a given sprint ID

Issues with Jqls1

search_issues_with_jql

Search for issues using JQL (Jira Query Language) via GET

Issues with Jql Posts1

search_issues_with_jql_post

Searches for issues using JQL with enhanced search capabilities via POST

Transition Issues1

transition_issue

Performs an issue transition and optionally updates the fields of the screen

Comments1

update_comment

Updates a comment

See full parameters and response schemas in the Jira integration docs

Two ways

Two ways to use Jira in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Jira action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Jira into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Jira

OAuthJira uses OAuth. You connect your Jira account once; ModuleX stores the access token encrypted and scoped to your organization, so your team shares a single secure connection.

Step-by-step setup in the Jira docs

Pairs well with Jira

Agents often chain Jira with these — connect them once and the agent can use all of them in a single task.

FAQ

Jira + ModuleX FAQ

A ModuleX agent can run any of Jira's 38 actions — across attachment to issues, comment to issues, multiple attachments to issues and watcher to issues — from a plain-English request, using your organization's own Jira credentials.

No. The agent selects the right Jira action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Through OAuth — you connect your Jira account once and ModuleX stores the token encrypted, scoped to your organization.

38, spanning attachment to issues, comment to issues, multiple attachments to issues and watcher to issues.

Jira runs on your own credentials, so any Jira usage is billed by Jira directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Jira to work in ModuleX.

Connect Jira once with your own credentials and let your agent run all 38 actions on demand.

Put Jira to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →