Jira

Triggers3

Things that can wake up your Jira coworker.

• New Issue

  Triggered when a new issue is created in Jira

  JIRA_NEW_ISSUE_TRIGGER
• New Project

  Triggered when a new project is added in Jira

  JIRA_NEW_PROJECT_TRIGGER
• Updated Issue

  Triggered when an issue is updated in Jira

  JIRA_UPDATED_ISSUE_TRIGGER

Actions20

Things your coworker can do in Jira.

• Add Attachment

  Uploads and attaches a file to a Jira issue.

  JIRA_ADD_ATTACHMENT
• Add Comment

  Adds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.

  JIRA_ADD_COMMENT
• Add Users to Project Role

  Adds users and optionally groups to a project role.

  JIRA_ADD_USERS_TO_PROJECT_ROLE
• Add User to Group

  Adds a user to a Jira group.

  JIRA_ADD_USER_TO_GROUP
• Add Watcher to Issue

  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.

  JIRA_ADD_WATCHER_TO_ISSUE
• Add Worklog

  Tool to add a worklog entry to a Jira issue. Use when logging time spent on an issue.

  JIRA_ADD_WORKLOG
• Assign Issue

  Assigns a Jira issue to a user, default assignee, or unassigns; supports email/name lookup.

  JIRA_ASSIGN_ISSUE
• Bulk Create Issues

  Creates multiple Jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

  JIRA_BULK_CREATE_ISSUE
• Create Group

  Creates a new group in Jira with the specified name.

  JIRA_CREATE_GROUP
• Create Issue

  Creates a new Jira issue (e.g., bug, task, story) in a specified project. IMPORTANT: Different Jira projects may have custom required fields beyond the standard ones (summary, project_key, issue_type). If issue creation fails with 'field X is required', use JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDS (requires projectIdOrKey and issueTypeId parameters) to discover available fields for your project, or check your Jira project's configuration. Custom fields can be provided via the 'additional_properties' parameter as a JSON string (e.g., '{"customfield_12345": "value"}'). Rapid bulk creation may trigger HTTP 429 rate limiting; throttle calls and use exponential backoff on 429 responses.

  JIRA_CREATE_ISSUE
• Link Issues

  Links two Jira issues using a specified link type with optional comment.

  JIRA_CREATE_ISSUE_LINK
• Create Project

  Creates a new Jira project with required lead, template, and type configuration.

  JIRA_CREATE_PROJECT
• Create Sprint

  Creates a new sprint on a Jira board with optional start/end dates and goal.

  JIRA_CREATE_SPRINT
• Create Version

  Creates a new version for releases or milestones in a Jira project.

  JIRA_CREATE_VERSION
• Delete Issue

  Permanently and irreversibly deletes a Jira issue by its ID or key. Obtain explicit user confirmation before calling.

  JIRA_DELETE_ISSUE
• Edit Issue

  Updates an existing Jira issue with field values and operations. Supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. Direct parameters take precedence.

  JIRA_EDIT_ISSUE
• Bulk Fetch 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.

  JIRA_FETCH_BULK_ISSUES
• Find Users (Deprecated)

  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.

  JIRA_FIND_USERS
• Get All Groups

  Retrieves all groups from the Jira instance with pagination support. 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. On large instances, omitting both pagination parameters to fetch all groups can be expensive; prefer targeted lookups with max_results and start_at when possible.

  JIRA_GET_ALL_GROUPS
• Get all projects

  Retrieves all visible projects using the modern paginated Jira API with server-side filtering and pagination support. Results reflect only projects the authenticated user can access — small or empty result sets may indicate permission restrictions, not absence of projects. An empty `values` array means no projects matched the filters; relax `query`, `status`, or `categoryId` if unexpected. Project keys are mutable; prefer the stable numeric project ID for durable references in follow-up calls.

  JIRA_GET_ALL_PROJECTS