Log inGet started
All blueprints
create-jira-tickets

astropods-org/create-jira-tickets 

Turns a problem description or a Slack thread URL into a Jira ticket in seconds using GPT-4o mini.

Deploy this blueprint
Copy a prompt to use in Claude Code, Codex, or Cursor.
Repository
astropods/agents/slack-jira-agent
Contributors
Rodric Rabbah
Rodric Rabbah@rrabbah
Integrations
OpenAISlackJira
More blueprints
coworker

coworker

6 deploys•simon

daily-customer-briefs

daily-customer-briefs

0 deploys•astropods-org

github-issue-scorer

github-issue-scorer

1 deploy•astropods-org

AGENT.md

Slack to Jira Agent

The bug is sitting in a Slack thread and nobody has filed a ticket yet. Slack to Jira Agent takes a problem description — typed directly, pasted from a conversation, or provided as a Slack thread URL — and turns it into a properly formatted Jira task in seconds. Works from the web playground or directly in Slack via the Slack adapter.

Usage

Send a message in one of two ways:

Plain-text description — describe the problem directly:

  • "Login button broken on mobile Safari — users get a 403 after OAuth redirect"
  • "Checkout flow crashes when applying a discount code on the order summary page"

Slack thread URL — paste a thread link to create a ticket from the actual conversation (requires SLACK_BOT_TOKEN):

  • https://myworkspace.slack.com/archives/C01234/p1234567890123456

What happens

  1. If a Slack thread URL is detected, the agent fetches the thread messages via the Slack API
  2. GPT-4o mini generates a concise ticket title (max 100 chars) and a detailed description
  3. The ticket is created in Jira as a Task under the configured project
  4. The agent returns the direct link to the created ticket

Slack integration

The agent supports both the web and Slack adapters. Enable the Slack adapter at deploy time and your team can create Jira tickets directly from any Slack channel by messaging the bot — no copy-pasting into a web form.

Environment variables

VariableDescription
OPENAI_API_KEYAuto-injected by Astropods
JIRA_API_KEYJira API token — from Atlassian account security settings
JIRA_USERNAMEJira account email address
JIRA_SUBDOMAINSubdomain for your Atlassian instance (e.g. mycompany) — alphanumeric and hyphens only
JIRA_PROJECT_IDJira project key (e.g. PROJ)
SLACK_BOT_TOKEN(Optional) Slack Bot token (xoxb-…) — required only when pasting a Slack thread URL; needs channels:history scope

Limitations

  • Creates tickets as Task type only; issue type is not configurable at runtime.
  • Jira description is plain text (ADF paragraph); rich formatting is not preserved.
  • Ticket quality depends on the detail in the description — the more context provided, the better the generated content.