Jira integration for AI agents
Track and manage issues, projects, releases, and assets
Connect Jira to Langdock and use it in chat, in agents and in workflows.
39 actions · 3 triggers
Jira actions
Each action is one step an agent or workflow can run in Jira.
- Add comment
Adds a comment to an issue. On Jira Service Management requests the comment is a public reply the customer sees, unless Comment visibility is set to Internal note. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
- Add worklog
Logs time spent on an issue as a worklog and, by default, reduces the issue's remaining estimate by the same amount. Use Get worklogs to see what is already logged. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
- Create asset
Creates an object in the connected Jira Assets workspace
- Create issue
Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask.
- Create project
Creates a Jira project from an installed project template.
- Create request
Raises a Jira Service Management request, the same way a customer does in the portal, optionally on behalf of another person. Use Get request type fields first to see which fields the request type needs
- Create subtask
Creates a subtask for an existing issue.
- Create version
Creates a new release version in a Jira project (e.g., 'RELEASE - 1.1.0'). Use this as the first step in a release workflow: create the version, then bulk-update ticket fixVersions to it, then transition tickets to 'Released'. Requires Administer Projects permission.
- Find components
Returns a paginated list of components for one or more projects. Use this to discover component IDs before creating or updating issues with components.
- Find users
Returns a list of active users that match the search string and property.
- Get all issue types for user
Gets all issue types for a user.
- Get asset
Returns one asset and its attributes. Use List assets or Search assets to find the ID
- Get comments
Returns all comments for an issue. On Jira Service Management requests, isPublic tells customer-visible replies apart from internal notes, which must not be repeated to the customer. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
- Get current user
Gets details about the user of the current connection.
- Get custom field options
Returns allowed options for a given custom field. Optionally scope by project and issue type to reflect context-specific options.
- Get field metadata for issue type
Gets all available field metadata for an in issue type.
- Get fields
Returns all Jira fields with schema metadata. Use this to find field IDs (e.g., customfield_12345) and understand their types.
- Get issue
Gets an issue by id or key.
- Get issue link types
Lists the issue link types of the Jira site with their wording in both directions, for example Duplicate: "duplicates" / "is duplicated by". Use the wording with Link issues
- Get issue types for project
Gets all issue types for a project.
- Get priorities
Returns all issue priorities (id and name). Use this to map human-friendly names to IDs.
- Get project
Returns the project details for a project.
- Get project stages
Gets the stages for issue types of a project.
- Get recent projects
Returns a list of up to 20 projects recently viewed by the user that are still visible to the user.
- Get request
Gets a Jira Service Management request with its request type, customer, status, participants, SLAs and the fields the customer filled in. Use Get comments for the conversation
- Get request type fields
Gets the fields a Jira Service Management request type asks for, including which are required and their allowed values. Call this before Create request so you know which fields to fill
- Get transition id
Gets available transition IDs for a Jira issue, with the fields each transition requires and the resolutions it accepts.
- Get versions
Lists all release versions for a Jira project. Use this to look up version IDs before creating issues, updating fixVersions on tickets, or building release workflows. Supports filtering by status (released, unreleased, archived).
- Get worklogs
Returns the time logged on an issue: who logged it, when the work started, how long it took and the worklog comment. Use it to see how much time has been spent on an issue or by a person in a period. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
- Link issues
Links two Jira issues, for example to mark a request as a duplicate of another or to relate it to an incident. The link reads "<issue> <relationship> <linked issue>"
- List assets
Lists asset summaries from the connected Jira Assets workspace. Use Search assets to filter with AQL
- List request types
Lists the request types of a Jira Service Management service desk, such as "Get IT help" or "Request new hardware". Use the returned ID with Get request type fields and Create request
- List service desks
Lists the Jira Service Management service desks (service projects) the user can access. Use the returned ID to list request types or raise a request
- Move issue by transition id
Moves an issue through workflow stages using a transition id, optionally setting a resolution and adding a public or internal comment.
- Search assets
Searches Jira Assets objects with Assets Query Language (AQL). Use List assets to browse without a filter
- Search for issues
Searches for issues using JQL.
- Update asset
Updates selected asset attributes while preserving the current object's other attributes
- Update comment
Updates a comment. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
- Update issue
Updates an existing Jira issue. Only send the fields the user asked to change and leave out all others, even if you know their current values. Can change summary, description, assignee, reporter, priority, labels, due date, components, fix versions, custom fields and attachments.
Jira triggers
A trigger starts a workflow when something happens in Jira.
- New comment
Triggers when someone adds a comment to a Jira issue. By default it skips comments written by the connected account and internal notes on Jira Service Management requests, so a workflow can react to customer replies without triggering on its own comments
- New issue
Triggers when new issues are created. Optionally filter with JQL.
- Updated issue
Triggers when an existing Jira issue is modified (e.g., status change, field edit, reassignment). Does not fire for newly created issues — use "New issue" for that.
Agent templates that use Jira
Setup and permissions
An action can ask for your confirmation before it runs. In an agent, each action is set to “Always allow” or “Needs approval”.