Integration

Fleet + Jira: Native Jira Cloud Polling That Triggers Agents

Name: Fleet
Author: Fleet

Jira is a native Fleet work-item provider. Fleet's Jira adapter calls the Jira Cloud REST v3 search API on your site, authenticating with an Atlassian API token plus your account email as HTTP basic auth (Atlassian's documented pattern — the token is the basic-auth password, not a bearer token). It polls the configured project for issues updated since the last cursor and normalizes each one into Fleet's common WorkItem shape (summary, status, labels, assignee, URL).

Trigger rules then match over those normalized fields to start a pipeline or dispatch a single agent — the same poll → trigger-rule → agent/pipeline flow as the Linear provider. Jira is configured through the Fleet dashboard, not .fleet/config.yaml: provider type jira, the site URL, project key, and account email are stored in the dashboard, and the API token is fetched at fleet watcher start via FetchIntegrationConfig. The default poll interval is five minutes.

Setup

1

Install Fleet and initialize your repo

curl -fsSL https://fleetctl.ai/install | sh
fleet init

2

Add the Jira integration in the Fleet dashboard

# Dashboard → Integrations → Jira
# type: jira
# site: https://<your-org>.atlassian.net
# proj_key: <KEY, e.g. PROJ>
# email: <your Atlassian account email>
# + Atlassian API token (stored server-side)

3

Define a trigger rule (status/label/assignee → start_pipeline or agent) in the dashboard

# e.g. provider: jira, condition: status equals "Ready for Dev" → start agent backend-developer

4

Start the watcher — it fetches the Jira config and begins polling

fleet watcher start

What you gain

Jira Cloud issues are a first-class work-item source via the REST v3 search API — no middleware needed
Trigger rules over status, labels, or assignee dispatch the right agent or pipeline directly from Jira ticket changes
Auth uses a standard Atlassian API token + email basic auth; config lives in the dashboard and the token is fetched at watcher start

Honest limits

Jira is a polling provider (default five-minute interval), not webhook-driven
Jira descriptions can be ADF JSON; the adapter relies on the issue URL and summary for context rather than rendering the full body
Polling is one-directional: Fleet reads Jira issues to trigger work and does not transition Jira tickets back when work completes

Frequently asked questions

Does Fleet read Jira tickets directly?

Yes. Fleet's Jira adapter polls the Jira Cloud REST v3 search API for the configured project, normalizes issues into WorkItems, and runs trigger rules against them. It does not require routing through GitHub labels.

How does Jira authentication work?

With an Atlassian API token and your account email as HTTP basic auth — the documented Atlassian pattern where the token is the password component, not a bearer token. The site, project key, and email are set in the dashboard; the token is fetched at watcher start.

More integrations

Fleet + GitHub →Fleet + Linear →Fleet + MCP (Model Context Protocol) →Fleet + tmux →Fleet + Git Worktrees →

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.

See how it works Install Fleet