Comment Created
Triggers when a comment is posted on a Jira issue. Can deliver comments on issues the connected account cannot open in Jira itself.
A tool for bug tracking, issue tracking, and agile project management.
Triggers when a comment is posted on a Jira issue. Can deliver comments on issues the connected account cannot open in Jira itself.
Triggers 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.
Triggers 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.
Triggers when an issue is created in Jira, including a sub-task. Can deliver issues the connected account cannot open in Jira itself.
Triggers 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.
Triggers 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.
Triggers when a sprint is completed and moves into the closed state.
Triggers when a sprint is created on a Jira board. Creating a sprint does not start it — watch Sprint Started for that.
Triggers when a sprint moves into the active state.
Triggers 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.
Triggers when a project version is created in Jira.
Triggers when a project version is deleted outright. A version that disappeared because it was merged into another one fires Version Merged instead.
Triggers when a project version is merged into another one, carrying both the version that went away and the one that survived.
Triggers when a project version is reordered within its project's release list.
Triggers when a project version is marked released.
Triggers when a released project version is put back to unreleased.
Triggers 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.
Uploads and attaches a file to a Jira issue.
Adds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.
Adds 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.
Adds a user to a Jira group.
Adds 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.
Adds 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.
Adds 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.
Analyses 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.
Assign one or more Jira projects to a custom field context.
Assigns a Jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Creates multiple Jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Fetch one cursor-paginated page of changelogs for up to 1,000 issues.
Tool 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.
Submits an asynchronous bulk move of Jira issues using destination project, issue type, and optional parent mappings. Returns a task ID for tracking progress.
Check 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.
Creates 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.
Create a component in a Jira project.
Create a Jira custom issue field and return its metadata.
Create a project and issue-type context for a Jira custom field.
Create selectable options in a Jira custom field context.
Create a Jira saved filter with a required name and optional JQL query.
Creates a new group in Jira with the specified name.
Creates 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.
Create a Jira issue link type.
Create a global Jira issue type.
Attach an external object to a Jira issue, creating or replacing by global ID.
Creates a new Jira project with required lead, template, and type configuration.
Create a Jira screen with a default field tab.
Create a Jira screen scheme with optional operation-specific screens.
Create a JSM customer request with field values and optional form answers.
Creates a new sprint on a Jira board with optional start/end dates and goal.
Creates a new version for releases or milestones in a Jira project.
Permanently deletes an attachment from Jira by its ID. This action is irreversible — the attachment cannot be recovered once removed. Use this action when you need to remove an unwanted file from a Jira issue.
Deletes a specific comment from a Jira issue using its ID and the issue's ID/key; requires user permission to delete comments on the issue.
Permanently deletes a Jira issue by ID or key, optionally deleting its subtasks as well. Obtain explicit user confirmation before calling.
Permanently delete one form attached to a Jira issue.
Permanently deletes a link between two Jira issues by link identifier.
Permanently delete a globally shared Jira project role.
Deletes one to fifty Jira workflow statuses by identifier.
Deletes a Jira version and optionally reassigns its issues.
Deletes a worklog from a Jira issue with estimate adjustment options.
Updates 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.
Tool 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.
DEPRECATED: 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.
Searches 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.
Find users for picker components by matching query against user attributes like display name and email.
Find users who hold every requested permission for a Jira issue or project.
Retrieves 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.
Retrieves all Jira issue type schemes with optional filtering and pagination.
Retrieves 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.
Retrieves 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.
Retrieves the binary content of a Jira attachment by ID. Use when you need to download a specific file attached to an issue.
Tool to retrieve Jira attachment settings including upload limits and enabled status. Use when you need to check if attachments are enabled or determine the maximum file size allowed.
Tool to retrieve a specific avatar image by type and ID from Jira. Use when you need to download avatar images for projects, issue types, or priorities.
Return one Jira board's identity, type, location, and visibility details. OAuth connections need the non-default read:issue-details:jira scope.
Return columns, filter, location, and ranking, plus type-specific settings.
Retrieve status and progress for one asynchronous Jira bulk operation.
Retrieves a specific comment by ID from a Jira issue with optional expansions.
Tool 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.
Tool 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.
DEPRECATED: 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).
Retrieves 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.
Tool to retrieve Jira fields in pages. Use when you need to filter or page through custom and system fields.
List property keys for a dashboard item or retrieve one property's value.
Tool 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.
Tool to retrieve favorite filters for the current user. Use when you need to discover which saved filters the user has marked as favorites.
Retrieves 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.
Retrieves 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.
Retrieves 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.
Retrieves 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.
Return one oldest-first page of an issue's complete change history.
Tool to retrieve editable fields for a Jira issue. Use before running an edit action to fetch custom field metadata and required fields.
Retrieve one complete form attached to a Jira issue.
Retrieve one Jira issue relationship by link ID.
Retrieve one configured Jira issue link type by ID.
Retrieves all configured issue link types from Jira.
Tool to get issue picker suggestions from Jira. Use when you need to search for issues and get auto-completion suggestions.
Retrieves a custom property from a Jira issue by key.
Retrieves links from a Jira issue to external resources.
Retrieves Jira issue resolution types. The preferred search endpoint returns a single page, so the result may not include every available resolution.
Retrieves all issue statuses associated with workflows from Jira. Returns global statuses that may not be valid for every project or workflow scheme; verify a returned status is applicable to the specific project before use.
Retrieves one Jira issue type by its unique ID.
Retrieves 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.
Fetches voting details for a Jira issue; requires voting to be enabled in Jira's general settings.
Retrieves 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.
DEPRECATED: 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.
Retrieves JQL autocomplete reference data including reserved words, field names, and function names. Use when building JQL query editors or validating JQL syntax.
Tool to retrieve JQL autocomplete reference data. Use when you need to discover available JQL fields, functions, and reserved words for building queries.
Tool to get JQL field auto-complete suggestions. Use when building JQL queries to discover valid field values or predicate options.
Tool 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).
Return one Jira permission scheme by ID.
Tool to retrieve all available Jira permissions. Use when you need to list all permission types that exist in Jira, including project and global permissions.
Tool 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.
Retrieves details of a Jira project by its ID or key.
Return the notification scheme assigned to a Jira project.
Return the permission scheme assigned to a Jira project.
Retrieves all available roles for a Jira project. Role IDs are project-specific and must not be reused across projects; call this action per project to obtain correct role IDs.
Lists 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.
Retrieves 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.
Retrieves 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.
Return workflow-scheme associations for Jira projects.
Retrieves a list of projects recently accessed by the authenticated user.
Retrieve one page of approvals for a Jira Service Management request.
Tool to retrieve Jira instance server information. Use when you need details about the Jira version, build, deployment type, or server configuration.
Tool to retrieve JSM request type field metadata for filling out portal requests. Use when you need to know which fields are required and their valid values.
Retrieves runtime information for the Jira Service Management instance. Use when you need to check the version, build date, or license status.
Retrieves 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.
Tool 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.
Retrieves 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.
Tool 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.
Tool to retrieve the default avatar image for a specific type (project, issuetype, or priority) from Jira. Use when you need to download the default avatar for a type.
Retrieve one privacy-filtered Jira user directly by account ID.
Retrieves 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.
Tool to retrieve the locale preference of the currently authenticated Jira user. Use when you need to know the user's language and regional settings.
Retrieves one Jira project version directly by its unique ID.
Retrieves worklogs for a specified Jira issue.
Retrieve full worklog records for a list of Jira worklog IDs.
Links two Jira issues using a specified link type with optional comment.
DEPRECATED: 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).
Search 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.
Return one page of quick filters configured on a Jira board.
Retrieves paginated Jira boards with filtering and sorting options. Use `start_at` and `max_results` together, looping through pages to retrieve all results.
Tool 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.
Return one page of custom field defaults grouped by context and issue type.
Return one page of issue type mappings for a Jira custom field's contexts.
Return one page of options configured for a custom field context.
Return one page of project mappings for a Jira custom field's contexts.
Return one page of contexts for a Jira custom field.
Lists gadgets on a Jira dashboard, optionally filtered by type, URI, or ID.
Return fields from Jira's deprecated company-managed field configuration API.
List projects associated with a custom field via Jira's experimental endpoint.
List fields via an experimental endpoint requiring Jira field-schemes beta enrollment.
Return one page of users belonging to a Jira group.
Tool 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.
Retrieves 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.
List basic metadata for forms attached to a Jira issue.
Lists the keys and URLs of properties defined on a Jira issue.
Return mappings for schemes used in company-managed Jira projects.
Tool 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.
Return one filtered page of Jira issue priorities.
Return issue type schemes assigned to selected Jira projects.
Retrieves all Jira project types available in the instance. Use when you need to discover available project types or list all types without filtering by a specific key.
Lists one filtered and ordered page of versions in a Jira project.
Return one filterable page of Jira screen schemes.
Return the fields configured on one Jira screen tab.
List the tabs configured on one Jira screen.
Return one filterable page of Jira screens and their metadata.
Return one page of customers attached to a Jira service desk.
Return one filtered page of request types in a service desk.
List service desks available to the connected Jira user.
Retrieves paginated sprints from a Jira board with optional state filtering.
Return 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.
Moves one or more Jira issues to a specified active sprint.
Parse 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.
Remove a specified Jira field from a screen tab.
Removes a user from a Jira group. This is a destructive operation that revokes group-based permissions; confirm intent before calling.
Removes a user or group from a project role.
Removes a user from an issue's watcher list by account ID.
Count 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).
Tool 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.
Searches 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.
Searches 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.
DEPRECATED: 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.
Sends a customized email notification for a Jira issue.
Sets a named JSON property on a Jira issue.
Transitions 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.
Updates an existing Jira comment by replacing its text content, with optional visibility restrictions.
Partially updates a sprint without clearing omitted fields. Changing state from future to active starts the sprint and requires start_date and end_date (on the sprint or in this request); changing active to closed completes the sprint, which cannot be reopened.
Update release metadata for an existing Jira project version.
Validate a proposed bulk workflow update without changing Jira workflows.
Returns Jira connection identity information. For bearer connections, it lists accessible Atlassian sites; for non-bearer connections, it returns the configured site URL and the authenticated user's account ID and display name when available.
The Jira integration connects your Dench AI CRM directly to Jira, so agents can read and act on your Jira data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
171 actions are available for agents to invoke on your behalf, and 17 triggers can start a Dench automation the moment something changes in Jira. Every call runs through Jira's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Jira and click Connect — you'll authorize access through Jira's own sign-in flow. No API keys or code required.
Ask an agent to use Jira in chat, or wire a Jira trigger into an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Jira integration connects your AI CRM to Jira, so AI agents can work with your Jira data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Jira integration currently exposes 171 actions, including Add Attachment, Add Comment, Add Field to Screen Tab, Add User to Group, Add Users to Project Role, and Add Watcher to Issue. Agents invoke them on your behalf from chat or from automations.
Yes. The Jira integration provides 17 triggers — such as Comment Created, Comment Deleted, Comment Updated, and Issue Created — that can start a Dench automation the moment something happens in Jira.
No. You connect Jira from your Dench workspace using Jira's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Jira's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Jira connection from your workspace settings at any time.