Jira
The Jira integration works with an ordinary Atlassian API token. There is no Atlassian app to install and nothing to approve in the Marketplace.
:::info Plan Integrations are available from the Starter plan upwards. :::
Connecting
Administration → Integrations → Jira. You need:
| Field | Where it comes from |
|---|---|
| Host URL | Your instance, e.g. https://acme.atlassian.net |
| The Atlassian account the token belongs to | |
| API token | Created at id.atlassian.com → Security → API tokens |
The token is stored on the organization and is never sent back to the browser.
Only owners and admins can connect or change it.
What it gives you
Sekee → Jira
For each linked (issue, test case) pair, Sekee writes a remote issue link on the Jira issue. It is written under a stable global id, so Sekee updates the link rather than adding a duplicate every time. The title is the test case name and the summary line says what the evidence currently is.
Links are rewritten:
- after a bug hunt verdict is recorded
- after a CI report is ingested
- when you link, unlink or refresh a requirement
All of it is best effort and gated by the integration's sync links setting. A Jira that is down or slow never fails a save in Sekee.
Jira → Sekee
A webhook endpoint re-reads a named issue when Jira says it changed, refreshing the cached title, status and priority on the requirement row.
The webhook's URL contains a secret minted per integration — that secret is the credential. A forged call can cause a refresh of one issue and nothing else, which is why it is safe to expose the path.
Requirements and the picker
With Jira connected, Requirements → Link requirement searches your instance and lets you pick issues by key or text. Without it, the picker says Jira is not connected, names who can connect it, and keeps a key you type until then.
See Requirements and coverage.
The link policy
If your organization has Block links outside Sekee turned on, the connected Jira's domain is automatically treated as inside — both by the paste guard in the browser and by the server that refuses the save. Connecting Jira does not require an exception to be added by hand.
See Policies.
Testing the integration
Point a staging organization at a stand-in rather than your real Jira: a small
HTTP server answering /rest/api/3/issue/:key and /remotelink is enough to
exercise both directions without writing remote links onto real issues.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| Search returns nothing | Token belongs to an account without permission on that project |
| Links never appear in Jira | Sync links is off, or the token cannot write remote links |
| Requirement fields look stale | The webhook is not reaching you; refresh the requirement by hand to confirm the credentials still work |
| A Jira link is refused as you paste it | The policy is on and the host does not match the connected instance exactly |