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.

The Jira connector keeps the work your teams already track in Jira tied to the compliance records in Aegis. Issues can come in as new risks or incidents, Aegis items can be created as Jira issues, and a single finding or action can be linked to the Jira ticket that fixes it, so Aegis can show whether that ticket was resolved before its due date. The connector moves data; a person still decides what a risk is worth and when it is 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, and at once for issue events Jira sends to the Jira webhook. The connector page has no sync-now button; to push one item to Jira straight away, use Create in Jira on that item's Jira issue panel.
Set it up /connectors/jira, by an Admin or Manager, where the Jira connector module is switched on for your organisation.

Who uses it

What's on this screen

No screenshot of this page is included in this edition; the description below follows the page as the product builds it.

The page configures one Jira connection: the most recently created one.

Once the connector has synced, the page shows Last successful sync: with the date and time of the last completed sync, and it still does after a reload. The counts of a sync are shown only for the visit in which you ran it; the audit log records every sync.

Setting it up

Before you start, create an API token for the Jira account at Atlassian's API token page, or ask your Jira administrator for an OAuth 2.0 access token issued for Aegis.

  1. Open /connectors/jira. Enter a Connection Name (for example Production Jira); it labels the connection wherever Aegis lists your Jira integrations.
  2. Enter the Instance URL, such as https://company.atlassian.net. It must start with https:// and point at an Atlassian or Jira host, otherwise Test Connection and Save Configuration stay disabled.
  3. Choose the Authentication Type. With API Token, fill in Email and API Token. With OAuth 2.0, the email field disappears and an OAuth Access Token field takes its place; Jira Data Center personal access tokens work there too.
  4. Select Test Connection. A green message confirms access, and the Default Project field turns into a list of your Jira projects shown as name and key. A red message gives the reason when the test fails.
  5. Pick the Default Project, or type its key (for example AEGSEC, not the project name). New Jira issues are created in this project.
  6. Choose the Sync Direction: From Jira (the default for a new connection), To Jira or Bidirectional. Then choose Map Issues To: Risks or Incidents. This only seeds the new connection's mapping.
  7. For inbound issues mapped to risks, choose a Default risk category and a Default risk owner. The form warns that inbound Jira issues are skipped until both are set. If no risk categories exist yet, it says so and asks you to create one under Risks first.
  8. Optionally add a JQL Filter, such as project = "PROJECT" AND status != Done, to narrow which issues are synced.
  9. Under Outbound updates of linked issues, tick the pushes you want (see the table below). All four are off until you switch them on.
  10. Leave Enable automatic synchronization ticked for the 15-minute schedule, then select Save Configuration. Saving again later edits the same connection rather than adding a second one.
Outbound option What it pushes to the linked Jira issue
Push status changes Moves the issue through an available Jira workflow transition, using the Aegis → Jira status table on the mapping page. A risk acceptance is never pushed.
Push the owner as assignee Only when exactly one Jira user has the owner's email address; otherwise the assignee is left unchanged.
Push the due date For risks, the next review date.
Push regulatory filing deadlines (incidents) For incidents, the next regulatory filing deadline as the Jira due date.

Editing a saved connection

  1. Open /connectors/jira. The form shows what is stored. Secret fields are blank with dots as placeholder; leave them blank to keep the stored token.
  2. To change the item type or risk category, select Configure mapping →. Map Issues To and the risk category are no longer on the form; a box in their place explains that they, and the status, priority and field mappings, are set on the mapping page.
  3. Change the Default risk owner if needed. It stays on the form while the direction brings issues in; risks and incidents created from Jira get this owner when the mapping assigns none.
  4. If you change the Instance URL to another address, a red note asks you to re-enter the token, and saving stays disabled until you do: a stored token is only sent to the instance it was entered for.
  5. Select Save Configuration. The existing connection is updated in place.

The mapping page

The link under the page title opens /connectors/mapping/jira/<id>, which decides how Jira issues become Aegis items. It is open to Admins and Managers.

Resolving a sync conflict

  1. On /connectors/jira, find the Sync conflicts card. Each row shows the Jira key, its summary and the kind of Aegis item it is linked to.
  2. Select Keep Aegis or Keep Jira. A confirmation asks, for example, “Overwrite SEC-123 in Jira with the Aegis values?”
  3. Confirm. A message reports that the conflict was resolved, and the row leaves the list.

Linking one item to a Jira issue

Audit findings, non-conformities, governance action items, continuity exercise actions and incidents carry a Jira issue panel once an enabled Jira connection exists.

  1. Open the item. The panel reads Not linked to a Jira issue. When more than one enabled connection exists, pick the Jira connection first.
  2. Type an existing key in Jira issue key (for example SEC-123) and select Attach issue, or select Create in Jira to open a new issue. A message confirms the linked or created key.
  3. Once linked, the panel shows the key (it opens the issue in Jira), its summary, Status in Jira, and after resolution a badge — Resolved on time, Resolved late or Resolved (no due date) — with the date it was resolved in Jira.
  4. Select Unlink and confirm to remove the link. The Jira issue itself is not changed.

On an incident, an amber note appears when the issue was closed in Jira while regulatory filings are still outstanding: the incident stays open and under the deadline monitor for you to review. A link in conflict shows the same Keep Aegis and Keep Jira choice inside the panel.

Tips and limits

Where this connects

The connector catalogue and shared connector behaviour are described in Connectors. Imported issues become Risks or Incidents. Linked findings appear in Audits and Non-conformities; linked actions in Governance bodies and Continuity.