Open any capability and you get its whole story in one popup. Here's how to read it, link children from any board or tool, and remove links you no longer need.

Open the capability popup

Use the ⋮ menu on a capability card and choose View Details, or click a capability card inside a swimlane. The popup slides in from the right. The icons in its title bar are Copy link, Open full page and Maximize. For a Jira or Azure DevOps capability, Open full page opens the item in the tool itself.

The capability popup: overview, progress, properties and custom fields.

Overview tab

Progress: children done out of total and story points delivered. The bar is computed from the status category of every linked child, whether it comes from Kendis, Jira or Azure DevOps.
Properties: status, type, responsible, estimate, start and end. For synced capabilities the description and most properties are read-only and refreshed from the tool.
Custom fields: the board's custom field layout, plus an ALM fields group for Jira / ADO capabilities when configured under Board Settings › Create New Settings.

Children and progress

The Children block lists every child with its type icon, PI board chip, title, status and assignee. Children are ordered: the capability's own backlog children first, then the features on the linked PI boards, then Jira or Azure DevOps children that are on no board. Features on a PI board show the status they have on that board. Children that are on no board are refreshed from the tool when you open the popup, at most once every two minutes per capability.

Nine children across three ARTs with live status.

Link an existing item from anywhere

Click Link existing above the children list. The picker searches the whole solution, not just one collection.

This solution tab: searches features of every PI board linked to the solution, across all contributing collections. Narrow it with Source (Kendis, Jira, ADO) and Program board. Rows show the feature's current parent chip; press Add to link a free feature, or Move to re-parent one that already belongs to another capability. Move asks you to confirm: the button changes to Move? with a warning that the current link will be removed, and a second click within five seconds performs it. Rows already under this capability show Added. Without a search text the tab lists the most recent features of the solution.
Jira tab: shown when a linked PI board is synced with Jira. Type an issue key (for example FEA-1042) or part of a title; Kendis queries Jira live and lists matches with their issue-type icon. With several Jira accounts, pick the instance in the box on the right.
ADO tab: shown when a linked PI board is synced with Azure DevOps. Search by the numeric work-item ID (for example 1042). With several accounts, pick the instance in the box on the right.
A result of the wrong level, for example a story when the board links features, is marked wrong level and cannot be added.
Press Add on a result. The child appears in the list immediately, and on the board under its status category. If the issue you picked is already a feature on a linked PI board, Kendis links that feature. Click Done to close.

This solution tab: recent features with their parent chip and Add / Move / Added actions.

Capabilities in Jira, features in Azure DevOps

Many solution trains do not live in one tool. Portfolio and solution management keep capabilities in Jira, while one or more ARTs deliver their features in Azure DevOps (or the other way round). Neither tool can hold a parent link that points into the other tool. The solution board can.

Bring the capabilities in from Jira (Content From ALM, or Add Existing from an org backlog synced with Jira).
Link the ADO PI boards to the solution so their features appear in the swimlanes.
Open a Jira capability, click Link existing, find the ADO feature on the This solution tab (or on the ADO tab if it is not on a board yet) and press Add.

Kendis stores that parent-child relation on the solution board. It shows the ADO feature under the Jira capability in the swimlane and in the popup, counts it in the capability progress, rolls it into objectives, analytics and Tracking, and keeps refreshing its status from Azure DevOps. Jira and Azure DevOps are not modified: the relation lives in Kendis only, and it stays there through resyncs and filter re-imports.

ⓘ One board, both tools

Because the relation is held in Kendis, you get a single picture of the solution even when portfolio and delivery are in different tools. Nobody has to duplicate epics into ADO or features into Jira to make the hierarchy visible.

Same tool or not: what Kendis does

Capability	Child	Result
Jira (account A)	Jira issue from account A	Parent link written in Jira (Epic Link / parent) and in Kendis
ADO (account B)	ADO work item from account B	Parent link written in Azure DevOps and in Kendis
Jira	ADO work item, or Jira issue from a different Jira account	Kendis-only link. Message: Linked in Kendis only (different agile tool or ALM account)
Kendis-only	Anything	Kendis-only link

ⓘ Same ALM means same account

Two Azure DevOps accounts on one organisation, or two Jira sites, are treated as different tools. The link is still created in Kendis, but Kendis will not try to write a parent link across accounts.

ⓘ Kendis-only links survive resync

Cross-tool children are kept when the board is resynced or when a Jira / ADO filter re-imports the capability, and their status keeps refreshing from their own tool.

If the tool rejects the link (missing permission, wrong link type), the child is still linked in Kendis and an error toast explains why the ALM write failed.

Unlink a child

Hover a child row and click the ✕ at its end. The child is unlinked straight away, without a confirmation. When the link had been written in Jira or ADO, Kendis removes it there too; a Kendis-only link is removed in Kendis only. The board updates immediately.

In Link existing you can undo a link you made in the same session: click its Added button again. Rows that were linked earlier show Added greyed out; unlink those with the ✕ on the child row.

Hierarchy, Dependencies, Objectives and Risks tabs

Hierarchy: the ancestry of the capability (its own parent, when it has one) and the children with story points. Link existing is available here as well.
Dependencies: dependencies raised on the capability itself.
Objectives: solution objectives this capability contributes to, grouped by objective group.
Risks: risks from the solution ROAM register linked to this capability.
Comments and Activity: available on Kendis-only capabilities. When the popup is narrow, tabs that do not fit move into an N more menu.

Hierarchy tab with ancestry and children.

Objectives tab showing the objective K-1 contributes to.

Frequently asked questions

The child I linked from ADO does not show on the board.

It shows in the swimlane of the PI board the item belongs to, under the capability, grouped by its status category. If the item is not on any linked PI board it has no swimlane to sit in: you find it under the capability in the capability list, marked ALM only, in the popup and in Capability Progress.

Why did the link not appear in Jira?

Either the child is from a different tool or account (Kendis-only link by design), or Jira refused the write; the toast carries Jira's message. Check the link-type settings on the PI board's Jira configuration.

Can I link a story instead of a feature?

No. The picker accepts the child level configured for the board (features by default). On the Jira and ADO tabs an item of another level is marked wrong level. Stories are linked on the PI board.

How current is the child status?

Features on a PI board show their status from that board, which follows the PI board's sync. Children that are on no board are refreshed from the tool when the popup opens, at most once every two minutes per capability, and on every resync.

Capability details and child linking