Timeline View for Strategic Themes and OKRs

The Timeline is one of two views inside a theme's OKR Roadmap. The other is the Roadmap view (swimlane schedule by objective). Same data, same drag-to-reschedule, same edit flows, same filter bar. The Timeline is the Gantt-style picture of who is delivering what, when.
​

Open a Strategic Theme and switch to Timeline view to see, on one screen:

The left panel is the tree, the right panel is the Gantt timeline. Drag a bar to reschedule. Click any row to open it for editing in the new Kendis Item card.

Your last-used view is remembered, so the next time you open the same theme it lands on the view you used last.

The tree column on the left lists everything in the theme, in this order:

Expand or collapse any row to drill into or hide its children. Linked items load lazily on first expand and stay loaded for the rest of the session.

Every row in the tree has a corresponding bar on the right, drawn between the row's start and end date.

Items without a start or end date appear as pinned pills on the left edge of the Timeline area instead of disappearing off the schedule. The pills stay visible no matter how far you scroll horizontally, so you can see what still needs scheduling.

Their tooltip shows "No Date" instead of synthetic dates, so there's no confusion about whether they have a real date or not.

Add a milestone from the Timeline header:

For ALM items appearing under a key result, the key in the left tree is a hyperlink. Click it to open the item in Jira or Azure DevOps in a new tab.

Click the row anywhere else (or right-click → View Details) to open the item in the new Kendis Item card, embedded directly in the Timeline page.

The Items filter bar lets you narrow the entire view to a slice of linked work, and the OKR tree cascades to match.

The bar applies to linked items and their children only. Objective Groups, Objectives, Key Results and Milestones are structural and are never hidden by a filter. What the cascade does instead is keep the OKR tree visible only where filtered items actually exist underneath.

The bar lives under the top header on the OKR Roadmap. The trigger is the blue Items pill at the top of the page. Click it once to expand the bar, click it again (or the chevron on the right of the bar) to minimise. The open / closed state is remembered per theme.

The bar is shared by both the Timeline and the Roadmap views, so any filter set in one view stays applied when you switch to the other.

Each facet is a dropdown. Click to open, pick one or more values, click Done to close. Selections take effect live (typing in a search box is debounced ~250 ms; chip toggles apply immediately).

The + Filter By button opens a picker of every field discovered across the theme's linked items, grouped under:

Pick a field and a new chip appears on the bar with its own dropdown of values. The values come straight from the items in scope, so the dropdown never lists a value that doesn't actually exist on any item.

Three field shapes behave differently:

You can stack as many dynamic chips as you like; they AND together with each other and with Status / Collection. Click the × on a chip to remove the facet, or the dropdown's Clear link to keep the chip but drop its values.

The search box at the top of the OKR Roadmap searches OKRs and linked items in one go. For linked items, the search runs against the primary key, ALM key, Kendis key and title fields, so any identifier you have to hand finds the item.

When you apply a filter, three things happen:

On the Roadmap view the same cascade applies to swim-lanes: a group or objective with no matching descendants is hidden, milestones and full-span headers always stay visible.

The Items pill in the top header shows the active filter count and, when a cascade is hiding rows, a small "· N hidden" annotation so you know how much the filter is taking off the view.

When you activate a filter for the first time on a theme, the timeline pre-loads every key result's linked items in the background so the cascade sees the whole tree, not just the parts you've already expanded. A small spinner appears next to the Items pill while this runs.

Filter state is saved per theme in your browser's local storage. Reload the page and the filters come back exactly as you left them, including dynamic chips, operators and values. Open the same theme on another browser or another device and you'll see the unfiltered view there until you set filters again.

The URL stays clean — old filter URLs are stripped on load so that shared bookmarks don't render as long base64 strings. A dedicated "Save View" sharing flow is a later release.

Filter options (statuses, projects, custom fields) are cached in your browser for five minutes so the dropdowns open instantly. If an admin has just changed a field template or an ALM mapping and you want to see it without waiting for the TTL, click the refresh icon on the right of the Items bar to drop the cache and re-fetch.

If a theme spans an unusually large set of Release Trains, the server caps the catalog load to keep dropdowns responsive. When that happens the bar shows a banner explaining the cap; the Assignees and other tenant-wide options still populate so the bar isn't blank. Narrow the theme's scope (or fewer collections) and the full catalog returns.

The same data renders in two ways. Switch via the toggle in the header.

The view you pick is saved, so the next time you open the OKR Roadmap you land on it directly.

Your default is set in the theme configuration. The toggle remembers your last choice.

Click the full-screen icon in the header to expand the Timeline to the full browser window. Click again to exit. Useful for screen sharing during reviews.

The Timeline supports zoom presets (day / week / month / quarter). Your selected zoom is remembered between sessions so you land in the same density next time.

The Timeline respects the same role-based permissions as the rest of the OKR area:

If you can see a row but a drag doesn't save, you don't have edit permission for that record. A short message appears at the top of the page when that happens.