Skip to main content

​
Overview

Software for bug tracking, issue tracking and agile project management. Through Langdock’s integration, you can access and manage Jira directly from your conversations.
Authentication: OAuth Category: Development Availability: All workspace plans

​
Available Actions

​
Get fields

jira.get_fields
Returns all Jira fields with schema metadata. Use this to find field IDs (e.g., customfield_12345) and understand their types. Requires Confirmation: No Parameters: None Output: Returns the operation result

​
Get priorities

jira.get_priorities
Returns all issue priorities (id and name). Use this to map human-friendly names to IDs. Requires Confirmation: No Parameters: None Output: Returns the operation result

​
Find components

jira.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. Requires Confirmation: No Parameters:
  • projectIdsOrKeys (TEXT, Optional): Comma-separated list of project IDs or keys to get components for (e.g., “NCE” or “NCE,PROJ2”). If not provided, returns components from all accessible projects.
  • query (TEXT, Optional): Filter components by name. Returns components whose name contains this string.
  • maxResults (TEXT, Optional): Maximum number of components to return (default: 50, max: 50).
  • startAt (TEXT, Optional): Index of the first component to return (for pagination). Default: 0.
  • orderBy (TEXT, Optional): Order results by field. Valid values: description, -description, +description, name, -name, +name, projectKey, -projectKey, +projectKey.
Output: Returns the operation result

​
Create issue

jira.create_issue
Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask Requires Confirmation: Yes Parameters:
  • parentKey (TEXT, Optional): The key of the parent issue, e.g. key of an epic
  • assigneeId (TEXT, Optional): The Account ID of the assignee user
  • description (MULTI_LINE_TEXT, Optional): A description of the issue. Can be either plain text or a JSON-formatted Jira document structure for rich formatting (with type: ‘doc’, content array, and version: 1). If JSON parsing fails, it will fall back to plain text formatting.
  • projectKey (TEXT, Required): The key of the project to assign the newly created issue to
  • summary (TEXT, Required): A short summary of the issue
  • issueTypeId (TEXT, Required): The ID of the issue type
  • priorityId (TEXT, Optional): The priority ID. If both priorityId and priorityName are provided, priorityId will be used.
  • labels (OBJECT, Optional): Array of label strings, e.g., [“bug”, “frontend”].
  • dueDate (TEXT, Optional): Due date in YYYY-MM-DD format. If a datetime is provided, only the date part will be used.
  • componentIds (OBJECT, Optional): Array of component IDs to assign to the issue, e.g., [“10000”, “10001”]. Use get_project with expand=components to find available component IDs for a project.
  • fixVersionIds (OBJECT, Optional): Array of fix version IDs, e.g., [“10010”, “10011”]. Use get_project with expand=versions to find available version IDs.
  • reporterId (TEXT, Optional): The Account ID of the reporter user. Use find_users to look up user IDs.
  • customFields (TEXT, Optional): JSON object with custom field values. Use field IDs as keys (e.g., customfield_12345). Select fields require object format: { “customfield_12345”: { “value”: “Option” } }. Use ‘Get custom field options’ to find valid values.
Output: Returns the operation result

​
Search for issues

jira.search_for_issues
Searches for issues using JQL Requires Confirmation: No Parameters:
  • jql (TEXT, Optional): A JQL expression. For performance reasons, this parameter requires a bounded query. A bounded query is a query with a search restriction. Example of an unbounded query: order by key desc. Example of a bounded query: assignee = currentUser() order by key. Additionally, orderBy clause can contain a…
  • fields (TEXT, Optional): A list of Jira issue fields to include in the response, formatted as a JSON array in square brackets. Default: [“id”, “key”, “summary”] Format: JSON array of strings, e.g., [“id”, “key”, “status”, “project”] - Must be enclosed in square brackets [] - Each field name should be in quotes and separa…
Output: Returns the operation result

​
Get issue types for project

jira.get_issue_types_for_project
Gets all issue types for a project Requires Confirmation: No Parameters:
  • projectId (ID, Required): The ID of the project
Output: Returns the operation result

​
Get all issue types for user

jira.get_all_issue_types_for_user
Gets all issue types for a user Requires Confirmation: No Parameters: None Output: Returns the operation result

​
Get recent projects

jira.get_recent_projects
Returns a list of up to 20 projects recently viewed by the user that are still visible to the user Requires Confirmation: No Parameters: None Output: Returns the operation result

​
Find users

jira.find_users
Returns a list of active users that match the search string and property Requires Confirmation: No Parameters:
  • query (TEXT, Optional): A query string that is matched against user attributes (displayName, and emailAddress) to find relevant users. The string can match the prefix of the attribute’s value. For example, query=john matches a user with a displayName of John Smith and a user with an emailAddress of johnson@example.com
Output: Returns the operation result

​
Get current user

jira.get_current_user
Gets details about the user of the current connection Requires Confirmation: No Parameters: None Output: Returns the operation result

