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 & Issue Tracking
Availability: All workspace plans

​
Available Actions

​
Create Issue

jira.createIssue
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 (plain text or JSON-formatted Jira document)
    • 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
    • customFields (TEXT, Optional): Custom field values when creating a Jira issue (JSON object)
Output: Returns the created issue with key, ID, and all specified details

​
Search for Issues

jira.searchforIssues
Searches for issues using JQL Requires Confirmation: No Parameters:
  • jql (TEXT, Optional): A JQL expression for performance reasons, this parameter requires a bounded query
    • fields (TEXT, Optional): A list of Jira issue fields to include in the response, formatted as a JSON array
Output: Returns array of issues matching the JQL query with specified fields

​
Get Issue Types for Project

jira.getIssueTypesforProject
Gets all issue types for a project Requires Confirmation: No Parameters:
  • projectId (TEXT, Required): The ID of the project
Output: Returns array of issue types available for the project

​
Get All Issue Types for User

jira.getAllIssueTypesforUser
Gets all issue types for a user Requires Confirmation: No Parameters: None Output: Returns array of all issue types available to the user

​
Get Recent Projects

jira.getRecentProjects
Returns a list of up to 20 projects recently viewed by the user Requires Confirmation: No Parameters: None Output: Returns array of recent projects with their details

​
Find Users

jira.findUsers
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
Output: Returns array of users matching the search criteria

​
Get Current User

jira.getCurrentUser
Gets details about the user of the current connection Requires Confirmation: No Parameters: None Output: Returns current user details including ID, email, and display name

​
Get Issue

jira.getIssue
Gets an issue by ID or key Requires Confirmation: No Parameters:
  • issueId (TEXT, Required): ID or key of the issue that should be retrieved
Output: Returns issue details including all fields and properties

​
Update Issue

jira.updateIssue
Updates an issue Requires Confirmation: Yes Parameters:
  • issueId (TEXT, 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
    • 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
    • customFields (TEXT, Optional): Custom field values when updating a Jira issue
Output: Returns the updated issue with new values

​
Create Subtask

jira.createSubtask
Creates a subtask for an existing issue Requires Confirmation: Yes Parameters:
  • parrentissueKey (TEXT, Required): The key of the parent issue
    • 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’)
    • description (TEXT, Optional): A description of the subtask
    • 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
    • customFields (TEXT, Optional): Custom field values when creating a Jira subtask
Output: Returns the created subtask with key, ID, and parent relationship

​
Move Issue by Transition ID

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

​
Get Transition ID

jira.getTransitionID
Gets available transition IDs for a Jira issue Requires Confirmation: No Parameters:
  • issueId (TEXT, Required): ID or key of the issue for which the transitions should be received
Output: Returns array of available transitions with their IDs and names

​
Get Field Metadata for Issue Type

jira.getFieldMetadataforIssueType
Gets all available field metadata for an 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 field metadata including custom fields and their configurations

​
Get Project

jira.getProject
Returns the project details for a project Requires Confirmation: No Parameters:
  • projectIdOrKey (TEXT, Required): The project ID or project key
    • expand (TEXT, Optional): Use expand to include additional information in the response
    • properties (TEXT, Optional): A list of project properties to return for the project
Output: Returns project details including name, key, description, and other properties

​
Get Comments

jira.getComments
Returns all comments for an issue Requires Confirmation: No Parameters:
  • issueIdOrKey (TEXT, Required): The ID or key of the issue
    • startAt (TEXT, Optional): The index of the first item to return in a page of results
    • maxResults (TEXT, Optional): The maximum number of items to return per page
    • orderBy (TEXT, Optional): Order the results by a field
    • expand (TEXT, Optional): Use expand to include additional information about comments
Output: Returns array of comments with their content, author, and timestamps

​
Add Comment

jira.addComment
Adds a comment to an issue Requires Confirmation: Yes Parameters:
  • issueIdOrKey (TEXT, Required): The ID or key of the issue
    • comment (MULTI_LINE_TEXT, Required): The text content of the comment
    • 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
    • visibilityIdentifier (TEXT, Optional): The ID of the group or the name of the project role
    • expand (TEXT, Optional): Use expand to include additional information about comments
    • properties (TEXT, Optional): A list of comment properties as JSON
Output: Returns the created comment with ID and content

​
Update Comment

jira.updateComment
Updates a comment Requires Confirmation: Yes Parameters:
  • issueIdOrKey (TEXT, Required): The ID or key of the issue
    • commentId (TEXT, Required): The ID of the comment
    • comment (MULTI_LINE_TEXT, Required): The text content of the comment
    • 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
    • visibilityIdentifier (TEXT, Optional): The ID of the group or the name of the project role
    • notifyUsers (TEXT, Optional): Whether users are notified by email
    • overrideEditableFlag (TEXT, Optional): Whether screen security is overridden
    • expand (TEXT, Optional): Use expand to include additional information about comments
    • properties (TEXT, Optional): A list of comment properties as JSON
