Jira Integration
SkillSearchAdds a jira skill so your agent can search tickets, track sprints, and summarize project analytics.
Use Jira Integration in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Jira Integration and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Jira Integration skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
About this skill
Search and analyze Jira tickets, sprints, and project analytics. Use this skill when the user asks about tickets, bugs, sprint tracking, or engineering work.
What this skill tells your AI
The instructions your AI receives, as published by builderio/agent-native in templates/analytics/.builder/skills/jira/SKILL.md and read by ahel’s review.
Connection
- Base URL:
$JIRA_BASE_URL(e.g.https://yourorg.atlassian.net) - Auth: Basic auth —
Base64($JIRA_USER_EMAIL:$JIRA_API_TOKEN) - Env vars:
JIRA_BASE_URL,JIRA_USER_EMAIL,JIRA_API_TOKEN - Caching: 10-minute in-memory cache, max 100 entries
- API versions: REST API v3 (
/rest/api/3), Agile API (/rest/agile/1.0)
Server Lib & API Routes
- File:
server/lib/jira.ts
Exported Functions
| Function | Description |
|---|---|
searchIssues(jql, fields?, maxResults?) | Search via JQL |
getIssue(issueKey) | Get single issue detail |
getProjects() | List all projects |
getStatuses(projectKey?) | List statuses (optionally by project) |
getBoards() | List agile boards |
getSprints(boardId) | List sprints for a board |
getAnalytics(projects, days) | Aggregate ticket analytics |
API Routes
| Route | Description |
|---|---|
GET /api/jira/search | Search tickets via JQL |
GET /api/jira/issue | Get issue detail |
GET /api/jira/projects | List projects |
GET /api/jira/statuses | List statuses |
GET /api/jira/boards | List boards |
GET /api/jira/sprints | List sprints |
GET /api/jira/analytics | Ticket analytics |
Dashboard
/adhoc/jira— Jira Tickets dashboard with Overview, Search, and Sprints tabs
Script Usage
# Search tickets
pnpm action jira-search --jql="summary ~ SSO ORDER BY created DESC" --fields=key,summary,status,assignee
# Ticket analytics
pnpm action jira-analytics --days=30
pnpm action jira-analytics --projects=ENG,PROD --days=30
Key Patterns & Gotchas
- IMPORTANT: The old
/rest/api/3/searchendpoint was removed by Atlassian (returns 410). Must use/rest/api/3/search/jqlinstead. - JQL for duplicate detection:
project = X AND summary ~ "keyword" ORDER BY created DESC - Always use markdown links for tickets:
[ENG-1234](https://yourorg.atlassian.net/browse/ENG-1234) getStatuseswith a projectKey returns an array of issue type entries; the code flattens nested statusesgetAnalyticsruns multiple search queries and aggregates client-side
Signals
- GitHub stars
- 7k
- Forks
- 635
- Last commit
- Oct 2026
ahel review
S4info
community integration, published by builderio, not jira
Automated review, not a security audit. Ruleset v1+k2.
Advanced
- Item type
- skill
- Key
jira- Source
- github.com/builderio/agent-native
github.com/builderio/agent-native