Jira
Read and write Jira issues, sprints, boards, and JQL queries from any myai canvas, function, or chat.
Jira is the issue tracker most enterprise engineering teams have standardized on. The data sitting in Jira — issues, sprints, boards, custom workflow state — drives the day-to-day work but historically requires the Jira UI to actually query. The integration treats Jira as a live data source: JQL queries from chat, sprint state in canvases, issue writes from automations, all without leaving the conversation.
What you can do
- Run JQL queries from a chat — "show me all unresolved bugs assigned to the platform team this sprint" returns a structured table inline.
- Issue CRUD and workflow transitions — automations can create issues, comment, assign, or transition through your custom workflow.
- Sprint and backlog visibility — sprint progress, capacity, burndown signals surfaced alongside business metrics.
- Board and epic tracking — read epic progress for the cross-team rollup view that doesn't quite exist natively.
- Comment and changelog history — for the workflows where "what happened on this issue over time" matters.
- User and project lookups — for assignee routing and project-aware automation.
How to connect
API token authentication via HTTP Basic Auth with your Atlassian email + token. Generate the token at id.atlassian.com, then provide both to the integration.
The token is sent as Authorization: Basic base64(email:api_token). Scope mirrors the user's Jira permissions — grant only what the workflows need.
Common use cases
- Sprint kickoff digest — function pulls the sprint's full issue list, summarizes by priority and owner, posts to the team's chat each Monday.
- Stuck-issue triage — recurring function flags issues that haven't moved in N days; routes to the right lead via Teams.
- Customer-to-Jira automation — incoming customer-success signal creates a matching Jira issue in the right project with full context attached.
Reference
- Connection model: Atlassian API token (HTTP Basic auth, base64-encoded email:token)
- Scope: ~16 operations across issues, sprints, boards, JQL, comments, workflow transitions
- Permissions mirror Atlassian user role — no separate ACL system