The Kendis Dependencies extension is a powerful tool designed to centralize your scaled agile workflow by bringing a dynamic dependency view directly into your Jira issues. This guide details how you can use the extension to identify, manage, and resolve cross-team dependencies without leaving Jira.

1. Roles and Prerequisites

Your access to view and edit dependencies is determined by your user roles within Jira and Kendis.

1.1. User Roles and Access Levels

User Role	Access Level in Extension	Prerequisites
Standard Jira User	View Dependencies (Read-Only)	Requires only valid Jira access.
Kendis User (View & Edit)	View & Edit Dependencies	Requires valid Jira access and a valid Kendis account with a personal API Token for the one-time authentication.

1.2. Prerequisites Checklist

System Configuration: The Jira Administrator must have completed the one-time system-level API configuration.
Board Synchronization: The Kendis Board Owner must have enabled dependency synchronization for the specific Program Board your work item is linked to.

2. Extension Availability and Access

To start, determine the status of the extension in your organization.

2.1. If the Extension is Not Installed (Initial Request)

If you cannot find the extension, you can initiate a request to your administrator:

Search and Initiate Request: Navigate to Apps > Explore more apps and search for Kendis Dependencies.
Submit Request: Click Get app to fill out a brief form and send a formal installation request to your Jira Administrator.

2.2. If the Extension is Installed (Ready to Use)

If the administrator has installed it, you can access it from your Apps.

First-Time Activation: When you open a relevant Jira work item (Story, Feature, etc.), you must manually open the App Actions menu by clicking the icon below the issue title.
Open the Widget: Select Kendis Dependencies from the menu.
Persistent View Note: After this initial click, the Kendis Dependencies panel will automatically be displayed in the sidebar for all future visits.

2.3. Enable Edit and Manage Access

To have the ability to edit or change a dependency status, you must authenticate with your Kendis user account.

One-Time User Setup: When you want to change a dependency status, a "User Credentials Required" pop-up will appear.

Enter User Credentials: Enter your personal Email and API Token (retrieved from your Kendis Profile) and click Validate Credentials.

Manage Status: Once validated, you can click the status field within the panel to instantly update the dependency status.

View Program Board: Click View in Kendis to open the full high-level board in a new tab.

3. Managing Boards and Dependencies

The widget is your interface to dependency data flowing from Kendis, including risk indicators and cross-board visibility.

3.1. Navigating Program and Solution Boards

The widget's header allows you to switch the data context your work item is viewing:

Active Boards Dropdown: Click the dropdown menu in the header.
Program Board Dependencies: Select a Program Board to view dependencies that are scoped within that single ART or PI.
Solution Board Dependencies (Cross-Board): Select a Solution Board to view dependencies that span across multiple Programs/ARTs operating under a higher-level Solution Train.

This is how you view actual cross-board dependencies from Kendis.

3.2. Dependency Data and Risk Indicators

The visual structure clearly identifies the relationship and associated risks using the 1 and 2 numbering system:

Data Field/Element	Description	Visibility and Risk
Provider (1) Item	The blocking work item that must deliver first.	Reverse Dependencies: Indicates a critical sequencing error.
Dependent (2) Item	The blocked work item that is waiting for the provider.	Overdue Dependencies: Flagged if the dependency is not 'Done' past the Target Resolution Date.
Status Field	The current resolution status (e.g., To Do, In Progress).	The only field a Kendis User can Edit.
Work Item Data	Issue Key, Summary, Team, and Iteration.	This data reflects the item's current state and planning details as managed in the Kendis Program/Solution Board.

4. Editing Status, Dates, and Conversations

Kendis Users (users who have completed the one-time authentication) can perform the following actions directly from the Jira widget.

4.1. Updating Dependency Status

Click the Status field.

Change the status (e.g., Done).

4.2. Managing Due Date (To Fix Overdue Dependencies)

Click the Date Not Set or existing date field within the dependency record.

Select a new Target Resolution Date from the calendar picker to reflect a new commitment and fix the Overdue indicator.

4.3. Adding Collaborative Comments

Click the Chat Bubble Icon located on the right side of the dependency record.

Add context or questions.

The comment is saved to the Kendis dependency record and is immediately viewable by all users in both the Jira widget and the Kendis platform.

5. Troubleshooting Common Problems

Here we’re talking about the most common errors faced by users and the steps required to resolve them.

5.1. API Configuration Error

The widget might display an "API Configuration" Error with a message about setting up Kendis credentials.

Cause: This indicates a failure in the initial system-level connection. The Jira Administrator has installed the app but has not successfully entered the master API credentials.

Action (Your Step):

This is an Administrator-level issue. You must immediately contact your Jira Administrator and inform them that the Kendis Dependencies application needs its organization credentials configured.

5.2. Verification-Failed Error

When trying to update a dependency status, the extension shows "Validation failed. Authentication failed. Please check your email and API token." prompt appears.

Cause: Your personal API Token, which grants you edit access, has either expired, been revoked, or was entered incorrectly during the one-time user setup.

Action (Your Steps):

Access the Kendis Platform using your personal user account.
Click on your Profile icon > API Keys.
Select the API Key you created for Jira and click Regenerate to create a new, valid token string.
Copy the entire new token string to your clipboard.
Go back to the Reconfigure User Credentials pop-up.
Enter your current Email, paste the new API Token, and click Validate Credentials.