Shows whether Jira is connected, which Atlassian account is in use, the accessible sites and which one is selected. Call this first if any other tool reports NOT_CONNECTED.

Starts the Atlassian OAuth 2.0 login: opens the system browser for consent and returns the authorization URL. Waits up to waitSeconds for the user to approve; if they have not yet, the login keeps waiting in the background (5 minutes total) and you can call this tool again or jira_auth_status to check. Show the user the URL if the browser did not open.

Lists the Jira Cloud sites this account can use through this integration. Re-fetches from Atlassian.

Chooses the default Jira site for all tools (by cloud id, name, or URL). Persists across restarts.

Deletes the stored tokens so this machine is no longer authorized. Revoke the app at https://id.atlassian.com/manage-profile/apps to fully revoke access.

Returns the Atlassian account the integration acts as (accountId, name, email).

Lists Jira projects on the site, optionally filtered by a name/key substring.

Project details including its issue types (with hierarchy level and whether each is a sub-task type). Call before creating issues in an unfamiliar project.

Issue types available in a project (Epic, Feature, Story, Task, Bug, Sub-task...). hierarchyLevel: 1 = epic level, 0 = standard, -1 = sub-task.

Lists the fields (required and optional, with allowed values) for creating an issue of a given type in a project. Use when a create fails because of a missing required field, or to find custom field ids.

All fields on the site (system and custom) with ids, plus the detected Sprint / Story Points field ids. Filter with query.

Issue link types (e.g. Blocks: 'blocks' / 'is blocked by'). Use the phrases with jira_link_issues.

Priority names available on the site.

Finds Jira users by name or email. Pass projectKey to restrict to users assignable in that project. Returns accountIds for use as assignee.

Runs a JQL query and returns a compact list. Examples: 'project = THEOS AND statusCategory != Done ORDER BY updated DESC', 'assignee = currentUser() AND sprint in openSprints()', 'text ~ "vite migration"'. Use nextPageToken to continue.

Approximate count of issues matching a JQL query, without fetching them.

Full details of one issue: fields, description (as Markdown), parent, sub-tasks, links, and optionally recent comments.

Creates an issue of any type. For hierarchy use parentKey: stories/features/tasks under an Epic, or sub-tasks under a standard issue (jira_create_subtask picks the sub-task type for you). Description is Markdown. Returns the new key and URL.

Updates fields on an issue. Only provided fields change. labels replaces the whole set; use addLabels/removeLabels for incremental changes. Set parentKey to move an issue under a different Epic, or null to detach.

Assigns an issue to a user ('me', accountId, email or display name). Omit assignee or pass null/'unassigned' to unassign.

Workflow transitions currently available for an issue (name, target status, required fields). Use before jira_transition_issue if unsure of the names.

Moves an issue through its workflow. transition can be the transition name, the target status name (e.g. 'In Progress', 'Done'), or the transition id. Optionally adds a comment or sets a resolution.

Adds a comment (Markdown) to an issue as the connected user.

Latest comments on an issue, newest first, as Markdown.

Creates a link between two issues. Read it as ' ', e.g. fromKey=THEOS-10, linkType='blocks', toKey=THEOS-12, or linkType='is blocked by', 'relates to', 'duplicates', 'is caused by'. Use jira_get_link_types for the site's phrases.

Permanently deletes an issue. Irreversible; confirm with the user first.

Creates an Epic (the project's epic-level issue type is detected automatically). Then use jira_create_child_issue to add features/stories under it.

Creates a Feature, Story, Task or Bug under a parent Epic (parentKey). The project is taken from the parent. Use issueType='Feature' where the project has that type; call jira_get_issue_types if unsure.

Creates a sub-task under a standard issue (Feature, Story, Task, Bug). The sub-task issue type is detected automatically.

Creates an Epic and a batch of child issues (features/stories/tasks) under it, optionally with sub-tasks under each child, in one call. Fails fast on the first error and reports what was created.

Lists the direct children of an Epic (its features/stories/tasks) or the sub-tasks of a standard issue, with status and assignee.

Scrum/Kanban boards, optionally filtered by project key or name. Board ids are needed for sprint lookups.

Sprints for a board (by boardId) or for a project's scrum boards (by projectKey). Default state filter: active and future.

Issues in a sprint. sprint is an id, a name, 'active' or 'next' (the latter two need boardId or projectKey).

Moves up to 50 issues into a sprint. sprint is an id, a name, 'active' or 'next' (name/active/next need boardId or projectKey; projectKey defaults to the first issue's project).

Issues assigned to the connected user, newest activity first. Defaults to open issues only. Filter by project, status category, or recent updates.

Before creating a ticket, searches a project for existing issues matching a summary/keywords (text search on summary, description and comments). Returns likely duplicates so the user can decide whether to create a new one.

Creates a well-structured ticket from what was discussed: problem statement, context, reproduction steps, expected/actual behaviour, acceptance criteria, technical notes and links. Builds a consistently formatted description. Use jira_find_duplicate_ticket first when appropriate.