Kendis Dependencies Extension for Jira Cloud: Real-Time Cross-Team Visibility, Directly in Jira

[#1]

In scaled-agile environments, especially when you’re coordinating across Agile Release Trains (ARTs), Program Increments (PIs), or even entire solution trains, dependencies are more than just “stuff that blocks other stuff.” They’re one of the biggest risk vectors for delivery predictability. Without strong dependency management, teams can trip over each other, miss critical handoff points, and derail release plans.

Managing cross‑team and cross‑board dependencies in Jira has traditionally required multiple tools, manual tracking, or complex workflows that live outside the issue itself. With the Kendis Dependencies Extension for Jira Cloud, dependency context and management become part of the Jira experience — no tool switching, no lost visibility, and no detached tracking.

This extension brings powerful scaled‑agile dependency management directly into Jira — enabling teams to identify, manage, update, and resolve cross‑team dependencies without leaving the issue view

What the Kendis Dependencies Extension Actually Does

At its core, the Kendis Dependencies extension is designed to centralize dependency visibility and management for Jira issues. It captures rich context  including status, risk indicators, target resolution dates, team and sprint information, and displays it in a structured widget you access from the Jira issue pane.

This means:  

• Dependencies are no longer just simple issue links — they have clear roles (provider vs dependent), status, and resolution expectations.
  
  
• Teams can see the real dependency picture immediately, including cross‑board and solution‑level relationships when configured.
  
  
• Dependency data flows both ways between Jira and Kendis — making sure Jira users always see updated dependency context, regardless of where changes originate.

How It Works in Jira

1. Seamless Access Inside the Jira Issue

Once the extension is installed and enabled at the organization level:

• Jira users can open a work item — whether a story, feature, or higher‑level issue — and select the Kendis Dependencies widget from the issue actions panel.
  
  
• After first‑time activation, the dependency panel sticks in the Jira sidebar for all future visits.

Users with only standard Jira access can view dependency details, while authorized users (who authenticate with their Kendis credentials and API token) can edit and manage dependency status, dates, comments, and more

Learn how to enable the widget: Kendis Help

Real Context and Risk Indicators in Every Dependency

The extension surfaces a rich set of dependency data that goes far beyond simple link types:

1. Provider vs Dependent Items: The Kendis Dependencies extension removes confusion from Jira dependency links by using a simple 1 and 2 numbering system:

• 1 → the item that must be completed first
• 2 → the item that depends on it and comes next

This makes dependency direction immediately clear, without relying on Jira’s often confusing link wording. A reverse dependency occurs when an issue you are waiting on is planned after your sprint. This means the dependency is set the wrong way around — the required work will not be delivered in time.

• Status Indicators: See the current resolution status (e.g., To Do, In Progress, Done) directly inside the widget.
  
  
• Sprint and Team Labels: Understand where each work item sits in planning, including team and iteration context.
  
  
• Target Resolution Dates: These dates help trigger overdue or at‑risk indicators if a dependency isn’t resolved on schedule.
  
  

This structured context gives Jira users much deeper insight into dependencies than a simple “linked issue” ever could, making it easier to prioritize blockers and focus conversations.

This structured context gives Jira users much deeper insight into dependencies than a simple “linked issue” ever could, making it easier to prioritize blockers and focus conversations.

View Dependencies Across Multiple Boards

Within the extension’s widget, users can switch context to view:

• Program Board Dependencies: Dependencies scoped within a single Agile Release Train or PI.
  
  
• Solution Board Dependencies: Cross‑board dependencies that span multiple programs or ARTs when your organization uses solution‑level planning.
  
  

This means Jira users can see dependencies they are part of, and dependencies that impact them — regardless of where the work lives in the broader planning hierarchy

Editing and Managing Dependencies in Jira

Users with edit access (after authentication) can update key dependency fields directly within Jira:

Update Status

Change the dependency status (e.g., from Open to Done) right in the widget. This instantly updates the dependency on both the Jira side and the Kendis board.

Adjust Target Resolution Dates

If a dependency becomes overdue, users can immediately update the date to reflect new commitments and resolve risk indicators.

Add Collaborative Comments

Users can add contextual comments in the widget. These conversations are stored on the dependency record and visible in both Jira and Kendis.

This eliminates the need for separate Slack threads, emails, or external notes — all essential communication remains connected to the dependency itself.

Troubleshooting & Admin Considerations

There are a few common setup situations Jira admins and users may encounter:

• Initial API Configuration: If the system‑level API credentials are not configured, users may see configuration errors in the widget. Admins must complete this setup to enable the extension’s full functionality.
  
  
• User Authentication Errors: If a user’s Kendis API token expires or is incorrect, edit access may fail. Users should regenerate and re‑validate their token via their Kendis profile.

These steps ensure that the extension connects properly and provides live syncing of dependency updates.

The Kendis Dependencies Extension for Jira Cloud is more than a simple integration — it’s a purpose‑built tool that brings strategic dependency tracking and cross‑team alignment into your everyday Jira workflows. By exposing rich dependency context inside Jira issues and ensuring two‑way sync with Kendis boards, teams gain unprecedented clarity and control over complex delivery relationships.

Install the extension today to eliminate blind spots, reduce context switching, and make dependencies visible, actionable, and collaborative — all within Jira itself.

marketplace.atlassian