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
- Admin and Manager open the connector page, save and test the connection, edit its mapping, resolve sync conflicts, and attach, create or unlink Jira issues on individual items.
-
Contributor and
Viewer are redirected away from
/connectors/jiraand its mapping page, and theJira issuepanel on findings, actions and incidents stays hidden for them.
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.
-
Header: A breadcrumb (
Connectors / Jira), the titleJira Connectorand a one-line description. Once a connection is saved, a linkMap statuses, priorities, fields and owners →appears under the description and opens the mapping page. -
Last-sync alert: When the last sync failed or only partly completed, a red
box headed
The last Jira sync did not completesits above the form with the reason. When issues were skipped for lack of defaults, it gives the number of Jira issues not imported and asks you to set a default risk category and owner on the connection. -
Configuration card: The connection form: name, instance URL, authentication,
Test Connection, project, sync direction, the risk defaults, JQL filter, outbound updates, the automatic-sync switch andSave Configuration. -
Sync conflicts card: Shown once a connection exists; lists linked issues
that changed on both sides, or reads
No sync conflicts. -
Disconnect: A
Disconnect connectorsection with aDisconnectbutton, available once a connection is saved. -
Help boxes:
Setup Instructions(six short steps) andSync Capabilities(the three directions and JQL filtering) at the foot of the page.
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.
-
Open
/connectors/jira. Enter aConnection Name(for exampleProduction Jira); it labels the connection wherever Aegis lists your Jira integrations. -
Enter the
Instance URL, such ashttps://company.atlassian.net. It must start withhttps://and point at an Atlassian or Jira host, otherwiseTest ConnectionandSave Configurationstay disabled. -
Choose the
Authentication Type. WithAPI Token, fill inEmailandAPI Token. WithOAuth 2.0, the email field disappears and anOAuth Access Tokenfield takes its place; Jira Data Center personal access tokens work there too. -
Select
Test Connection. A green message confirms access, and theDefault Projectfield turns into a list of your Jira projects shown as name and key. A red message gives the reason when the test fails. -
Pick the
Default Project, or type its key (for exampleAEGSEC, not the project name). New Jira issues are created in this project. -
Choose the
Sync Direction:From Jira(the default for a new connection),To JiraorBidirectional. Then chooseMap Issues To:RisksorIncidents. This only seeds the new connection's mapping. -
For inbound issues mapped to risks, choose a
Default risk categoryand aDefault 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. -
Optionally add a
JQL Filter, such asproject = "PROJECT" AND status != Done, to narrow which issues are synced. -
Under
Outbound updates of linked issues, tick the pushes you want (see the table below). All four are off until you switch them on. -
Leave
Enable automatic synchronizationticked for the 15-minute schedule, then selectSave 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
-
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. -
To change the item type or risk category, select
Configure mapping →.Map Issues Toand 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. -
Change the
Default risk ownerif 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. -
If you change the
Instance URLto 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. -
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.
-
Rules:
Which item a record becomesis checked from top to bottom; the first rule that matches decides, and an issue that matches no rule is skipped. - Status and priority: Map each Jira value to an Aegis status, and each priority to a severity, or to impact and likelihood for risks.
- Fields and owner: Map any Jira field, custom fields included, to an Aegis field, and match an email field to an active Aegis user, with a fallback owner when nobody matches.
-
Aegis → Jira status: The Jira status each Aegis status is pushed as when
Push status changesis on. An empty row uses the default shown. -
Preview: Shows how the current mapping would treat recent issues, without
saving or syncing anything. Then select
Save mapping.
Resolving a sync conflict
-
On
/connectors/jira, find theSync conflictscard. Each row shows the Jira key, its summary and the kind of Aegis item it is linked to. -
Select
Keep AegisorKeep Jira. A confirmation asks, for example, “Overwrite SEC-123 in Jira with the Aegis values?” - 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.
-
Open the item. The panel reads
Not linked to a Jira issue.When more than one enabled connection exists, pick theJira connectionfirst. -
Type an existing key in
Jira issue key(for exampleSEC-123) and selectAttach issue, or selectCreate in Jirato open a new issue. A message confirms the linked or created key. -
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 lateorResolved (no due date)— with the date it was resolved in Jira. -
Select
Unlinkand 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
- When both sides changed the same linked issue, nothing is written and the link is marked as a conflict until a person resolves it.
- A Jira status that would formally accept a risk is refused; a Jira closure never closes a regulatory filing of an incident.
-
The Jira webhook checks an HMAC-SHA256 signature in
x-hub-signature; its secret is set on your instance by Euraika, and it only accepts events where the webhook connector module is switched on. Without it, changes arrive with the 15-minute sync. - Findings and actions are only created in Jira one at a time, from their panel; the 15-minute sync never creates them in bulk.
- For a saved connection the risk category lives on the mapping page, even though the missing-defaults alert asks you to set it “on the connection”.
-
Disconnectasks for confirmation, then deletes the stored configuration and credentials, the sync schedules and mappings that use them, and the connection's record of which Aegis items are linked to which Jira issues; syncing stops and Aegis returns you to the Connectors page. Records already imported stay in Aegis, and you can configure the connector again later.
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.