Output: Returns the updated comment with new content

​
Get Project Stages

jira.getProjectStages
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 array of project stages with their details

​
Triggers

​
Updated Issue

jira.updatedIssue
Triggers when an issue was updated Requires Confirmation: No 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 result of the operation

​
New Issue

jira.newIssue
Triggers when new issues are created Requires Confirmation: No Parameters: None Output: Returns the result of the operation

​
New Issue (JQL)

jira.newIssueJQL
Triggers when new issues are created Requires Confirmation: No Parameters:
  • jqlQuery (TEXT, Required): JQL query to filter issues
Output: Returns the result of the operation

​
Create Issue

jira.createIssue
Creates an issue in Linear Requires Confirmation: Yes Parameters:
  • teamId (TEXT, Required): The ID of the team to create the issue in. Team id’s can be retrieved using the ‘Get teams’ action
    • title (TEXT, Required): The title of the issue
    • description (TEXT, Optional): The description of the issue in markdown format
    • options (OBJECT, Optional): Provide additional Linear issue properties as a JSON object. This field accepts any valid Linear issue fields beyond the basic ones above
Output: Returns the created issue with ID, title, identifier, URL, priority, state, assignee, and labels

​
Create Comment

jira.createComment
Creates a new issue comment in Linear Requires Confirmation: Yes Parameters:
  • issueId (TEXT, Optional): The ID of the issue to comment on
    • commentBody (TEXT, Required): The body of the comment to add
Output: Returns the created comment with ID and content

​
Update an Issue

jira.updateanIssue
Updates an existing issue in Linear Requires Confirmation: Yes Parameters:
  • title (TEXT, Optional): The new title of the issue
    • assigneeId (TEXT, Optional): The ID of the person assigned to the task
    • stateId (TEXT, Optional): The state of the issue. Can be Backlog, Todo, To discuss, In Progress, Blocked, In Review, Waiting for Release, Done, Canceled, Triage
    • issueId (TEXT, Required): The ID of the issue that should be updated
Output: Returns the updated issue with new values

​
Get Issue Details

jira.getIssueDetails
Gets the details of a specific issue Requires Confirmation: No Parameters:
  • issueId (TEXT, Required): The ID of the issue
Output: Returns issue details including ID, title, description, state, assignee, labels, and other properties

​
Get Team Members

jira.getTeamMembers
Gets all team members in a given Linear team Requires Confirmation: No Parameters:
  • teamId (TEXT, Required): The ID of the team
Output: Returns array of team members with their IDs, names, and other details

​
Get Current User

jira.getCurrentUser
Get the user details of your profile in Linear Requires Confirmation: No Parameters: None Output: Returns current user details including ID, name, email, and other profile information

​
Get Teams

jira.getTeams
Lists all teams in Linear workspace Requires Confirmation: No Parameters: None Output: Returns array of teams with their IDs, names, and other details

​
Get Issues in Team

jira.getIssuesinTeam
Gets all issues from a given team Requires Confirmation: No Parameters:
  • teamId (TEXT, Required): The team ID to use for searching issues
Output: Returns array of issues in the specified team

​
Search Issues

jira.searchIssues
Searches for issues in Linear Requires Confirmation: No Parameters:
  • teamId (TEXT, Optional): The ID of the team to search issues in. Leave empty to search across all teams
    • query (TEXT, Optional): Text to search for in issue titles and descriptions
    • status (TEXT, Optional): Filter by issue status (e.g., ‘backlog’, ‘in_progress’, ‘done’)
    • assigneeId (TEXT, Optional): Filter issues by assignee ID
    • limit (TEXT, Optional): Maximum number of issues to return (default: 50, max: 100)
Output: Returns array of issues matching the search criteria

​
Common Use Cases

Data Management

Manage and organize your Jira data

Automation

Automate workflows with Jira

Reporting

Generate insights and reports

Integration

Connect Jira with other tools

​
Best Practices

Getting Started:
  1. Enable the Jira integration in your workspace settings
  2. Authenticate using OAuth
  3. Test the connection with a simple read operation
  4. Explore available actions for your use case
Important Considerations:
  • Ensure proper authentication credentials
  • Respect rate limits and API quotas
  • Review data privacy settings
  • Test operations in a safe environment first

​
Troubleshooting

IssueSolution
Authentication failedVerify your OAuth credentials
Rate limit exceededReduce request frequency
Data not foundCheck permissions and data availability
Connection timeoutVerify network connectivity

​
Support

For additional help with the Jira integration, contact support@langdock.com