# Jira

Requirements and issues, kept as context the agent can cite

- Category: Apps
- Runs in: the Phloem cloud

Puts your Jira Cloud requirements and issues in Trace, so Hamming can cite where a limit came from or where a failure is tracked.

## What Phloem reads
- **Requirements and issues** — from the projects or JQL you set. Issues of your requirement types become requirements; the rest stay issues.
- **Fields** — summary, status, priority, assignee, labels, issue type, and every number custom field. A unit in the field's name is kept as its unit.
- **Links** — *blocks* and other issue links, and the parent issue
- **Parts** — if you name a part number field, each issue links to the part with that number

Phloem never writes to Jira.

## What you need
- A Jira Cloud site (`acme.atlassian.net`).
- An Atlassian account's email and an API token. Create the token at **id.atlassian.com → Security → API tokens**. Phloem reads what that account can read.

## Connect
1. In the console, open **Connectors**, choose **Add connector**, then **Jira**.
2. Enter **Jira site**, **Atlassian account email** and **API token**.
3. Set the scope. List project keys in **Projects** (empty reads every project), or write a **JQL scope**, which replaces **Projects**. Leave out `ORDER BY`; Phloem sets the order.
4. Optional: **Requirement issue types** (default `Requirement`) and **Part number field** — a field name or id (`customfield_10061`) whose value names a part.
5. Save.

## Notes
- Trace picks up changed issues every few minutes.
- Jira does not report deletions. A deleted issue leaves Trace at the next full sync.
- A scope larger than 2,000 pages of 100 issues stops with an error. Narrow the scope.
- **Keep in Trace** and **Sync now** are on the connector's page.

## Connection fields

| Field | Type | Required | Notes |
|---|---|---|---|
| Jira site | Text | Yes |  |
| Atlassian account email | Text | Yes |  |
| API token | Secret | Yes | Create one at id.atlassian.com → Security → API tokens. |
| Projects | Any of | No | Project keys to read. Leave empty to read every project, or use JQL. |
| JQL scope | Text | No | Replaces Projects when set. Ordering is the connector's. |
| Requirement issue types | Any of | No | Issues of these types are requirements; the rest are issues. |
| Part number field | Text | No | A field whose value names a part; the issue then references it. |