1. Overview
Kendis has just released a dynamic, fully integrated application, Kendis Dependencies for Jira Cloud. This app helps with strategic alignment, allowing you to instantly embed real-time PI dependency management directly into your Jira issues.
This guide details the crucial steps required to ensure the application is installed, securely configured, and accessible to every user in your organisation.
1.1 Prerequisites
Before starting the process, ensure you have the necessary credentials and permissions:
Jira Administrator and Kendis Board Owner permissions.
The Kendis API Token, Email Address, and Organization Domain prefix. The process for generating this token is explained below.
1.2 Roles and Responsibilities
Jira Administrator: Responsible for the initial installation and secure system-level API configuration.
Kendis Board Owner: Responsible for enabling the dependency synchronisation on specific Program Boards.
Standard Jira Users: After setup, all users can read dependency information via the application in Jira.
2. Install and Configure Kendis App
The Jira administrator is responsible for installing the app and establishing the secure connection.
2.1 Installation Steps
Log in to Jira as an administrator. Navigate to Apps > Explore more apps.
Search for Kendis Dependencies and click Get it now.
Confirm the correct Jira site on the "Select a site" screen and click Review.
Review the permissions the application requires for data storage, sharing, and processing on the next screen before proceeding further.
Once installed, click Manage apps. In the Jira Admin settings sidebar, you will be able to see the Kendis Dependencies application under Apps.
Click the Kendis Dependencies to configure the application.
2.2 Configure the System-Level Connection
This step secures the system link using the API token.
On the API Configuration screen, enter the Organisation Short Name, your Admin Email, and the API Token (Jump to Section 3 to generate the API token from Kendis).
Once you have generated and pasted the API key, click Validate Credentials. The system will confirm: "Your credentials are configured," confirming a secure connection.
3. Generate API Token and Retrieve Credentials
As an admin, you retrieve the master API Token to establish a secure connection between Jira and the Kendis Platform. This token is different from your standard Jira password.
Log in to the Kendis Platform. Click your Profile icon, navigate to API Keys, and create a new API Token.
Enter the key name and set the Expiration to Custom Defined (recommended) for long-term access.
Copy the generated token and paste it into your Jira board configuration tab.
Token Field: Contains the unique API Token (e.g., PNJ2-qDFO2n1_...) which must be copied for use in external applications.
Warning: The token is shown only once. You must copy it now, as it is not stored and cannot be viewed again.
Revoke Button: Immediately deactivates the current token, preventing all access to Kendis from applications using it.
Regenerate Button: Creates a new token string for this key name, instantly invalidating the previous token.
Update Button: Saves any changes made to the key's name or expiration date.
4. Final Validation and User Handoff
The final phase confirms the successful setup, validates that data is flowing into Jira, and clearly outlines the access privileges for all users within the organization. This is essential for program oversight and risk mitigation.
Navigate to a Jira work item (Story or Feature) that is linked to the newly configured Kendis Program Board.
Click the View app actions icon (shown in the image below), and then select Kendis Dependencies to open the widget.
Confirm that the Kendis Dependencies widget loads and displays live dependency data (Provider, Dependent, Board Name, etc.).
4.1 Which Items are Visible to Users?
Interface Element | Details Visible | Purpose |
Header | Active Board (e.g., Finance Board), Refresh, View in Kendis controls. | Used to switch board context or pull the latest data. |
Dependency Structure | Visual lines connecting the Dependent Item (2) to the Blocking Item (1), including the link type (e.g., "is blocked by"). | Provides immediate visual context of who is waiting on whom. |
Work Item Data | Issue Key, Summary, current Status (e.g., To Do), assigned Team, and planned Iteration. | Displays all required data fields needed to track the commitment. |
Actionable Status | The status field (e.g., To Do or Accepted). | The primary interactive element for authorized users to change the dependency status. |
4.2 Access Levels
Viewing: All Jira users have view-only access to all data displayed on this widget immediately.
Editing: To change the status, you must complete the one-time user setup to validate your personal Kendis account.