Search for JIRA issues using JQL (JIRA Query Language).

Returns a paginated result with total count. Use start_at to page through large result sets.

Args: jql: JQL query string (e.g., "project = PROJECT AND status = 'In Progress'") max_results: Maximum number of results to return (default: 50) start_at: Index of the first result (default: 0, for pagination)

Returns: Dict with issues array, total count, start_at, and max_results

Get detailed information about a specific JIRA issue including comments and links. Optionally include subtasks and available workflow transitions.

Args: issue_key: The JIRA issue key (e.g., "PROJECT-123") include_subtasks: Also fetch subtasks (extra API call) include_transitions: Also fetch available workflow transitions (extra API call)

Returns: Issue details with comments, links, and optionally subtasks/transitions

Creates a new issue in a specified Jira project. Requires project key, summary, description, and issue type. Optional fields include assignee, priority, labels, and custom fields.

On Cloud instances, pass an accountId string for assignee_name (not a username).

Args: project_key: Key of the project to create issue in (e.g., "PROJECT") summary: Issue summary description: Issue description issue_type_name: Type of the issue to create (e.g., "Bug", "Task") assignee_name: Assignee — accountId on Cloud, username on Server/DC (optional) priority_name: Name of the priority (optional) labels: List of labels to add to the issue (optional) custom_fields: Dictionary of custom fields to set (optional)

Returns: JSON object with the key of the new issue

Update fields on an existing JIRA issue. All field parameters are optional — only provided fields are updated. Optionally add a comment in the same call.

On Cloud instances, pass an accountId string for assignee (not a username).

Args: issue_key: The JIRA issue key (e.g., "PROJECT-123") summary: New summary (optional) description: New description (optional) assignee: New assignee — accountId on Cloud, username on Server/DC (optional) priority: New priority name (optional) labels: New labels list — replaces existing labels (optional) comment: Comment to add after update (optional) custom_fields: Dictionary of custom fields to update (optional)

Returns: Confirmation with issue key

Transition a JIRA issue to a new workflow state. Use jira_get_issue with include_transitions=True to see available transitions and their IDs.

Args: issue_key: The JIRA issue key (e.g., "PROJECT-123") transition_id: ID of the transition to execute (from jira_get_issue transitions) comment: Optional comment to add with the transition

Returns: Confirmation with issue key

Get metadata for creating issues — available issue types and their required/optional fields.

Call without issue_type to list available types. Call with issue_type to get field requirements.

Args: project_key: Project key (e.g., "OCPBUGS") issue_type: Issue type name (e.g., "Bug"). If omitted, lists available types.

Returns: Issue types list, or field details (name, required, allowed values) for one type