Centralise your risk management by syncing Jira issues directly with Kendis Risk Register. This integration allows you to track, mitigate, and link risks to your Program Boards, Solution Boards, and Collection in real-time.
Prerequisites
Before starting the configuration, ensure:
You have Admin access in Kendis.
A Jira ALM account is already integrated into your Kendis workspace.
Your Jira project contains a specific issue type for risks (e.g., "Risk" or "Story").
Establish Jira-Kendis Connection
Before Kendis can see your Jira data, you must define the connection between the two systems.
Connect Jira
Click the Settings icon on the bottom left, then select Risk Connections.
Click the New Connection button.
Connection Name: Give it a clear name like Jira Risk Sync.
ALM Account: Select your pre-configured Jira instance (e.g., Connect to Jira (K demo)).
Save: This unlocks the next tabs for project and mapping configuration.
Select Your Jira Project
Switch to the Jira Projects tab.
Click Add Project.
Search for and select the project where your risks live (e.g., CP Capabilities Warehouse).
Map Your Fields
This is the most critical step. It tells Kendis which Jira fields correspond to Kendis risk attributes.
Kendis Attribute | Jira Mapping Field | Purpose |
Item Type | Risk (or Story) | Defines which Jira issue type represents a risk. |
Link Type | blocks | Shows how the risk impacts other items. |
Title | Summary | The main headline of the risk. |
Status | Status | Syncs the workflow state (e.g., To Do to Done). |
Raised On | Created Date | Tracks when the risk was first identified. |
Target Date | Due Date | The deadline for mitigation. |
Set Up Your Risk Register
Think of the Register as the Folder that holds all your synced risks.
Click the "!" icon in the left-hand sidebar.
Click the Create Risk Register button.
Configure the Register:
Prefix: Enter a 3-letter code (e.g., RSK) to uniquely identify items.
Register Name: e.g., Q1 Program Risks.
Risk Connection: Select the connection you just built in Phase 1. This "plumbs" the register to Jira.
Risk Matrix: Choose your 5x5 or 3x3 impact/probability matrix.
Populating the Register
To optimise your data entry process, Kendis provides three ways to populate your Risk Register, ensuring your Jira data stays synchronized without manual re-typing.
Click the + Add button at the top of your Risk Register interface to access the following options:
Create Risk
Select Create Risk to build a new entry directly within Kendis.
If two-way sync is enabled in your mapping settings, Kendis will automatically generate a corresponding work item in your Jira project.
Add Content from Jira (Best for Bulk)
This allows you to import risks via a Jira Query.
Simply provide the Jira Project Name and a Saved Query Name (JQL) to fetch all matching risks into Kendis.
Add Existing (Link by ID)
Use this for specific items you've already identified in Jira.
Select Add Existing and enter the Jira Item ID (e.g., PROJ-123) to establish a direct link to that work item.
Linking Risks to Planning Contexts
A risk is only useful if you know what it affects. You can link your Register to three different levels:
Where to Link?
Program Boards: Use this for team-level risks identified during PI Planning.
Solution Boards: Use this for high-level risks affecting multiple Agile Release Trains (ARTs).
Collections: Use this for portfolio-level visibility.
How to Link:
Inside your Risk Register, click the + Link Board button in the top right.
Choose the category (Program, Solution, or Collection).
Select the specific board name from the dropdown.
Once linked, you can see the count of associated boards next to the register name.
Monitoring and Analytics
Once your risks are flowing, use the Analytics button inside the Register to visualize:
Risk Heatmap: See which risks are in the "Red" zone.
Status Distribution: Track how many risks are "Mitigated" vs. "Open."
Sync Health: Click any risk to see the Jira Icon. This confirms the item is live and syncing.