Integrations/Connectors
Jira
What it is
Project and ticket management platform. The integration is bidirectional: EterShield creates issues in Jira from Tasks and Risks, and Jira updates the status back.
How to configure
In Settings → Integrations → Jira:
| Field | Example |
|---|---|
| URL | https://empresa.atlassian.net |
| Project Key | ES |
| Issue Type | Task |
utilizador@empresa.pt |
|
| API Token | Generated at id.atlassian.com → API tokens |
Automatic Task push (new)
The Jira integration now has the "Automatic push to Jira" toggle (config.autoPush). When active:
- Every new or updated Task is sent to Jira automatically, with no need to click "Sync with Jira"
- It applies to both creation and update of Tasks (it does not fire directly from Gaps, only via Task)
- It is off by default: the manual flow (button on the details page) remains available
How data comes in and goes out
EterShield → Jira:
- Any Task can be sent to Jira manually (button on the details page) or automatically (see above)
- Any Risk can be sent to Jira
- Priority mapping:
EterShield Jira CRITICAL Highest HIGH High MEDIUM Medium LOW Low INFO Lowest - Stores
jiraIssueKeyandjiraIssueUrlon the record
Jira → EterShield (webhook): Configure in Jira → Settings → System → Webhooks:
- URL:
https://etershield.etergrowth.com/api/v1/integrations/jira/webhook - Headers:
x-api-key: SEU_API_KEY+x-tenant-id: SEU_TENANT_ID - Event:
Issue Updated
The endpoint validates the HMAC-SHA256 signature (x-hub-signature / x-hub-signature-256) when a webhook secret is configured in EterShield. Important: always configure the secret; if it is missing, signature verification is skipped (the webhook still requires x-api-key + x-tenant-id, but without cryptographic proof of Jira origin).
Status mapping:
| Jira | EterShield |
|---|---|
| To Do | TODO |
| In Progress | IN_PROGRESS |
| In Review | IN_REVIEW |
| Done | DONE (and Risk → MITIGATED) |
| Blocked | BLOCKED |
Full flow
Where it appears in EterShield
- Tasks → with a direct link to the Jira issue
- Risks → with a direct link to the Jira issue
Coming soonThis page will be available soon.