Skip to main content

New Kendis Item Card

Easier, better and inline editable Kendis Items cards

Written by Kendis Team

The Kendis card is the new way to read and edit a single item end-to-end. It currently appears on these views:

  • Org Views Backlog (the board and item listings under a workspace)

  • Roadmaps

  • Timeline view

  • Kanban board

  • Strategic Themes (when you open a linked item)

  • OKR Timeline and OKR Roadmap (when you open a linked or child item)

  • Milestones

It does not open on Program Board, Solution Board or Risk Register yet. Items opened from those surfaces continue to use the existing detail popup until those screens are migrated in a later release.

How the card opens

Click any item on one of the surfaces listed above. Instead of the old popup, the new card appears. There's nothing to enable or configure.

The same card opens whether the item is:

  • A Kendis-only item (carries the Kendis "K" mark on the type pill).

  • A Jira-synced item (Jira issue-type icon and the Jira key).

  • An Azure DevOps work item (ADO work-item icon and the ADO ID).

The card layout adapts to the source: ALM items show ALM-specific fields (Reporter for Jira, Area Path and Iteration Path for ADO), Kendis-only items show Kendis-specific fields (Responsible, Other Requirements). Content and tabs are tuned per source so empty sections aren't shown.

Two layouts

A button in the top toolbar switches between three ways to look at the same card:

Layout

Notes

Slide-over

Slides in from the right of the page. Keeps the surface behind it visible so you can scan the board while reading the item. The default when you click an item.

Full page

A dedicated page on its own URL (/item/<id>). Open it from the toolbar's "Open full page" icon, or paste a link copied with the "Copy link" button.

The toolbar at the top of the card carries:

  • A Breadcrumb of the item's ancestors. Click any crumb to navigate to that ancestor in the card.

  • Copy link — copies a permanent link to the item.

  • Open full page — navigates to the dedicated /item/<id> page.

  • Maximize / Restore — flips the slide-over between docked-right and full-viewport.

  • Close (Esc) — closes the card.

The header

Under the toolbar, every card shows:

  • A type pill with the item's type icon and its key. For Jira and ADO items the pill is a hyperlink that opens the issue in Jira or Azure DevOps in a new tab. For Kendis-only items the pill carries the Kendis "K" mark and is not a link (you're already inside the item).

  • The item title. Click the title to edit it in place. Click away or press Enter to save.

  • Below the header, a tab strip.

The tabs

Tab

Always shown

Notes

Overview

Yes

Description, custom fields, children list. The default tab on every item.

Hierarchy

Yes

Ancestor chain and direct children.

Comments

Kendis-only items

Rich-text composer plus the comment thread.

Activity

Kendis-only items

Full edit history.

For ALM items (Jira / ADO) the Comments and Activity tabs are hidden on purpose: comments and history live in the upstream provider and don't share state with Kendis. Showing empty Kendis tabs would feel broken.

Inline editing

Click any field value to edit it. Click away (or press Enter on single-line fields) to save. There's no separate edit mode and no save button.

