create-jira-tickets
- Visibility
- public
- Deploys
- 0
- Build Number
- f49ce6a2
- Updated
- Jun 23, 2026
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
- If a Slack thread URL is detected, the agent fetches the thread messages via the Slack API
- GPT-4o mini generates a concise ticket title (max 100 chars) and a detailed description
- The ticket is created in Jira as a
Taskunder the configured project - 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
| Variable | Description |
|---|---|
OPENAI_API_KEY | Auto-injected by Astropods |
JIRA_API_KEY | Jira API token — from Atlassian account security settings |
JIRA_USERNAME | Jira account email address |
JIRA_SUBDOMAIN | Subdomain for your Atlassian instance (e.g. mycompany) — alphanumeric and hyphens only |
JIRA_PROJECT_ID | Jira 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
Tasktype 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.
- Visibility
- public
- Deploys
- 0
- Build Number
- f49ce6a2
- Updated
- Jun 23, 2026