Jira Ticket Creator with Web Research

Create Jira tickets whose content is enriched by web search. Follow these phases in order.

Setup

Three environment variables are required:

• JIRA_BASE_URL — your Atlassian instance (e.g. https://yourteam.atlassian.net)
• JIRA_EMAIL — the email tied to your Atlassian account
• JIRA_API_TOKEN — an API token from https://id.atlassian.com/manage-profile/security/api-tokens

All Jira API calls use Basic auth via curl -u and force HTTP/1.1:

curl --http1.1 -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" -H "Content-Type: application/json" "$JIRA_BASE_URL/rest/api/3/..."

Phase 1 — Parse Arguments

Parse the user's request to extract:

If the user does not provide a project key, ask for it before proceeding.

Phase 2 — Web Research (if applicable)

If the user asked for research, or if the ticket would benefit from context (e.g. a bug report referencing an external API, a story about integrating a third-party service):

1. Use the web_search tool to search for the relevant topic.
2. Use the xurl tool or curl to fetch key pages for details.
3. Extract the most relevant information: error descriptions, API docs, best practices, version notes, or solution approaches.

Compile findings into a structured summary:

### Research Summary
- **Source**: [URL]
- **Key findings**: ...
- **Relevant details**: ...

If no research is needed, skip to Phase 3.

Phase 3 — Compose Ticket Content

Build the ticket description in Atlassian Document Format (ADF). Combine:

• The user's original request/context
• Research findings from Phase 2 (if any)
• Acceptance criteria (when creating Stories)
• Steps to reproduce (when creating Bugs)

Keep the description concise and actionable.

ADF Structure

Jira API v3 uses ADF for the description field. Minimal example:

{
  "type": "doc",
  "version": 1,
  "content": [
    {
      "type": "paragraph",
      "content": [{ "type": "text", "text": "Description text here." }]
    }
  ]
}

For richer formatting (headings, bullet lists, links):