Fields that edit inline include:

  • Title and description.

  • Status and assignee (Jira / ADO via the provider's user search; Kendis users via the Kendis search).

  • Responsible (Kendis-only items).

  • Story points / estimate.

  • Start and end dates.

  • Labels.

  • Item colour.

  • External key (for items that carry one).

  • Custom fields — both Kendis custom fields and ALM custom fields, including rich-text custom fields with formatting, lists and links.

  • For Azure DevOps items: Area Path and Iteration Path via cascading tree pickers that mirror your ADO project structure.

  • For Jira-feature levels: PI Board via a multi-select against every PI Board configured in the workspace.

The card saves to the same back-end endpoints the legacy popup used, so values you change are visible everywhere immediately.

The Overview tab

Default tab. Contents in order:

  1. Identity at the top — type pill, key, title.

  2. Area Path and Iteration Path (Azure DevOps items only), above the description, so you can scope the work without scrolling.

  3. Description as a rich-text editor.

  4. Other Requirements (Kendis-only items) as a second rich-text block.

  5. Rich-text custom fields, rendered formatted inline. Edit by clicking into the panel.

  6. Children — a list of direct children with inline editing of title, status, assignee and story points, drag to reorder, and an Add child button. The button respects the hierarchy level: for example a Feature can add Stories. New children appear in the list immediately for everyone viewing the card.

The right rail (Properties)

Down the right side of the card, the rail shows a compact properties block:

  • Progress card — % complete, "X of Y children done", "P / T pts".

  • Status — editable for both Kendis-only and ALM items.

  • Responsible (Kendis-only) — single user.

  • Assignee (ALM) — Jira or ADO user via the provider's user search.

  • Reporter (Jira only) — read-only chip.

  • Estimate — story points, editable inline.

  • Start and End dates.

A Show N more toggle reveals the rest:

  • Collection — the Release Train pill.

  • PI Board — a chip list for most items; for PI-feature levels, an editable multi-select to add the item to one or more PI boards.

  • PI and Sprint pills.

  • Color — a colour picker (Kendis-side tag, not synced to Jira / ADO).

  • External key with a launch link.

  • Labels — a labels input.

  • Watchers — chips with avatar and name, an × Remove on each, a "+ Add watcher" picker that excludes anyone already watching.

Below the standard properties, Custom fields render against the item's source — Kendis custom fields for K-only items, the configured Jira fields for Jira items, ADO fields for ADO items. Per-source save dispatch keeps the right field-payload going to the right place.

The Hierarchy tab

Two sections:

  • Ancestry — the parent chain, indented one level deep per ancestor. Click any row to navigate to that ancestor. The current item is highlighted at the bottom with a "This item" tag.

  • Children — the same children list the Overview tab carries, with the same inline editing and Add child flow.

The Comments tab (Kendis-only items)

Threaded comments on the item:

  • A rich-text composer at the top with bold, italic, code, inline code, bullet list, link, ordered list. Use ⌘/Ctrl + Enter to post.

  • Edit or delete your own comments.

  • The tab header shows the comment count.

  • Add a link via an inline form, no window.prompt.

The Activity tab (Kendis-only items)

A full history of changes to the item — status moves, assignee changes, field edits, date changes, parent reassignments. Each entry shows who, when and what changed.

Live updates

When you change a field on the card, anyone else looking at the same item sees the change reflected on their card without a manual refresh. The children list on Hierarchy and Overview updates the same way when a child is added or reordered.

Hyperlinks back to Jira and Azure DevOps

For ALM items, the type pill at the top of the card is a clickable hyperlink. One click opens the item in Jira or Azure DevOps in a new tab. In the Children list, the row icon for an ALM row carries the same link, so you can jump out to the provider without opening the child first.

Keyboard shortcuts

Key

Action

Esc

Close the card

Where the new card does not open

  • Program Board — items still open in the existing detail popup.

  • Solution Board — same as Program Board.

  • Risk Register — risks still open in the existing risk popup.

These surfaces will move to the new card in a later release. Until then, the old popup is what you'll see when you open an item from one of those boards.

Troubleshooting

Situation

What to check

The new card didn't open, the old popup did

You're on a surface that hasn't moved over yet (Program Board, Solution Board, Risk Register). Open the same item from a migrated surface (Org View, Kanban, Roadmap, Timeline, Strategic Themes linked items, OKR Timeline, Milestones) to see the new card.

Field edit didn't save

Click into the field again. A small indicator next to a field flags the reason on hover, usually a required-field validation, a permission missing for that field, or the ALM rejected the change.

Card is empty for an ALM item

The item may not have synced yet. Check the type pill links out to a real Jira / ADO record; if not, the ALM connection is the place to look.

Hyperlink to Jira / ADO doesn't open

Confirm the ALM account is connected in Settings → ALM accounts and that you have permission on the project.

Children added by a colleague aren't appearing

Live updates flow over the same channel the rest of Kendis uses. Refresh once if your network drops and the channel reconnects.

Full-page link doesn't work for me

The full-page route is /item/<itemId>. If the link returns an error, your account doesn't have access to the item.

Can't see the Comments / Activity tab on a Jira issue

This is intentional. Comments and activity for ALM items live in the upstream provider and aren't duplicated in the Kendis card.

Did this answer your question?