Jira
Every review opens a ticket in the project that owns the vendor, and closes itself the moment the risk score is signed off. Your team keeps working where they already work, and the review stops being a second queue nobody watches.
- Category
- Ticketing & work
- Auth method
- OAuth 2.0 or API token
- Direction
- Two-way
- Sync frequency
- Real time
- Scopes requested
- 5
- Available on
- All plans
- Maintained by
- Urengi
- of reviews tracked as a ticket
- 74%
- median time to connect
- 4 min
- scopes requested, none optional
- 5
- ticket per review, never a duplicate
- 1
What the Jira integration does
Three jobs, all of them things a project lead currently does by hand.
One ticket per review
The ticket opens in the project that owns the vendor, carries the tier and the evidence checklist, and links back to the review. Re-running a review updates it rather than opening a second.
Transitions follow the review
Evidence received, tier approved, exception granted — each moves the ticket to the status you mapped. Nobody drags a card to reflect a decision made elsewhere.
Renewals arrive as work
A review that reopens creates the ticket ahead of the certificate expiring, with the due date already set. Renewals stop being a surprise in the last week.
Exactly what Urengi can see
Five scopes on the projects you name. Urengi cannot see a project you did not select.
Urengi reads
- Project and issue-type names
- Issue status and transition names
- Assignee display names and emails
- Issues Urengi itself created
Urengi writes
- Review tickets in the selected projects
- Status transitions you mapped
- Comments carrying evidence updates
Urengi never touches
- Issues in projects you did not select
- Attachments or their contents
- Boards, sprints or workflow configuration
- Anything after you revoke the token
Connect it in four steps
One authorisation, one field mapping, and a test sync you run yourself.
01
Authorise the connection
Open Jira from this page and approve the scopes listed above — OAuth in a browser tab, or a scoped API key you paste. An admin approves them once.
02
Choose what syncs
Pick the projects, spaces or accounts Urengi should watch. Narrow is fine to start with; widening it later does not re-authorise anything.
03
Map your fields
Match owners, cost centres and tiers to what Urengi already tracks. Defaults arrive pre-filled from the first sync, so most teams change nothing.
04
Run a test sync
Pull one record and check it landed on the right review. The audit entry confirms the mapping before a real vendor is touched.
Your token, your rules.
Urengi stores the Jira token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Jira and every Urengi write stops within seconds — the audit log keeps the history, the connection simply ends.
Read the security statement- SOC 2 Type II
- audited annually
- Per-tenant keys
- no shared secrets
- Revocable in Jira
- one click, no ticket
- EU or US residency
- chosen at signup