Returns the Jira user identity associated with the configured credentials (GET /rest/api/2/myself).

Returns Jira Data Center deployment info: version, deployment type, and build number (GET /rest/api/2/serverInfo).

Runs a JQL query and returns matching issues (GET /rest/api/2/search) with key, summary, status, assignee, reporter, created, and updated.

Fetches full details for a single issue (GET /rest/api/2/issue/{key}): summary, description, status, comments, labels, and assignee.

Confluence access: linked Confluence pages are NOT part of an issue's fields and are never returned here. In Jira Data Center they are stored as REMOTE LINKS. To read the Confluence content associated with an issue, an agent should:

1. Call get_issue_remote_links with the same issueKey to list linked Confluence pages (each entry has a url like .../pages/viewpage.action?pageId=).

2. Extract the numeric pageId from that url (the pageId= query parameter).

3. Call confluence_get_page with that pageId and format: "view" to get readable, server-rendered content (use format: "storage" for the raw source). These Confluence tools are available when CONFLUENCE_BASE_URL is configured. Alternatively, use confluence_search with a CQL query such as text ~ "<ISSUE-KEY>" to find pages that mention the issue.

Creates a new Jira issue (POST /rest/api/2/issue) and returns the created issue key.

Adds a comment to an issue (POST /rest/api/2/issue/{key}/comment).

Moves an issue through its workflow (POST /rest/api/2/issue/{key}/transitions). Use get_transitions first to discover valid transitionId values.

Lists all Jira projects visible to the authenticated user (GET /rest/api/2/project).

Lists the workflow transitions currently available for an issue (GET /rest/api/2/issue/{key}/transitions).

Lists all comments on an issue (GET /rest/api/2/issue/{key}/comment).

Lists an issue's remote links (GET /rest/api/2/issue/{key}/remotelink), including linked Confluence pages ('Wiki Page' links) and generic web links.

Runs an arbitrary JQL query (GET /rest/api/2/search) and returns raw issue data for the requested fields. Use this for ad-hoc reporting when search_issues' fixed field set isn't enough.

Turns workshop notes or Fit/Gap analysis text into properly structured Jira Stories, Tasks, and Bugs, then creates them in the given project. If items is provided, those pre-structured items are created as-is (recommended when the calling agent has already analyzed the notes). Otherwise, notes is parsed heuristically: lines tagged 'Story:'/'Task:'/'Bug:', 'As a ... I want ... so that ...' phrasing (-> Story), and bullet/numbered lines (-> Task) are detected automatically. Use dryRun to preview extracted items before creating anything in Jira.