- Category: project management
- Auth: OAUTH2, S2S_OAUTH2, API_KEY
- Composio-managed OAuth available? Yes
- Tools: 125
- Triggers: 17
- Slug:
JIRA - Version: 20261101_00
Frequently Asked Questions
How do I set up custom OAuth credentials for Jira?
How do I set up custom OAuth credentials for Jira?
What is the difference between JQL GET, JQL POST, and Search Issues?
What is the difference between JQL GET, JQL POST, and Search Issues?
fields parameter to request specific fields, or ["*all"] to request all fields.Tools
Add Attachment
Add Attachment
Add Comment
Add Comment
JIRA_ADD_COMMENTAdds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.Input Parameters
code, links text, lists, and @mentions. To mention users, use @username for single-word names or @“Display Name” for names with spaces. Plain URLs are not hyperlinked; use [text](url) format for clickable links.visibility_value must also be provided. IMPORTANT: ‘group’ visibility requires group-level visibility to be enabled in the Jira instance settings by an administrator. For ‘role’ visibility, use JIRA_GET_PROJECT_ROLES action to discover valid role names for the project.Output
Add Field to Screen Tab
Add Field to Screen Tab
JIRA_ADD_FIELD_TO_SCREEN_TABAdds a Jira field to a screen tab. By default, Jira also updates field associations for projects linked to the screen; set skip_field_association to true to avoid that side effect.Input Parameters
Output
Add Users to Project Role
Add Users to Project Role
JIRA_ADD_USERS_TO_PROJECT_ROLEAdds users or groups to a Jira project role. Users can be identified by account ID and groups by name or ID; group names and group IDs cannot be combined in the same request.Input Parameters
Output
Add User to Group
Add User to Group
Add Watcher to Issue
Add Watcher to Issue
JIRA_ADD_WATCHER_TO_ISSUEAdds a user to an issue’s watcher list by account ID. Requires the authenticated user to have permission to view the issue and manage watchers; insufficient permissions may result in silent failure or an error response.Input Parameters
Output
Add Worklog
Add Worklog
JIRA_ADD_WORKLOGAdds a worklog entry to a Jira issue to record time spent. By default, it requests automatic adjustment of the issue’s remaining estimate; other estimate adjustment options are available.Input Parameters
Output
Analyse Jira Expression
Analyse Jira Expression
JIRA_ANALYSE_EXPRESSIONAnalyses Jira expressions for syntax validation, type checking, and complexity analysis. Use when you need to validate Jira expression syntax before using it in automation rules, custom fields, or workflows.Input Parameters
Output
Assign Issue
Assign Issue
JIRA_ASSIGN_ISSUEAssigns a Jira issue to a user, default assignee, or unassigns; supports email/name lookup.Input Parameters
'-1' (as a string) to assign to the project’s default assignee. Provide None (Python null, which translates to JSON null) or omit this field to unassign the issue. Takes precedence over assignee_name if provided. JIRA_FIND_USERS may return multiple matches or omit emails due to privacy restrictions; verify the correct account_id before assigning.account_id via JIRA_FIND_USERS first and passing it directly.Output
Bulk Create Issues
Bulk Create Issues
JIRA_BULK_CREATE_ISSUECreates multiple Jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.Input Parameters
Output
Bulk Move Issues
Bulk Move Issues
JIRA_BULK_MOVE_ISSUESSubmits an asynchronous bulk move of Jira issues using destination project, issue type, and optional parent mappings. Returns a task ID for tracking progress.Input Parameters
Output
Check User Permissions
Check User Permissions
JIRA_CHECK_PERMISSIONSCheck user permissions for global and project-level operations in Jira. Use this action to verify whether a user has specific permissions at the system level or within projects. Useful for authorization checks before performing operations, or for auditing user access rights.Input Parameters
Output
Create Board
Create Board
JIRA_CREATE_BOARDCreates a new Jira board (kanban, scrum, or agility) with optional filter and location configuration. Use this action when you need to set up a new board for a project or create a personal board for tracking work. The board will organize and visualize issues based on the specified filter or project context.Input Parameters
Output
Create Component
Create Component
Create Custom Field Context
Create Custom Field Context
JIRA_CREATE_CUSTOM_FIELD_CONTEXTCreate a project and issue-type context for a Jira custom field.Input Parameters
Output
Create Filter
Create Filter
Create Group
Create Group
Create Issue
Create Issue
JIRA_CREATE_ISSUECreates a Jira issue in a specified project with standard and additional custom fields, including fields required by the project. If the assignee is not available on the create screen, the issue may be created without the requested assignee; the omission is reported.Input Parameters
Output
Link Issues
Link Issues
JIRA_CREATE_ISSUE_LINKLinks two Jira issues using a specified link type with optional comment.Input Parameters
Output
Create Issue Type
Create Issue Type
Get JQL Autocomplete Data
Get JQL Autocomplete Data
JIRA_CREATE_JQL_AUTOCOMPLETEDATARetrieves JQL autocomplete reference data including reserved words, field names, and function names. Use when building JQL query editors or validating JQL syntax.Input Parameters
Output
Create Project
Create Project
JIRA_CREATE_PROJECTCreates a new Jira project with required lead, template, and type configuration.Input Parameters
Output
Create Screen
Create Screen
Create Screen Scheme
Create Screen Scheme
Create Sprint
Create Sprint
JIRA_CREATE_SPRINTCreates a new sprint on a Jira board with optional start/end dates and goal.Input Parameters
Output
Create Version
Create Version
JIRA_CREATE_VERSIONCreates a new version for releases or milestones in a Jira project.Input Parameters
Output
Delete Attachment
Delete Attachment
Delete Comment
Delete Comment
Delete Issue
Delete Issue
Delete Issue Link
Delete Issue Link
Delete Statuses
Delete Statuses
Delete Version
Delete Version
JIRA_DELETE_VERSIONDeletes a Jira version and optionally reassigns its issues.Input Parameters
Output
Delete Worklog
Delete Worklog
JIRA_DELETE_WORKLOGDeletes a worklog from a Jira issue with estimate adjustment options.Input Parameters
adjust_estimate is ‘manual’ (e.g., ‘1h 30m’, ‘5d’).Output
Edit Issue
Edit Issue
JIRA_EDIT_ISSUEUpdates a Jira issue with field values and operations, with direct field parameters taking precedence over fields. If no merged fields are set and other direct parameters are absent, the request can also clear the assignee and due date.Input Parameters
update for more complex operations like list modifications. IMPORTANT: The ‘status’ field cannot be updated via this action - use JIRA_TRANSITION_ISSUE action instead to change issue status. Rich text fields (description, environment, and custom textarea fields) support plain text or Markdown - they are automatically converted to Atlassian Document Format (ADF). You can also pass ADF directly as a JSON object.code, links text, and lists. Note: Jira enforces size limits on the description field (typically ~32,767 characters, varies by instance). For very large content, consider splitting across comments or using attachments.False requires admin or project admin permissions.Output
Evaluate Jira Expression
Evaluate Jira Expression
JIRA_EVALUATE_JIRA_EXPRESSIONTool to evaluate Jira expressions using the enhanced search API. Use when you need to extract or transform data from Jira using Jira expression language. Useful for complex data queries, transformations, and building custom objects from Jira data.Input Parameters
Output
Bulk Fetch Issues
Bulk Fetch Issues
JIRA_FETCH_BULK_ISSUESTool to bulk fetch multiple Jira issues by their IDs or keys (max 100 per call). Use when you need to retrieve details for multiple issues efficiently in a single API call.Input Parameters
Output
Find Users (Deprecated)
Find Users (Deprecated)
JIRA_FIND_USERSDEPRECATED: Use JIRA_FIND_USERS2 instead. Searches for Jira users by email or display name to find account IDs; essential for assigning issues, adding watchers, and other user-related operations. Broad queries may return multiple matches — always disambiguate using full email before selecting an account_id. Results may include app/bot accounts; verify account_type is a human user before use in downstream operations.Input Parameters
Output
Find Users 2
Find Users 2
JIRA_FIND_USERS2Searches Jira users by query string, account ID, or property, returning one page of matches. Use it to find users for issue assignment, watchers, or other user-related operations; page size is limited to 1,000.Input Parameters
Output
Find Users For Picker
Find Users For Picker
JIRA_FIND_USERS_FOR_PICKERFind users for picker components by matching query against user attributes like display name and email.Input Parameters
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.total. Defaults to 50.Output
Find Users With Permissions
Find Users With Permissions
JIRA_FIND_USERS_WITH_PERMISSIONSFind users who hold every requested permission for a Jira issue or project.Input Parameters
Output
Get All Groups
Get All Groups
JIRA_GET_ALL_GROUPSRetrieves a page of groups from the Jira instance. Useful for resolving correct group names or IDs before passing them to other tools. Some returned groups are system-managed and may be inaccessible via other group operations. Use start_at/max_results to page through results.Input Parameters
next_start_at from the response (or increment start_at by max_results); stop when has_next_page is false.has_next_page/next_start_at to fetch more.Output
Get All Issue Type Schemes
Get All Issue Type Schemes
Get all projects
Get all projects
JIRA_GET_ALL_PROJECTSRetrieves a page of visible Jira projects with server-side filtering and pagination. Results are limited by the user’s access, and an empty page may reflect the requested offset or filters; use numeric project IDs for durable references because project keys can change.Input Parameters
description (to include the project description), issueTypes (to include all issue types associated with the project), lead (to include information about the project lead), and projectKeys (to include all project keys associated with the project).['property1', 'property2'].Output
Get Issue Statuses
Get Issue Statuses
Get All Users
Get All Users
JIRA_GET_ALL_USERSRetrieves all users from the Jira instance including active, inactive, app accounts, and system accounts, with pagination support. On Jira Cloud, fields like email_address may be redacted due to privacy settings — never treat them as guaranteed present. Successful responses may silently omit users due to permission restrictions; a smaller-than-expected result set may reflect access limits, not absence of users.Input Parameters
start_at by max_results each request (or use next_start_at from the response); stop when has_next_page is false.has_next_page/next_start_at from the response to fetch subsequent pages.Output
Get Attachment
Get Attachment
Get Attachment Meta
Get Attachment Meta
Get Comment
Get Comment
Get Component
Get Component
JIRA_GET_COMPONENTSTool to retrieve components from Jira projects with search and filtering. Use when you need to list or find components across projects, optionally filtered by project IDs/keys or search query.Input Parameters
Output
Get Create Field Metadata for Issue Type
Get Create Field Metadata for Issue Type
JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDSTool to retrieve field metadata for a specific issue type in a project. Use this to discover required fields, allowed values, and field configurations before creating issues of a specific type.Input Parameters
Output
Get Current User
Get Current User
JIRA_GET_CURRENT_USERRetrieves detailed information about the currently authenticated Jira user. The returned accountId is the correct identifier for fields like lead_account_id in JIRA_CREATE_PROJECT, JIRA_ADD_WATCHER_TO_ISSUE, and JIRA_REMOVE_WATCHER_FROM_ISSUE — never use email or username in those fields.Input Parameters
Output
Get Dashboard Item Properties
Get Dashboard Item Properties
Get Dashboards
Get Dashboards
JIRA_GET_DASHBOARDSTool to list and search Jira dashboards visible to the current user. Use when you need to discover available dashboards, filter by ownership or favorites, or retrieve dashboard details including permissions and popularity.Input Parameters
Output
Get Favorite Filters
Get Favorite Filters
JIRA_GET_FAVORITE_FILTERSTool to retrieve favorite filters for the current user. Use when you need to discover which saved filters the user has marked as favorites.Input Parameters
Output
Get fields
Get fields
JIRA_GET_FIELDSRetrieves Jira issue field metadata to discover field IDs and names, with optional custom-field and project-scope filtering or creation fields for a project and issue type. Results depend on the authenticated user’s access.Input Parameters
Output
Get custom fields paginated
Get custom fields paginated
JIRA_GET_FIELDS_PAGINATEDTool to retrieve Jira fields in pages. Use when you need to filter or page through custom and system fields.Input Parameters
Output
Get Filter
Get Filter
JIRA_GET_FILTERRetrieves a specific Jira saved filter by ID, including its JQL and sharing metadata, to reuse in subsequent searches. Use when you need to fetch filter details or extract the JQL query to run searches.Input Parameters
Output
Get Group
Get Group
JIRA_GET_GROUPRetrieves details of a specific Jira group by name or ID. Use JIRA_GET_ALL_GROUPS to discover valid group names/IDs first. Some system-managed groups may be inaccessible due to permission restrictions even when name/ID is known.Input Parameters
Output
Get Service Management Info
Get Service Management Info
Get Issue
Get Issue
JIRA_GET_ISSUERetrieves a Jira issue by ID or key with customizable fields and expansions. Returned expanded sections are limited to changelog, renderedFields, names, schema, transitions, operations, editmeta, and versionedRepresentations when explicitly requested.Input Parameters
["summary", "status"].["jira.meta.data", "com.example.custom.info"].fields parameter are interpreted as field keys (e.g., ‘summary’) instead of field IDs (e.g., ‘customfield_10000’). Default is false (uses field IDs).Output
Get Issue Changelogs
Get Issue Changelogs
Get Create Issue Metadata (Deprecated)
Get Create Issue Metadata (Deprecated)
JIRA_GET_ISSUE_CREATE_METADATADEPRECATED: Use JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDS instead. This action wraps the deprecated query-based GET /issue/createmeta endpoint. Tool to retrieve issue creation metadata for Jira projects (available projects, issue types, and required fields).Input Parameters
Output
Get Issue Edit Meta
Get Issue Edit Meta
JIRA_GET_ISSUE_EDIT_METADATATool to retrieve editable fields for a Jira issue. Use before running an edit action to fetch custom field metadata and required fields.Input Parameters
Output
Get Issue Link Types
Get Issue Link Types
Get issue picker
Get issue picker
JIRA_GET_ISSUE_PICKER_SUGGESTIONSTool to get issue picker suggestions from Jira. Use when you need to search for issues and get auto-completion suggestions.Input Parameters
username and userkey cannot be used as search terms for this parameter, due to privacy reasons. Use accountId instead.currentIssueKey is a subtask, whether to include the parent issue in the suggestions if it matches the query.Output
Get Issue Property
Get Issue Property
Get Issue Resolutions
Get Issue Resolutions
Get Issue Type
Get Issue Type
Get issue types
Get issue types
JIRA_GET_ISSUE_TYPESRetrieves all Jira issue types available to the user using the modern API v3 endpoint; results vary based on ‘Administer Jira’ global or ‘Browse projects’ project permissions. Response includes two shapes: global issue types (no scope field) and project-scoped types (include scope.project.id); deduplicate by id, not name. Always use issuetype.id (not display name) when referencing issue types in other API calls to avoid validation errors.Output
Get Issue Watchers
Get Issue Watchers
JIRA_GET_ISSUE_WATCHERSRetrieves watcher information for a Jira issue, subject to Jira permissions. The returned watcher list may be absent or empty; when available, it can be filtered by account ID.Input Parameters
Output
Get Issue Worklogs (Deprecated)
Get Issue Worklogs (Deprecated)
JIRA_GET_ISSUE_WORKLOGSDEPRECATED: Use JIRA_GET_WORKLOG instead. This action is deprecated because it lacks the expand parameter for worklog properties. Use JIRA_GET_WORKLOG which provides the same functionality plus the ability to expand worklog properties using the ‘expand’ parameter. Legacy description: Retrieves worklogs for a Jira issue with user permission checks.Input Parameters
Output
Get JQL autocomplete reference data
Get JQL autocomplete reference data
Get JQL autocomplete suggestions
Get JQL autocomplete suggestions
JIRA_GET_JQL_AUTOCOMPLETEDATA_SUGGESTIONSTool to get JQL field auto-complete suggestions. Use when building JQL queries to discover valid field values or predicate options.Input Parameters
Output
Get My Permissions
Get My Permissions
JIRA_GET_MY_PERMISSIONSTool to retrieve the user’s permissions in Jira. Use when checking what actions the authenticated user can perform in a specific context (project, issue, or comment).Input Parameters
Output
Get User Locale Preference
Get User Locale Preference
Get Permissions
Get Permissions
Get Permitted Projects
Get Permitted Projects
JIRA_GET_PERMITTED_PROJECTSTool to retrieve projects where the current user has specific permissions. Use when you need to find which projects a user can access with certain permission levels.Input Parameters
Output
Get Project
Get Project
JIRA_GET_PROJECTRetrieves details of a Jira project by its ID or key.Input Parameters
Output
Get Project Permission Scheme
Get Project Permission Scheme
JIRA_GET_PROJECT_PERMISSION_SCHEMEReturn the permission scheme assigned to a Jira project.Input Parameters
Output
Get Project Roles
Get Project Roles
Get Project Templates
Get Project Templates
JIRA_GET_PROJECT_TEMPLATESLists project template keys from a fixed catalog, optionally filtered by project type. When a type is specified, it checks access to that project type; the catalog does not verify individual templates’ current availability.Input Parameters
Output
Get Project Type
Get Project Type
JIRA_GET_PROJECT_TYPERetrieves detailed information about a specific Jira project type by its key. Use when you need to get metadata about project types like software, service desk, business, or product discovery projects.Input Parameters
Output
Get Project Versions
Get Project Versions
JIRA_GET_PROJECT_VERSIONSRetrieves all versions for a Jira project with optional expansion. Use version IDs from the response (not names) when setting fixVersions or affectedVersions on issues — submitting names alone causes 400 validation errors.Input Parameters
Output
Get Recent Projects
Get Recent Projects
JIRA_GET_RECENT_PROJECTSRetrieves a list of projects recently accessed by the authenticated user.Input Parameters
Output
Get Issue Remote Links
Get Issue Remote Links
JIRA_GET_REMOTE_ISSUE_LINKSRetrieves links from a Jira issue to external resources.Input Parameters
Output
Get Server Info
Get Server Info
Get Service Desk Request Type Fields
Get Service Desk Request Type Fields
Get Sprint
Get Sprint
JIRA_GET_SPRINTRetrieves detailed information about a specific sprint by its ID. Use this action when you need to fetch a single sprint’s details directly by ID, such as checking sprint status, dates, goal, or metadata. For finding sprint IDs, use JIRA_LIST_SPRINTS first.Input Parameters
Output
Get System Avatars
Get System Avatars
JIRA_GET_SYSTEM_AVATARSTool to retrieve all system avatars for a specific type (issuetype, project, user, or priority). Use when you need to get a list of available default avatars that can be assigned to Jira entities.Input Parameters
Output
Get Transitions
Get Transitions
JIRA_GET_TRANSITIONSRetrieves available workflow transitions for a Jira issue. Always use the numeric id from the response when calling JIRA_TRANSITION_ISSUE — transition IDs are project/workflow-specific and must not be hardcoded or reused across different issues or projects. When multiple transitions share similar names, use id to disambiguate.Input Parameters
Output
Get Universal Avatar Type Owner
Get Universal Avatar Type Owner
JIRA_GET_UNIVERSAL_AVATAR_TYPE_OWNERTool to retrieve all avatars (system and custom) for a specific type and entity in Jira. Use when you need to view available avatar options for projects, issue types, or priorities.Input Parameters
Output
Get Universal Avatar View Type
Get Universal Avatar View Type
Get User Groups
Get User Groups
JIRA_GET_USER_GROUPSRetrieves all groups for a specific Jira user by account ID. Use this action when you need to check group membership for a particular user, verify permissions, or audit user access. Essential for understanding which groups a user belongs to before performing group-related operations.Input Parameters
Output
Get Avatar Image
Get Avatar Image
Get Issue Votes
Get Issue Votes
Get Worklogs
Get Worklogs
JIRA_GET_WORKLOGRetrieves worklogs for a specified Jira issue.Input Parameters
maxResults is 50, startAt=50 retrieves the second page.Output
Get Worklogs By IDs
Get Worklogs By IDs
List All Projects (Deprecated)
List All Projects (Deprecated)
JIRA_LIST_ALL_PROJECTSDEPRECATED: Use JIRA_GET_ALL_PROJECTS instead. Tool to list all projects accessible to the user. Wraps the deprecated GET /project endpoint; prefer the paginated JIRA_GET_ALL_PROJECTS (GET /project/search).Input Parameters
description (Returns the project description), issueTypes (Returns all issue types associated with the project), lead (Returns information about the project lead), projectKeys (Returns all project keys associated with the project).Output
List Assignable Users
List Assignable Users
JIRA_LIST_ASSIGNABLE_USERSSearch a page of users eligible for assignment in a Jira project or issue, optionally evaluating a workflow transition. Requires a project or issue context and a user query or account ID.Input Parameters
Output
List Boards
List Boards
JIRA_LIST_BOARDSRetrieves paginated Jira boards with filtering and sorting options. Use start_at and max_results together, looping through pages to retrieve all results.Input Parameters
Output
List Comments by IDs
List Comments by IDs
JIRA_LIST_COMMENTSTool to retrieve multiple comments by their IDs in a single request. Use when you need to fetch specific comments efficiently. Supports up to 1000 comment IDs per request with optional expansion for rendered HTML and properties.Input Parameters
Output
List Custom Field Context Default Values
List Custom Field Context Default Values
List Custom Field Context Issue Type Mappings
List Custom Field Context Issue Type Mappings
List Custom Field Context Options
List Custom Field Context Options
List Custom Field Context Project Mappings
List Custom Field Context Project Mappings
List Custom Field Contexts
List Custom Field Contexts
List Dashboard Gadgets
List Dashboard Gadgets
List Field Scheme Fields
List Field Scheme Fields
List Jira Filters
List Jira Filters
JIRA_LIST_FILTERSTool to search and list Jira saved filters (saved searches) visible to the current user. Use when you need to discover existing filters, find filters by name or owner, or get filter details including JQL queries and sharing permissions.Input Parameters
Output
List Group Members
List Group Members
JIRA_LIST_GROUP_MEMBERSReturn one page of users belonging to a Jira group.Input Parameters
Output
List Groups (Picker)
List Groups (Picker)
JIRA_LIST_GROUPS_PICKERTool to search and list groups using Jira’s picker endpoint. Use when you need to find groups by name or get a filtered list of groups.Input Parameters
Output
List Issue Comments
List Issue Comments
JIRA_LIST_ISSUE_COMMENTSRetrieves paginated comments from a Jira issue with optional ordering. Paginate by incrementing start_at by max_results until the cumulative count reaches the total field in the response. A response with total=0 and an empty comments array means the issue has no comments.Input Parameters
Output
List Issue Forms
List Issue Forms
List Issue Property Keys
List Issue Property Keys
List Project Types
List Project Types
List Sprints
List Sprints
JIRA_LIST_SPRINTSRetrieves paginated sprints from a Jira board with optional state filtering.Input Parameters
max_results each iteration; stop when response field isLast is true.Output
List Updated Worklogs
List Updated Worklogs
JIRA_LIST_UPDATED_WORKLOGSReturn one updated-worklog checkpoint page. Jira omits updates from the minute before each request, so delay the final checkpoint read by at least one minute before advancing a durable checkpoint.Input Parameters
Output
Move Issues to Sprint
Move Issues to Sprint
JIRA_MOVE_ISSUE_TO_SPRINTMoves one or more Jira issues to a specified active sprint.Input Parameters
Output
Parse JQL Queries
Parse JQL Queries
JIRA_PARSE_JQL_QUERIESParse and validate JQL queries, returning their abstract syntax tree structure along with any errors or warnings. Use when you need to validate JQL syntax or understand query structure before execution.Input Parameters
Output
Remove User from Group
Remove User from Group
JIRA_REMOVE_USER_FROM_GROUPRemoves a user from a Jira group. This is a destructive operation that revokes group-based permissions; confirm intent before calling.Input Parameters
Output
Remove User from Project Role
Remove User from Project Role
JIRA_REMOVE_USER_FROM_PROJECT_ROLERemoves a user or group from a project role.Input Parameters
Output
Remove Watcher from Issue
Remove Watcher from Issue
Search Approximate Count
Search Approximate Count
JIRA_SEARCH_APPROXIMATE_COUNTCount issues matching a JQL query using approximate count endpoint. Use when you need a fast count of issues without retrieving full issue details. The JQL query must be bounded (include at least one search restriction).Input Parameters
Output
Search Dashboards
Search Dashboards
JIRA_SEARCH_DASHBOARDSTool to search for Jira dashboards with filtering, sorting, and pagination support. Use when you need to find dashboards by name, owner, sharing permissions, or status. Supports filtering by owner account ID, group, project, and dashboard name.Input Parameters
Output
Search Issues Using JQL (GET)
Search Issues Using JQL (GET)
JIRA_SEARCH_FOR_ISSUES_USING_JQL_GETSearches Jira issues using JQL with token pagination and field selection. Results contain a defined set of issue details rather than arbitrary requested fields. Use the returned token to continue a search; a raw Jira token requires the original JQL.Input Parameters
next_page_token is not provided. Provide this parameter to start a search. To continue a paginated search with a raw Jira token, provide both the original JQL and next_page_token; tokens returned by this action already include that context. IMPORTANT: JQL must include at least one search restriction (filter condition such as project, status, assignee, issuetype, labels, created, updated, etc.). Unbounded queries containing only ORDER BY clauses (e.g., ‘order by created DESC’) are rejected by the API. Always include a filter like ‘project = X’ or ‘status = Open’. NOTE: This action uses Jira’s enhanced search API which has stricter JQL syntax requirements than the Jira UI.summary, customfield_10010, *all, *navigable). Defaults if omitted.Output
Search Issues Using JQL Enhanced (POST)
Search Issues Using JQL Enhanced (POST)
JIRA_SEARCH_FOR_ISSUES_USING_JQL_POSTDEPRECATED: Use JIRA_SEARCH_ISSUES instead. Searches for Jira Cloud issues using Enhanced JQL via POST request; supports eventual consistency and token-based pagination. Use this POST endpoint for long/complex JQL to avoid HTTP 414 errors on GET-based search. IMPORTANT: This action is for Jira Cloud only and will not work with Jira Server or Data Center instances.Input Parameters
Output
Search issues
Search issues
JIRA_SEARCH_ISSUESSearches Jira issues using structured filters or raw JQL, defaulting to issues updated in the last 30 days when no criteria are supplied. Results are paginated; when Jira omits a total, the reported total is the number of issues returned on the page.Input Parameters
Output
Send Notification for Issue
Send Notification for Issue
JIRA_SEND_NOTIFICATION_FOR_ISSUESends a customized email notification for a Jira issue.Input Parameters
NotificationRecipients object specifying who should receive the notification. At least one recipient category (e.g., reporter, assignee, a user, or a group) within this object must be configured.groups (if provided) AND permissions (if provided), AND also have general permission to view the issue.restrict is used, in which case it becomes mandatory. It is recommended to also provide text_body for email clients that do not support HTML.Output
Set Issue Property
Set Issue Property
Transition Issue
Transition Issue
JIRA_TRANSITION_ISSUETransitions a Jira issue to a different workflow state, with support for transition name lookup and user assignment by email. IMPORTANT: Only fields that are on the transition’s screen can be set during the transition. Which fields are available depends on the Jira workflow configuration and varies per project. Use JIRA_GET_TRANSITIONS with expand=‘transitions.fields’ to check which fields a transition supports. If a field (e.g., assignee) is not on the transition screen, use a JIRA_EDIT_ISSUE action after the transition to set other fields.Input Parameters
inline code (backticks), link text for hyperlinks, bullet lists (lines starting with -, *, or +), and numbered lists (lines starting with 1., 2., etc.). Example: ‘Fixed critical bug in user.login() method. See docs for details.’Output
Update Comment
Update Comment
JIRA_UPDATE_COMMENTUpdates an existing Jira comment by replacing its text content, with optional visibility restrictions.Input Parameters
visibility_value must also be specified. Valid values are ‘group’ or ‘role’.visibility_type is specified. For ‘group’ type, provide the group name (e.g., ‘jira-administrators’). For ‘role’ type, provide the project role name (e.g., ‘Administrators’).Output
Triggers
Comment Created
Comment Created
Comment Deleted
Comment Deleted
JIRA_COMMENT_DELETEDType: webhookTriggers when a comment is deleted from a Jira issue. The deleted comment’s text still arrives. Can deliver comments on issues the connected account cannot open in Jira itself.Configuration
Payload
Comment Updated
Comment Updated
JIRA_COMMENT_UPDATEDType: webhookTriggers when an existing comment on a Jira issue is edited. The payload carries the comment as it now reads, not what it said before. Can deliver comments on issues the connected account cannot open in Jira itself.Configuration
Payload
Issue Created
Issue Created
JIRA_ISSUE_CREATEDType: webhookTriggers when an issue is created in Jira, including a sub-task. Can deliver issues the connected account cannot open in Jira itself.Configuration
Payload
Issue Deleted
Issue Deleted
JIRA_ISSUE_DELETEDType: webhookTriggers when an issue is deleted from Jira. The deleted issue’s full field set still arrives, so the filters below apply to it as usual. Can deliver issues the connected account cannot open in Jira itself.Configuration
Payload
Issue Updated
Issue Updated
JIRA_ISSUE_UPDATEDType: webhookTriggers when a field on an existing issue changes — its status, assignee, or anything else on the issue. One edit can change several fields and arrives as one event; creating a sub-task also updates its parent. Commenting does not fire it. Can deliver issues the connected account cannot open in Jira itself.Configuration
Payload
Sprint Closed
Sprint Closed
JIRA_SPRINT_CLOSEDType: webhookTriggers when a sprint is completed and moves into the closed state.Configuration
Payload
Sprint Created
Sprint Created
JIRA_SPRINT_CREATEDType: webhookTriggers when a sprint is created on a Jira board. Creating a sprint does not start it — watch Sprint Started for that.Configuration
Payload
Sprint Started
Sprint Started
JIRA_SPRINT_STARTEDType: webhookTriggers when a sprint moves into the active state.Configuration
Payload
Sprint Updated
Sprint Updated
JIRA_SPRINT_UPDATEDType: webhookTriggers when a sprint’s name, goal, dates or state changes. Starting a sprint also fires this when the same call changed another field; closing one does not.Configuration
Payload
Version Created
Version Created
JIRA_VERSION_CREATEDType: webhookTriggers when a project version is created in Jira.Configuration
Payload
Version Deleted
Version Deleted
JIRA_VERSION_DELETEDType: webhookTriggers when a project version is deleted outright. A version that disappeared because it was merged into another one fires Version Merged instead.Configuration
Payload
Version Merged
Version Merged
JIRA_VERSION_MERGEDType: webhookTriggers when a project version is merged into another one, carrying both the version that went away and the one that survived.Configuration
Payload
Version Moved
Version Moved
JIRA_VERSION_MOVEDType: webhookTriggers when a project version is reordered within its project’s release list.Configuration
Payload
Version Released
Version Released
JIRA_VERSION_RELEASEDType: webhookTriggers when a project version is marked released.Configuration
Payload
Version Unreleased
Version Unreleased
JIRA_VERSION_UNRELEASEDType: webhookTriggers when a released project version is put back to unreleased.Configuration
Payload
Version Updated
Version Updated
JIRA_VERSION_UPDATEDType: webhookTriggers when a project version’s name, description or dates change. Releasing and un-releasing a version each fire this as well, alongside Version Released and Version Unreleased.
JIRA_COMMENT_CREATEDType: webhookTriggers when a comment is posted on a Jira issue. Can deliver comments on issues the connected account cannot open in Jira itself.Configuration
Payload