Jira

Link Jira Cloud issues to Aegis risks and incidents, in either direction, and track how Jira tickets for audit findings and actions are closed.

At a glance

Direction Both ways, as chosen per connection: from Jira, to Jira, or both.
What it brings in Issues matching the connection's project and JQL filter. Outbound, Aegis creates issues for risks and incidents and, when switched on per connection, pushes status, assignee, due date and regulatory deadline changes of linked issues.
Where it lands A new risk or incident, decided by the first matching rule of the connection's mapping. Audit findings, non-conformities, governance action items and continuity exercise actions can be linked one by one; for those Aegis only records when and whether the Jira issue was resolved on time.
Credentials and permissions Your Jira Cloud address, the email of a Jira account and an API token from Atlassian (or an OAuth token). The account needs to browse the project and, for outbound sync, to create and edit its issues.
Owner of imported records The owner from the mapping, else the connection's default owner, else the person who ran the sync. A scheduled run without a usable owner or risk category skips the issue and reports it.
When it runs Every 15 minutes for enabled connections, on demand with the sync button, and at once for issue events Jira sends to the Jira webhook.
Set it up /connectors/jira, by people allowed to configure connectors, on a plan that includes the connector.

Good to know

Where this connects

Mappings are edited from the connector page; the inbound and outbound fields are described in Connectors. Linked findings appear in Audits and Non-conformities.