Jira

This action allows users to upload a file and attach it to a specific Jira issue. It supports various file formats and ensures that the attachment is associated with the correct issue key.

This action adds a rich comment to a specific Jira issue, allowing Markdown formatting. Users can specify visibility restrictions for the comment if needed.

This action adds one or more users (and optionally groups) to a specific project role in Jira. Users are identified by their Atlassian account IDs, and roles are identified by their role ID.

This action adds a user to a Jira group. The user is identified by their Atlassian account ID, and the group is identified by either its name or ID.

This action adds a specified user as a watcher to a Jira issue. A watcher receives notifications about updates to the issue.

Add a worklog entry to a Jira issue to track time spent. You can specify the time worked, when it started, an optional comment, and visibility restrictions.

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.

This action assigns a specified Jira issue to the designated user or the project's default assignee. It also allows for unassigning the issue by not providing an account ID and supports lookup by username or email.

This action creates multiple Jira issues in a single API call. It allows for bulk creation of issues with various attributes, such as assignee and priority, streamlining the issue management process.

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.

This action creates a new group in Jira. Groups are used to organize users and manage permissions across projects and issues.

Creates a new issue in a specified Jira project. This includes setting parameters such as the issue type, summary, and assignee details. Note: Some projects may have custom required fields - use JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDS (requires projectIdOrKey and issueTypeId) to discover them if needed.

This action links two Jira issues based on the specified relationship type. It allows users to track dependencies and relationships between issues within their projects.

Retrieves JQL autocomplete reference data including reserved words, field names, and function names. Use when building JQL query editors or validating JQL syntax.

This action creates a new Jira project with the necessary configurations. It requires information such as the project key, name, type, and template to successfully set up a project in Jira.

This action allows the creation of a new sprint within a specified Jira board. Users can set optional start and end dates, as well as define a primary goal for the sprint.

This action creates a new version within a specified Jira project, allowing users to manage project milestones effectively. It includes attributes such as name, description, and release dates that provide context to the version being created.

This action permanently deletes a specified attachment from Jira. It requires the attachment ID to perform the delete operation.

This action deletes a specified comment from a Jira issue. It requires the issue ID or key along with the comment ID to perform the delete operation.

This action deletes a specified Jira issue. It can also delete any associated subtasks if requested.

This action deletes a specified version in Jira. It can also optionally move issues associated with the deleted version to another specified version.

This action deletes a specific worklog entry from a Jira issue. It provides options to notify users and adjust the issue's remaining estimate as needed.

Updates a specified Jira issue by changing its fields or adding new information. This action allows users to modify attributes such as the summary, description, and assignee of the issue.

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.

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.

This action allows you to search for Jira users using various parameters like email or display name. It returns a list of users that match the search criteria for further operations.

Tool to find users in Jira by query string, account ID, or property search. Use when you need to search for users to assign to issues, add as watchers, or perform other user-related operations.

Find users for picker components by matching query against user attributes like display name and email.

This action retrieves a single page of groups from the Jira instance. Use `start_at` and `max_results` to page through results; the response includes `has_next_page` and `next_start_at` to drive pagination.

This action retrieves a list of all issue type schemes from Jira. It allows for optional filtering based on specific IDs and supports pagination for large sets of data.

Retrieves a list of all projects that the user has visibility over. This action allows filtering, sorting, and pagination of project results based on specified criteria.

This action retrieves issue statuses that are associated with workflows in Jira. It provides detailed information about each status including name, description, and category. Note: This may not include statuses from team-managed (Next-Gen) projects or unused statuses.

This action retrieves a single page of users from the Jira instance. Use `start_at` and `max_results` to page through results; the response includes `has_next_page` and `next_start_at` to drive pagination.

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.

This action fetches a specific comment from a Jira issue by its ID. You can specify optional parameters to expand additional information in the response.

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.

This action retrieves detailed information about the currently authenticated Jira user. It provides data such as the user's display name, email address, groups, and application roles.

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 metadata for Jira issue fields so you can identify custom field IDs before editing an issue.

Tool to retrieve Jira fields in pages. Use when you need to filter or page through custom and system fields.

This action retrieves a specific Jira saved filter using its ID. It returns the filter's JQL query, owner, sharing permissions, and other metadata. This enables a workflow pattern: (1) list/search filters, (2) get filter details including JQL, (3) use that JQL with JIRA_SEARCH_* actions to retrieve matching issues.

This action retrieves information about a specific Jira group. You can fetch the group by its name or unique ID, and optionally expand to include the list of users in the group.

Retrieves runtime information for the Jira Service Management instance. Use when you need to check the version, build date, or license status.

This action retrieves a specific Jira issue using its ID or key. Users can customize the fields and additional data included in the response to suit their specific needs.

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).

Tool to retrieve editable fields for a Jira issue. Use before running an edit action to fetch custom field metadata and required fields.

This action retrieves all issue link types configured in the Jira instance. It provides a comprehensive list of the relationships available for issues in your project.

Retrieves issue picker suggestions from Jira for auto-completion when searching for issues.

This action retrieves a specific property associated with a Jira issue using its ID or key. It allows users to access custom information stored in Jira properties.

This action fetches all issue resolutions available in Jira. It retrieves resolution types such as 'Done' or 'Fixed' that can be applied to issues.

Retrieves a list of all available Jira issue types for the user. This action allows access to Jira's issue type details that can be utilized within the application.

This action retrieves the list of users watching a specific Jira issue. It allows clients to understand who is interested in updates for that issue.

Retrieves all worklogs associated with a specific Jira issue. This includes filtering options such as start dates and pagination for large sets of worklogs.

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).