Skip to main content
Connect DevHelm to Jira to open an issue in your project on every incident event. DevHelm uses the Jira Cloud REST API v3 with Basic authentication (your Atlassian account email plus an API token), creating one issue per event in the project and issue type you choose.

​
Setup

1

Create an Atlassian API token

  1. Go to id.atlassian.com/manage-profile/security/api-tokens
  2. Click Create API token, give it a descriptive label, and choose an expiry
  3. Copy the token immediately — Atlassian shows it only once
Note the email of the Atlassian account that created the token; you’ll need both for authentication.
2

Find your domain, project key, and issue type

  • Domain — your Atlassian site, e.g. yourteam.atlassian.net (just the host, no https://)
  • Project key — the uppercase prefix on issue IDs; if your issues are OPS-123, the key is OPS
  • Issue type — the name of an existing type in that project (e.g. Bug, Task, Incident). Defaults to Bug if omitted. The name is case-sensitive and must already exist in the project.
3

Create the alert channel in DevHelm

devhelm alert-channels create \
  --name "Jira Issues" \
  --type jira \
  --config '{"channelType":"jira","domain":"yourteam.atlassian.net","email":"you@company.com","apiToken":"your-atlassian-api-token","projectKey":"OPS","issueType":"Bug"}'
4

Test the channel

devhelm alert-channels test <channel-id>

​
Configuration

FieldDescriptionRequired
domainAtlassian instance domain, e.g. yourteam.atlassian.net (no https://)Yes
emailAtlassian account email associated with the API tokenYes
apiTokenAtlassian API token used for Basic authYes
projectKeyProject key where issues are created, e.g. OPSYes
issueTypeIssue type name; defaults to Bug (case-sensitive, must exist)No

​
Issue format

DevHelm creates one issue per incident event (fire-and-forget — it does not reopen or transition existing issues). The summary leads with the severity and monitor name, and the description includes the monitor URL, failure reason, latest status code, duration, and a link back to the incident in DevHelm.

​
Troubleshooting

  1. Use the API token, not your account password
  2. Make sure email is the exact Atlassian account that created the token
  3. If the token expired, generate a new one and update the channel
  1. Confirm domain is just the host (yourteam.atlassian.net) with no https:// prefix or trailing path
  2. Verify the projectKey exists and is the uppercase prefix from issue IDs (e.g. OPS from OPS-123)
  3. Check issueType matches an existing type name in that project exactly — names are case-sensitive
The account behind the token needs Create issue permission in the target project. Confirm the user’s project role grants it, then run devhelm alert-channels test <id>.