Jira
Issue and project tracking platform for projects, issues, sprints, workflows, comments, and releases.
Supports issue-tracking work across issues, comments, attachments, watchers, project events, and issue lifecycle changes.
Use Jira with Snow
Snow is a personal AI assistant that builds real apps for you, and they can put Jira to work.
What Snow can do with Jira
These are the Jira operations Snow and the apps you build with it can run. Sign in to choose which ones Snow may run without asking.
Reads69
Look at your data without changing it.
- 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.
- Get All Groups
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.
- 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.
- Get All Users
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.
- Get Attachment
Retrieves the binary content of a Jira attachment by ID. Use when you need to download a specific file attached to an issue.
- Get Attachment Meta
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.
- Get Component
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.
- Get Create Field Metadata for Issue Type
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.
- Get Current User
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.
- Get custom fields paginated
Tool to retrieve Jira fields in pages. Use when you need to filter or page through custom and system fields.
Creates11
Add something new to your account.
- Add Attachment
Uploads and attaches a file to a Jira issue.
- Add Comment
Adds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.
- Add Worklog
Tool to add a worklog entry to a Jira issue. Use when logging time spent on an issue.
- Bulk Create Issues
Creates multiple Jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
- Create Board
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 Group
Creates a new group in Jira with the specified name.
- 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.
- Create Project
Creates a new Jira project with required lead, template, and type configuration.
- Create Sprint
Creates a new sprint on a Jira board with optional start/end dates and goal.
- Create Version
Creates a new version for releases or milestones in a Jira project.
Updates10
Change something that is already there.
- Add User to Group
Adds a user to a Jira group.
- Add Users to Project Role
Adds users and optionally groups to a project role.
- 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.
- Assign Issue
Assigns a Jira issue to a user, default assignee, or unassigns; supports email/name lookup.
- 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.
- Move Issues to Sprint
Moves one or more Jira issues to a specified active sprint.
- Transition 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.
- Update Comment
Updates text content or visibility of an existing Jira comment.
- Remove Watcher from Issue
Removes a user from an issue's watcher list by account ID.
- Send Notification for Issue
Sends a customized email notification for a Jira issue.
Deletes7
Remove something. This often cannot be undone.
- Delete Issue
Permanently and irreversibly deletes a Jira issue by its ID or key. Obtain explicit user confirmation before calling.
- Remove User from Group
Removes a user from a Jira group. This is a destructive operation that revokes group-based permissions; confirm intent before calling.
- Remove User from Project Role
Removes a user or group from a project role.
- Delete Attachment
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.
- Delete Comment
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.
- Delete Version
Deletes a Jira version and optionally reassigns its issues.
- Delete Worklog
Deletes a worklog from a Jira issue with estimate adjustment options.
Triggers
These are the trigger events currently available for Jira.
- New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
- New Project
Triggered when a new project is added in Jira
- Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Related integrations
Ready to put Jira to work?
Sign up free, build an app by chatting, and connect Jira in minutes. No credit card required.