​
Get issue

jira.get_issue
Gets an issue by id or key Requires Confirmation: No Parameters:
  • issueId (ID, Required): Id or key of the issue that should be retrieved
Output: Returns the operation result

​
Update issue

jira.update_issue
Updates an issue Requires Confirmation: Yes Parameters:
  • issueId (ID, Required): Id of the issue that should be updated
  • assigneeId (TEXT, Optional): The Account ID of the assignee user
  • description (TEXT, Optional): A description of the issue. Can be either plain text or a JSON-formatted Jira document structure for rich formatting (with type: ‘doc’, content array, and version: 1). If JSON parsing fails, it will fall back to plain text formatting.
  • projectKey (TEXT, Optional): The key of the project to assign the newly created issue to
  • summary (TEXT, Optional): A short summary of the issue
  • issueTypeId (TEXT, Optional): The ID of the issue type
  • priorityId (TEXT, Optional): The priority ID. If both priorityId and priorityName are provided, priorityId will be used.
  • labels (OBJECT, Optional): Array of label strings, e.g., [“bug”, “frontend”].
  • dueDate (TEXT, Optional): Due date in YYYY-MM-DD format. If a datetime is provided, only the date part will be used.
  • componentIds (OBJECT, Optional): Array of component IDs to assign to the issue, e.g., [“10000”, “10001”]. Use get_project with expand=components to find available component IDs for a project.
  • fixVersionIds (OBJECT, Optional): Array of fix version IDs, e.g., [“10010”, “10011”]. Use get_project with expand=versions to find available version IDs.
  • customFields (TEXT, Optional): JSON object with custom field values. Only include fields to update. Use field IDs as keys (e.g., customfield_12345). Select fields require object format: { “customfield_12345”: { “value”: “Option” } }. Use ‘Get custom field options’ to find valid values.
Output: Returns the operation result

​
Create subtask

jira.create_subtask
Creates a subtask for an existing issue Requires Confirmation: Yes Parameters:
  • parrentissueKey (TEXT, Required): The key of the parent issue (e.g., “PROJECT-123”)
  • summary (TEXT, Required): The title/summary of the subtask
  • projectKey (TEXT, Optional): The project key (will be extracted from parent issue if not provided)
  • subtasktypeId (TEXT, Optional): The ID of the subtask issue type (defaults to ‘10000’ if not provided)
  • description (TEXT, Optional): A description of the subtask. Can be either plain text or a JSON-formatted Jira document structure for rich formatting (with type: ‘doc’, content array, and version: 1). If JSON parsing fails, it will fall back to plain text formatting.
  • assigneeId (TEXT, Optional): The ID of the user to assign the subtask to
  • reporterId (TEXT, Optional): The ID of the user who is reporting the subtask
  • priorityId (TEXT, Optional): The ID of the priority level for the subtask
  • labels (OBJECT, Optional): Array of label strings, e.g., [“bug”, “frontend”].
  • componentIds (OBJECT, Optional): Array of component IDs, e.g., [“10000”, “10001”]. If both componentIds and componentNames are provided, IDs take precedence.
  • componentNames (OBJECT, Optional): Array of component names, e.g., [“API”, “UI”]. Used when componentIds is not provided.
  • fixVersionIds (OBJECT, Optional): Array of fixVersion IDs, e.g., [“10010”, “10011”]. If both fixVersionIds and fixVersionNames are provided, IDs take precedence.
  • fixVersionNames (OBJECT, Optional): Array of fixVersion names, e.g., [“v1.0”, “v1.1”]. Used when fixVersionIds is not provided.
  • dueDate (TEXT, Optional): Due date in YYYY-MM-DD format. If a datetime is provided, only the date part will be used.
  • customFields (TEXT, Optional): JSON object with custom field values. Use field IDs as keys (e.g., customfield_12345). Select fields require object format: { “customfield_12345”: { “value”: “Option” } }. Use ‘Get custom field options’ to find valid values.
Output: Returns the operation result

​
Move issue by transition id

jira.move_issue_by_transition_id
Moves an issue through workflow stages using a transition id Requires Confirmation: Yes Parameters:
  • issueId (ID, Required): Id or key of the issue that should be moved
  • transitionId (TEXT, Required):
  • comment (TEXT, Optional): A comment to add during the transition
Output: Returns the operation result

​
Get transition id

jira.get_transition_id
Gets available transition ids for a Jira issue Requires Confirmation: No Parameters:
  • issueId (ID, Required): Id or key of the issue for which the transitions should be received.
Output: Returns the operation result

​
Get field metadata for issue type

jira.get_field_metadata_for_issue_type
Gets all available field metadata for an in issue type Requires Confirmation: No Parameters:
  • projectId (TEXT, Required): Id or key of the project the issue metadata should be received for.
  • issueTypeId (TEXT, Required): Id of the issue type the data should be retrieved for.
Output: Returns the operation result

