Jira
Connect Jira Cloud to give Herald access to your issue tracker. Jira is configured once from the unified Add Integration list for both issue ingestion and real-time investigation access.
Authentication uses OAuth for ingestion plus your Atlassian account email and a Jira Cloud API token for tool access. Use an Atlassian API token, not a Jira personal access token.
The agent can:
- Fetch comprehensive Jira issue details by issue key (for example,
ENG-1234) - Retrieve comments, linked issues, and file attachments
- Read attachment contents, including files inside zip archives
| Parameter | Description |
|---|---|
| Connection name | A label for this Jira connection in Herald. |
| Atlassian subdomain | Only the subdomain from your Atlassian URL. For example, if Jira is at https://acme.atlassian.net, enter acme — not the full URL or hostname. |
| Jira email | The Atlassian account email used for cloud API authentication. |
| Jira API token | An API token from Atlassian account security. |
Optional parameters
| Parameter | Description |
|---|---|
| Projects | Jira project keys to ingest. If left empty, all accessible projects are ingested. |
After submitting the form, complete the Atlassian authorization flow and select the Jira site Herald should access.
