When does each Epic or Feature start and finish, how far along is it, what is it waiting on, and how does that line up with our PIs?
The Collection Timeline answers those questions in one Gantt-style planning view. Choose one hierarchy level, such as Epics or Features, and see that work across weeks, months, quarters and years. Expand any parent to inspect its children, overlay PI Boards as planning bands, turn on dependency lines, and keep milestones and phases on the same chart.
The view stays connected to the work underneath it. It reads the dates and fields Kendis holds from Jira or Azure DevOps, shows ART planning alongside those dates, and can write date changes back when you move work on the timeline.
At a glance
With the Collection Timeline you can:
Turn backlog items into a time-based plan at one hierarchy level, with children available on demand.
Compare item dates with ART planning by showing actual dates and planned PI sprint dates together.
See progress in context with roll-up bars that calculate completion from the work underneath them.
Keep unscheduled work visible on the start line instead of letting items without dates disappear from the plan.
Overlay PI Boards as bands so increment boundaries are visible against the work itself.
Show dependencies, milestones and phases on the same planning surface.
Move or resize bars to change dates, with supported changes written back to Jira or Azure DevOps.
Create different planning views with grouping, Multi Group, filters, sorting, search and mapped ALM fields.
Move from week-level detail to a multi-year view without losing the overall shape of the plan.
Contents
Key terms
Where to find the Timeline
Create a timeline
Manage your timelines
Read the timeline
What a bar represents
Items without dates
Progress, colours and labels
Columns
Zoom and move around
Change dates from the timeline
Open an item
Add and remove items
Search, filter and sort
Group the timeline
Show PI boards as bands
Dependencies
Milestones and phases
Settings
Fiscal calendars on the time axis
Keep the timeline current
Permissions
Limits and recommended practice
Which timeline should I use?
Troubleshooting
1. Key terms
Term | What it means |
Collection | The workspace that holds a backlog: an ART, a solution train, a portfolio, a department, or any custom type your company has defined. |
Timeline | One Gantt-style view of one hierarchy level of a collection. A collection can have many timelines. Each has a key such as TL-3. |
Hierarchy level | The level of item a timeline charts, for example Epic or Feature. Fixed when the timeline is created. |
Bar | One item drawn from its start date to its end date. |
Roll-up bar | The bar of an item that has children. It is tinted and shows a progress fill and a percentage. |
By ART Planning | The span of the PI sprints an item or its children are planned into. Drawn as a baseline under the bar, or used as the bar itself when you choose planning mode. |
Start line | The left edge of the chart where items without dates are pinned so they stay visible at every zoom level. |
Fit | The zoom level that frames every dated item in the visible area. |
PI band | A shaded span on the chart marking the first and last sprint of a PI board you have chosen to show. |
Milestone / Phase | A dated marker (milestone, a diamond) or a dated range (phase, a bar) kept in the Milestones section at the top of the chart. Items can be linked to them. |
Manage Timeline | The collection permission needed to create timelines, change settings, add items and edit dates. |
2. Where to find the Timeline
Open a collection and select Timeline in the left navigation. This opens the collection's timeline workspace, where you can create separate views for different audiences or hierarchy levels.
The Timeline View page lists the timelines of that collection. Select a timeline's name to open it.
While a timeline is open:
the breadcrumb reads collection type > collection > Timeline > timeline name,
the browser tab shows the timeline key,
and the collection's left menu is hidden to give the chart the full width. It returns when you leave the page.
The Timeline entry appears when the Timeline module is enabled for the collection. If you cannot see it, ask the collection's administrator to check the collection's module configuration.
Anyone with a role on the collection can open its timelines. Creating and editing needs the Manage Timeline permission. See Permissions.
3. Create a timeline
You need the Manage Timeline permission on the collection.
Open the collection's Timeline page.
Select Create Timeline.
Enter a title under Enter Timeline Title. Up to 60 characters.
Choose what the timeline shows:
All Items: every item of the chosen level in this collection.
Select Filter: only the items a saved filter returns. Choose the filter under Select Filter. The list offers No Filter, your Shared filters and My filters from the Backlog, and your tool's own saved searches under Jira Filters or Azure DevOps Queries.
Choose the Select Hierarchy Level. The top level of the collection is pre-selected.
Select Save Timeline.
Kendis opens the new timeline straight away.
Each timeline is intentionally focused on one hierarchy level. If leadership needs an Epic view and the ART needs a Feature view, create a timeline for each rather than forcing both conversations onto one chart.
If this is the collection's first timeline, the page shows Create Your First Timeline with the same Create Timeline button.
Tip: start broad. Create the timeline with All Items at the collection's top level, then narrow the working view with filters and grouping. Children are always one expand away.
4. Manage your timelines
The Timeline View page lists each timeline with its Key, Name, Created By and Created On. Select a column heading to sort by it.
Action | Where | What it does |
Search | Search box above the list | Matches key, name, creator or creation date |
Rename | Pencil icon beside the name | Edits the name in place. Up to 60 characters |
View Timeline | Row menu | Opens the timeline |
Archive Timeline | Row menu | Hides the timeline from the list after confirmation. Nothing on the items changes |
Show Archived / Hide Archived | Page settings menu, titled Manage Boards | Switches the list between active and archived timelines. The heading gains Archived while archived timelines are shown |
Unarchive Timeline | Row menu on an archived timeline | Restores it to the active list |
Rename, archive and unarchive need the Manage Timeline permission. Other users see the list without those controls.
5. Read the timeline
The timeline combines two views of the same work: a planning grid on the left and a time-based chart on the right. Each row and bar represent the same item, so you can read fields and hierarchy while also seeing timing, duration and overlap. Drag the divider to give either side more space.
5.1 Rows
From top to bottom:
Milestones (n). A collapsible section holding the milestones and phases linked to this timeline. Users who can add milestones also see + Add here. Kendis remembers whether you left this section open or closed.
A level divider, for example Features (12), naming the timeline's level and counting the top-level rows.
Item rows, one per item at the timeline's level. A row with children has an expander. Children load when you first expand them, and each child can be expanded in turn.
Load More N at the bottom when the collection has more items than the page shows. Rows load 50 at a time.
When you group the timeline, group rows replace the level divider. See Group the timeline.
5.2 The time axis
The header has three rows at every zoom level, for example year, quarter and month. When your company uses a fiscal calendar, the labels follow it, such as FY26 and Q3 FY26. See Fiscal calendars on the time axis.
A pink line marks today, with the date shown in the header, for example 17 Oct.
When a multi-year timeline is squeezed into the view, the lowest header row hides its labels rather than overlap them.
5.3 Hover a bar
Hovering a bar shows a card with the item key and title, Start Date and End Date, the item's Completion as a percentage with the done and total counts, its Status, and Teams and Sprints it is planned into.
To see which PI boards the item is planned on, hover its planning baseline instead. That card also lists the Boards. See Dates versus planning.
Hovering a row's title shows KEY: Title in full.
6. What a bar represents
A bar represents where an item sits in time. By default, it runs from the item's Start Date to its End Date, using the dates Kendis syncs from Jira or Azure DevOps or the dates stored on a Kendis-only item.
An item that starts and ends on the same day is drawn as a one-day bar so it stays visible.
6.1 Dates versus planning
The timeline can show two different planning signals for the same item:
Actual dates: the item's own Start Date and End Date.
Planning dates, labelled By ART Planning: the first sprint start and last sprint end of every PI sprint the item, or any of its descendants, is planned into.
The Select the Bar Type setting decides how the two are shown:
Option | Bar | Baseline |
Show Both (Date & Planning) | Actual dates. If an item has no actual dates but is planned into sprints, its planning dates are used instead | The planning span is drawn as a lighter baseline under the bar |
Show By Date | Actual dates only | None |
Show By Planning | Planning dates only. Bars cannot be dragged or resized in this mode | None |
A new timeline uses Show By Date.
Hovering a baseline shows the same card as the bar with the footer Based on current ART planning.
6.2 Azure DevOps iteration dates
For Azure DevOps collections, two further settings control whether iteration paths supply dates:
Azure DevOps Iteration Path Dates: Use Start and End Dates from Iteration Paths or Don't Use Iteration Path Dates.
Date Preferences, shown when iteration dates are in use: Prefer Start and End Date Values or Prefer Iteration Path Dates. This decides which wins when an item has both.
The iteration dates come from the iteration path on the work item and on its children.
6.3 Group bars, milestones and phases
A group row spans from the earliest start to the latest end of the items in it, drawn as a thin rail in the group's colour.
A milestone is drawn as a diamond on its date.
A phase is drawn as a bar from its start date to its end date.
7. Items without dates
Unscheduled work should not disappear simply because it has no dates yet. The timeline keeps it visible and makes that missing planning decision obvious.
An item with no usable dates is drawn as a grey, dashed pill pinned to the start line at the left edge of the chart. The pill stays at the left edge as you scroll and zoom, and keeps the same minimum width so it reads the same at every level. Its hover card shows blank dates.
Undated children follow their parent:
if the parent has dates, the child sits as a short pill at the parent's start,
if the parent is itself pinned to the start line, the child is pinned beneath it.
Undated items never distort the chart. They are left out of Fit, sort to the bottom of their level, and do not stretch a parent's roll-up span.
To hide undated items' bars altogether, set Items without Dates to Don't Show in Settings. The rows remain in the grid.
To give an undated item dates, drag its pill to where it belongs. The Edit Item popup opens with the dropped dates filled in, and Cancel returns the pill to the start line. See Change dates from the timeline.
8. Progress, colours and labels
8.1 Status colours
Bars are coloured by the item's status category:
Category | Colour |
To Do | Orange |
In Progress | Blue |
Done | Green |
Any other category, or no status | Purple |
An item with its own colour set in Kendis keeps that colour instead.
8.2 Roll-up bars and the percentage
Parent items become roll-up bars, so the timeline shows not only when the work is planned but also how far through it you are. The bar uses a pale status tint with a solid completion fill and a percentage such as 64%. Leaf items remain solid bars without a roll-up percentage.
The % control in the toolbar chooses how completion is calculated:
Mode | How it counts |
By Rollup (Status) (default) | Every item in the subtree counts once. Completion is done items over all items |
By Rollup (Estimate) | The same, weighted by story points. An unestimated item without children counts as one point |
By Done Children (Status) | Only the direct children's statuses are counted |
Items in a miscellaneous or unmapped status category are excluded from the count. The hover card shows the same figure as Completion with the done and total behind it.
Your choice of mode is remembered for this timeline in your browser.
8.3 Bar labels
By default each bar carries its key and title in white. When the bar is too short for the text, the label sits to the right of the bar instead. Long titles are shortened.
Turn labels off with Show Item Label on Bars in Settings.
9. Columns
The grid can show these columns. Title is always present.
Column | What it shows |
Title | Item key, linked to Jira or Azure DevOps where the item lives there, the item type icon and the title. The header also holds the Show manually added items only checkbox |
Status | A coloured dot and the status name |
Counts | For a parent: the number of direct children followed by a dot and count per bucket. Grey for to do, amber for selected, blue for in progress, green for done. Hover for To Do, In Progress and Done counts |
Estimate | A leaf's story points. For a parent, its own points and the rolled-up total, split by bucket |
Program Boards | PI boards the item or its children are planned on, as prefix pills. One is shown, the rest behind +N |
Teams | Teams with an initial avatar in the team colour. Two are shown, the rest behind +N |
Sprints | Sprints the item is planned into |
Solution Boards | Solution boards the item appears on |
Start Date / End Date | The item's dates |
Dependencies | The number of dependency links, or + when there are none. Select it to see the list |
Area Path / Iteration Path | Azure DevOps collections only |
Mapped fields | Any Jira or Azure DevOps field mapped for this hierarchy level |
Choose and arrange columns
Columns n/m in the toolbar opens Settings on the Columns tab, where you add, remove and reorder the columns for everyone who uses this timeline. See Settings.
Drag a column heading to reorder columns for yourself. Kendis remembers your order in this browser.
Drag a heading's edge to resize it. Widths are not saved.
10. Zoom and move around
10.1 Zoom levels
The Zoom group at the top right has - and + buttons and a segmented control: Week, Month, Quarter, Year and Fit.
Fit frames every dated item in the visible area and is the default when you open a timeline. It is also applied again when the fiscal calendar finishes loading. Undated items are ignored when fitting.
Week, Month, Quarter and Year set the scale and then centre the chart on today. If today lies outside your data, the chart scrolls to the start of the data instead.
- and + step one level at a time through the same ladder, so the header always shows the same kind of rows. Two further steps beyond Year compress a very long timeline until the whole board is in view.
Ctrl and the mouse wheel zoom too, and the segmented control follows.
Zoom changes the level of detail, not the scope of the data. The axis continues to span the work on the timeline, so long-range items remain reachable.
Your zoom level is remembered for this timeline in your browser.
10.2 Moving around
Scroll the chart horizontally to move through time. The grid and chart scroll together vertically.
There is no separate Today button. Choosing any of Week, Month, Quarter or Year brings today to the centre, and the pink today line marks it.
11. Change dates from the timeline
You need the Manage Timeline permission, and the bar type must not be Show By Planning.
When the plan changes, you can adjust dates directly from the timeline in three ways:
select a bar,
drag a bar to a new position,
drag a bar's right edge to change its end.
Each opens the Edit Item popup for that item. Under Set Date you see Start Date and End Date, pre-filled with the dragged position when you dragged. Adjust either date and select Save, or Cancel to put the bar back where it was.
Both dates are required, and the start must be before the end. Otherwise Kendis says Start date/End date is missing or Start date must be smaller than End date.
What happens on save
The item's Start Date and End Date are saved in Kendis and the bar moves.
For an item that lives in Jira or Azure DevOps, Kendis writes the new dates to the tool as well. The loader names the tool while this happens.
Parent roll-ups are not changed by a date edit. Roll-up progress follows status and estimate, not dates.
Milestones and phases have their own date popup. See Milestones and phases.
12. Open an item
Select an item's title in the grid to open it in a side pane on the right. The pane shows the full item card: fields, children, links, comments and history, with the same permissions as anywhere else in Kendis.
Drag the pane's edge to resize it. Kendis remembers the width.
Changes you make in the pane, such as status, title, dates, assignee or colour, are applied to the row and bar immediately.
A child you create or link in the pane appears under its parent on the timeline.
Select the item's key instead to open it in Jira or Azure DevOps in a new tab.
13. Add and remove items
13.1 What the timeline shows
A timeline created with All Items shows every item of its level in the collection. A timeline created with a filter shows the items that filter returns.
In both cases you can also add individual items by hand, and the timeline shows the union: filter results plus hand-added items.
Tick Show manually added items only in the Title column header to see only the items you added by hand.
13.2 Add an item
You need the Manage Timeline permission.
Select Add at the right of the toolbar. The Add Items popup offers:
a search box, Search item from backlog, to find an existing item of this level in the collection and add it,
Create New to create a new item with the title you typed,
Add From JIRA or Add From Azure DevOps to import items from your tool.
The item is added to the timeline and its row appears with its roll-ups.
13.3 Remove an item
Right-click a bar and choose Remove this item from timeline. Confirm Are you sure you want to remove this item from Timeline?
This only removes the item from the timeline's hand-added list. The item itself is untouched.
The option is offered only for items you added by hand. An item shown because of the timeline's level or filter cannot be removed this way. Change the filter instead.
14. Search, filter and sort
14.1 Search
Type in Search... and press Enter. The grid keeps only items whose key or title match.
14.2 Filters
Filters uses the same filtering model as the Backlog, so a timeline can become a focused planning view without creating another copy of the work. A count badge shows how many conditions are active.
Build conditions on any field and Apply to filter what you see.
Choose a saved filter under Select Filter to apply it. Applying a saved filter that differs from the timeline's current one makes it the timeline's filter for everyone who opens the timeline.
A Backlog saved filter shows its condition count and the note This is a Backlog filter. Its conditions are managed in the Backlog and applied here as saved. Edit it in the Backlog.
Reset removes the filter. Because the filter decides which items the timeline shows, Kendis asks first: Do you want to remove the filter from timeline? Doing so will also cause all filter items to be removed from timeline.
When nothing matches, Kendis says No records found matching your search or filter settings.
14.3 Sort
Select the heading of Title, Status, Start Date, End Date or a mapped field to sort by it. Select again to reverse. An arrow marks the active sort.
The default order is by date, earliest first, with undated items last.
Children are sorted by date within their parent.
The sort is part of the page address, so a shared link opens with the same order.
Reset Sorting in the toolbar returns to the default.
Sorting is unavailable while the timeline is grouped.
14.4 Manual order
Drag a row up or down within its parent to reorder it. The new order is the collection's own backlog order, so it is shared with every view of the collection.
Right-click a top-level bar and choose Send Item to Top to move it to the top for the current session.
15. Group the timeline
15.1 Group By
Grouping changes the conversation without changing the underlying work. Choose a dimension under Select Group By:
No Group
Parent
Program Boards
Batches
Milestones
Teams
Sprints
Solution Boards
Status
Kendis Responsible
JIRA Responsible or DevOps Responsible
For Azure DevOps: Project, Area Path, Iteration Path
Any mapped Jira or Azure DevOps field
Each group becomes a collapsible row with a colour square, name and count. Groups are ordered by the earliest start date of their items. Items that do not belong to any group collect in a final grey row such as No Parent or No Team.
Expand a group to load its items. Group bars span the items inside them.
Your grouping is remembered for this timeline in your browser.
15.2 Multi Group
Multi Group opens Select Groups, where you can:
choose a Select Group By for each hierarchy level, so Epics can be grouped one way and their Features another,
add a +Subgroup inside a group for a second grouping level,
Save as a named configuration, Shared with the collection or Private to you, and Update it later,
Apply, Reset or Cancel.
A saved configuration is part of the page address, so a shared link opens with the same grouping.
16. Show PI boards as bands
PI bands let you see increment boundaries against the dates of the work. Select Select Boards in the toolbar; when boards are already chosen it reads N Selected.
In the panel:
Pick a Select Collection. Any collection you can see is offered.
Pick one or more PI boards under Select Boards.
Remove a board by closing its pill.
Select Save.
Each selected board appears as a lightly shaded band from its first sprint's start to its last sprint's end, with a dark header pill naming the board and its prefix. Boards whose sprints have no dates draw no band.
The selection is saved on the timeline and shared with everyone who opens it.
17. Dependencies
Turn on Dependencies when the timing of one item depends on another. The toolbar button shows or hides the dependency lines and stays green while they are visible.
Lines are drawn in red from the item that is waiting to the item it waits for.
A line appears only when both ends are loaded on the timeline. Expand parents or load more rows to reveal more lines.
A bar with dependencies carries a small red badge with the count.
Hover a line to see both items and the link type. Select a line to open the dependency and edit or delete it.
The Dependencies column shows the count per item. Select it, or the + when there are none, to open the item's dependency list.
Dependencies cannot be created by dragging between bars. Create them from the item's dependency list.
Your choice to show or hide lines is remembered for this timeline in your browser.
18. Milestones and phases
The Milestones (n) section at the top holds the milestones and phases linked to this timeline. Milestones are diamonds on a date. Phases are bars over a range. Each carries a label chip with its key and title, and hovering shows its dates and status.
Add
Select + Add on the Milestones row:
Create Milestone/Phase opens the milestone form.
Add Existing links milestones or phases that already exist in the collection.
Kendis confirms with Milestone(s)/Phase(s) added successfully. An archived milestone cannot be linked, and Kendis says so.
Edit dates
Select a milestone or phase, or drag it, to open Edit Milestone or Edit Phase. Set the Milestone Date, or the Start Date and End Date for a phase, and Save. This needs the Edit Milestones/Phases permission.
Link items to a milestone or phase
Right-click an item's bar and open Link to Milestone / Phase. The submenu lists each milestone with its key, title and date. Choose one and confirm Are you sure? with Yes. Tick Don't ask me again to skip the confirmation next time.
Milestones the item is already linked to are not offered again.
Group by milestone
Choose Milestones under Select Group By to see items grouped under the milestones they are linked to.
19. Settings
Select Settings at the top right. The modal has two tabs. Everything in it is saved on the timeline and applies to everyone who opens it. After Save, Kendis reloads the page so the new settings take effect.
General Settings
Setting | Options | Shown |
Azure DevOps Iteration Path Dates | Use Start and End Dates from Iteration Paths, Don't Use Iteration Path Dates | Azure DevOps collections |
Date Preferences | Prefer Start and End Date Values, Prefer Iteration Path Dates | Azure DevOps collections using iteration dates |
Select the Bar Type | Show Both (Date & Planning), Show By Date, Show By Planning | Always |
Items without Dates | Show Bars (At the Start Line), Don't Show | Always |
Show Item Label on Bars | Show Labels, Hide Labels | Always |
See What a bar represents, Items without dates and Progress, colours and labels for what each option does.
Columns
Select Columns lists the columns currently shown. Title cannot be removed.
Drag the handle to reorder.
Use the dropdown on a row to swap it for another column.
Select the cross to remove a column.
Add a column offers every column not yet shown.
What is yours alone
These are remembered in your own browser, not on the timeline:
zoom level,
dependency lines on or off,
the % completion mode,
your column order,
Group By and Multi Group selection,
whether the Milestones section is open,
the side pane width.
The sort order lives in the page address instead, so it travels with a shared link.
20. Fiscal calendars on the time axis
If your company has set up a fiscal calendar, the timeline's header follows it.
The calendar attached to the collection is used. If there is none, the company's default calendar applies.
Quarter and year bands start on the fiscal start month and carry the calendar's own names, for example Q3 FY26 and FY26. A fiscal year is named for the calendar year in which it starts.
Without a fiscal calendar, or with one that starts in January, the header shows calendar quarters and years such as Q1 2026 and 2026.
Week-based 4-4-5 calendars are shown with calendar quarters and years.
The calendar loads as the timeline opens. If it arrives after the chart has drawn, the header is redrawn and Fit is applied again.
21. Keep the timeline current
The timeline is another view of the same collection data used by the Backlog. Kendis keeps that data current through the Jira or Azure DevOps sync, so the timeline can open quickly without querying the external tool every time.
Dates you change on the timeline are written back to the tool straight away.
Edits in the side pane update the row and bar immediately.
Changes made by other people, or arriving through sync, appear when you reload the page.
If a milestone's field is changed elsewhere while you have the timeline open, a banner tells you which field changed and offers Reload to see it.
22. Permissions
Permissions come from the user's role on the collection. Company administrators have every permission. Guest users cannot open the timeline and see You do not have access.
Action | Who can do it |
Open the Timeline page and any timeline, zoom, search, filter the view, group, sort, change the % mode, reorder columns, toggle dependencies, open items | Anyone with a role on the collection |
Create, rename, archive and unarchive timelines; change Settings and Select Boards; add and remove items; drag, resize or select bars to edit dates; reorder rows; apply a saved filter to the timeline | Users with Manage Timeline |
+ Add on the Milestones row | Users who can add milestones |
Edit a milestone's or phase's dates | Users with Edit Milestones/Phases |
Link items to milestones and phases | Users who can link items to milestones |
Opening an item in the side pane uses the item's own permissions. A user who can view the timeline but not edit the item sees it read-only in the pane.
23. Limits and recommended practice
Limits
A timeline shows one hierarchy level. Create another timeline for another level.
Timeline names are limited to 60 characters.
Rows load 50 at a time. Load More N fetches the next 50.
Children load when a parent is expanded, and group contents load when a group is expanded.
Bar labels are shortened to about 60 characters. Hover for the full text.
Dependency lines need both items loaded on the timeline.
Column widths are not saved. Column order, zoom, grouping and the % mode are saved per browser.
There is no export or print button on this page.
Recommended practice
One timeline per level, named for its audience, for example Epics for leadership and Features for the ART.
Start with Fit, then pick a level. Fit tells you the shape of the whole board. Quarter or Month is where you work day to day.
Keep Show Both on when planning is in flux. The baseline shows whether the dates on the item agree with where the work has actually been planned.
Use the start line as a to-do list. Every pill on the left is an item nobody has scheduled yet. Drag it into place when you know.
Overlay the PI boards you are tracking. Bands make it obvious when an epic's dates straddle an increment boundary.
Group by Teams or Program Boards before a planning session, then switch back to No Group to sort by date.
24. Which timeline should I use?
Kendis has several time-based views. The right one depends on the planning question you are trying to answer.
View | Use it when the question is |
Collection Timeline (this guide) | When does each epic or feature in this collection start and finish, how complete is it, what does it depend on, and how does that sit against our PIs? |
Collection Roadmap | How does our planned delivery look by theme or section over the coming quarters? The Roadmap arranges items in sections and has a period navigator for quarters, halves and years. |
PI Roadmap | When do our Program Increments themselves run, across collections, on a fiscal calendar? It charts PIs, not backlog items. |
OKR Timeline | When do our objectives and key results run, and what work is linked to them? Found under Strategic Themes. |
Solution Timeline | How do the epics and features of one solution board lay out across its Solution Increments? Opened from a Solution board's menu. |
PI board Timeline View | How does one PI's work lay out sprint by sprint? Opened from a PI board's menu. |
25. Troubleshooting
Symptom | Why it happens | What to do |
Timeline is missing from the collection's navigation | The Timeline module is not enabled for this collection. | Ask the collection administrator to enable it in the collection's configuration. |
You do not have access when opening a collection | You have no role on the collection, or you are a guest user. | Ask the collection administrator for a role. |
Create Timeline, Add, Settings or the row menus are missing | Your role does not include Manage Timeline. | Ask the collection administrator to review your role. |
Selecting or dragging a bar does nothing | You do not have Manage Timeline, or the bar type is Show By Planning. | Check your permission, or switch Select the Bar Type to Show By Date or Show Both. |
The chart looks empty after opening | Your data is far from today and the view is on a level other than Fit, or every item is undated. | Select Fit. Check the start line for grey pills. |
An item sits in a grey pill on the left edge | It has no start or end date, and no planned sprints to borrow from. | Drag the pill to where it belongs and save, or set dates on the item. |
An item's bar does not match its Start Date and End Date | The bar type is Show By Planning, or the item has no actual dates and is showing planning dates, or Azure DevOps iteration dates are preferred. | Check Select the Bar Type and the Azure DevOps date settings. |
A parent bar shows 0 % although children are done | The % mode is By Done Children (Status) and the done work is deeper than one level, or the done items are in an unmapped status category. | Switch to By Rollup (Status), or check the status mapping. |
No dependency lines appear | Lines are hidden, or the other end of each link is not loaded. | Select Dependencies, then expand parents or Load More N. |
Remove this item from timeline is not offered | The item is on the timeline because of its level or the filter, not because it was added by hand. | Change the filter, or tick Show manually added items only to see which items can be removed. |
No records found matching your search or filter settings | The search or filter matches nothing, and there are no milestones. | Clear the search, or open Filters and Reset. |
Please select a hierarchy level or Please enter a valid name | The create form is incomplete. | Fill in the title and choose a level. |
Start date/End date is missing or Start date must be smaller than End date | The Edit Item popup needs both dates in order. | Correct the dates and save. |
Applying a saved filter changed what other people see | A saved filter applied on the timeline becomes the timeline's filter for everyone. | Apply ad hoc conditions instead when you only want to narrow your own view. |
The header shows calendar quarters although the company uses a fiscal year | The calendar starts in January, or it is a week-based 4-4-5 calendar. | Expected behaviour. Quarter and year bands follow the calendar only for month-based calendars that do not start in January. |
Sorting by a column is not possible | The timeline is grouped. | Set Select Group By to No Group first. |
You are not allowed to perform this action when editing a milestone | You lack Edit Milestones/Phases. | Ask the collection administrator. |
A milestone cannot be added: is archived and cannot be linked with this board | The milestone is archived. | Unarchive it in the collection's milestones, then add it. |
Someone else's change is not showing | The timeline does not refresh on its own for other people's edits. | Reload the page. |
A practical way to use the Collection Timeline
A useful timeline should support a planning conversation, not become another reporting artefact. For most programmes, this is a good starting rhythm:
Create one timeline per audience and level. An Epic-level timeline works well for broader planning; a Feature-level timeline gives the ART more detail.
Start with Show Both (Date & Planning). This makes gaps between item dates and current ART planning visible immediately.
Keep undated work on the start line. Treat those grey pills as explicit planning decisions still to be made.
Overlay the PI Boards that matter. The shaded bands make it easy to see work that crosses increment boundaries or no longer fits the plan.
Begin reviews on Fit, then move to Quarter or Month. Fit gives the shape of the whole plan; the closer zoom levels are where scheduling decisions happen.
Turn on dependencies before planning discussions. A date can look reasonable until you see the item it depends on finishing later.
Group for the question you are asking. Use Teams to discuss ownership, Program Boards to discuss PI scope, or mapped ALM fields for product- or domain-specific views.
Move work when the decision is made. Drag or resize the bar, confirm the dates, and let Kendis write the supported change back to Jira or Azure DevOps.
The backlog remains the source of the work. The Collection Timeline turns that same work into a shared view of timing, planning and dependency risk.


