​
Get project

jira.get_project
Returns the project details for a project Requires Confirmation: No Parameters:
  • projectIdOrKey (ID, Required): The project ID or project key
  • expand (TEXT, Optional): Use expand to include additional information in the response. This parameter accepts a comma-separated list. For example: description,lead,issueTypes,url,projectKeys,permissions,insight
  • properties (TEXT, Optional): A list of project properties to return for the project. This parameter accepts a comma-separated list
Output: Returns the operation result

​
Get comments

jira.get_comments
Returns all comments for an issue. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name. Requires Confirmation: No Parameters:
  • issueIdOrKey (ID, Required): The ID or key of the issue. Required and can be provided by the user or passed down from the search_for_issues action.
  • startAt (TEXT, Optional): The index of the first item to return in a page of results (page offset)
  • maxResults (TEXT, Optional): The maximum number of items to return per page
  • orderBy (TEXT, Optional): Order the results by a field. Accepts created to sort comments by their created date
  • expand (TEXT, Optional): Use expand to include additional information about comments in the response
Output: Returns the operation result

​
Add comment

jira.add_comment
Adds a comment to an issue. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name. Requires Confirmation: Yes Parameters:
  • issueIdOrKey (TEXT, Required): The ID or key of the issue. Required and can be provided by the user or passed down from the search_for_issues action.
  • comment (MULTI_LINE_TEXT, Required): The comment content. Can be plain text or Atlassian Document Format (ADF) JSON for rich formatting. For ADF, provide a JSON object with type: ‘doc’, version: 1, and content array. Example ADF: {“type”:“doc”,“version”:1,“content”:[{“type”:“paragraph”,“content”:[{“type”:“text”,“text”:“Hello ”},…
  • visibilityType (TEXT, Optional): Whether the comment visibility is restricted by group or project role
  • visibilityValue (TEXT, Optional): The name of the group or the name of the project role that visibility of this comment is restricted to
  • visibilityIdentifier (TEXT, Optional): The ID of the group or the name of the project role that visibility of this comment is restricted to
  • expand (TEXT, Optional): Use expand to include additional information about comments in the response
  • properties (TEXT, Optional): A list of comment properties as JSON. Each property key is limited to 255 characters
Output: Returns the operation result

​
Update comment

jira.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. Requires Confirmation: Yes Parameters:
  • issueIdOrKey (TEXT, Required): The ID or key of the issue. Required and can be provided by the user or passed down from the search_for_issues action.
  • commentId (TEXT, Required): The ID of the comment
  • comment (MULTI_LINE_TEXT, Required): The comment content. Can be plain text or Atlassian Document Format (ADF) JSON for rich formatting. For ADF, provide a JSON object with type: ‘doc’, version: 1, and content array. Example ADF: {“type”:“doc”,“version”:1,“content”:[{“type”:“paragraph”,“content”:[{“type”:“text”,“text”:“Hello ”},…
  • visibilityType (TEXT, Optional): Whether the comment visibility is restricted by group or project role
  • visibilityValue (TEXT, Optional): The name of the group or the name of the project role that visibility of this comment is restricted to
  • visibilityIdentifier (TEXT, Optional): The ID of the group or the name of the project role that visibility of this comment is restricted to
  • notifyUsers (TEXT, Optional): Whether users are notified by email
  • overrideEditableFlag (TEXT, Optional): Whether screen security is overridden to enable hidden fields to be edited
  • expand (TEXT, Optional): Use expand to include additional information about comments in the response
  • properties (TEXT, Optional): A list of comment properties as JSON. Each property key is limited to 255 characters
Output: Returns the operation result

​
Get custom field options

jira.get_custom_field_options
Returns allowed options for a given custom field. Optionally scope by project and issue type to reflect context-specific options. Requires Confirmation: No Parameters:
  • fieldId (TEXT, Required): ID of the custom field (e.g., customfield_12345)
  • projectId (TEXT, Required): Optional: Scope options to a project
  • issueTypeId (TEXT, Required): Optional: Scope options to an issue type
Output: Returns the operation result

​
Get project stages

jira.get_project_stages
Gets the stages for issue types of a project Requires Confirmation: No Parameters:
  • projectId (TEXT, Required): Id or key of the project the stages should be retrieved for.
Output: Returns the operation result

​
Triggers

​
Updated issue

jira.updated_issue
Triggers when an issue was updated. Parameters:
  • projectKey (TEXT, Optional): The key of the project that should trigger the workflow
  • issueType (TEXT, Optional): The type of issue that should trigger the workflow
Output: Returns the operation result

​
New issue

jira.new_issue
Triggers when new issues are created. Optionally filter with JQL. Parameters:
  • jqlQuery (TEXT, Optional): Optional JQL query to filter issues. Example: project = “PROJ” AND status = “In Progress” AND assignee = currentUser() AND priority in (High, Highest) ORDER BY created DESC
Output: Returns the operation result