Selected fields of selected tracker items are shown in a specific order in a tree table, which is a table, where items, that are parent of other items, can be expanded, to also show the children (recursively).
Here the focus is on the tracker. The whole tracker is regarded as a document and the tracker items are the document paragraphs. The tracker item hierarchy represents the document outline and each item has a defined position within that outline.
Here the focus is on work in progress, therefore this format is only applicable for work items. Work items are presented in form of a Kanban Board, where work items are shown as cards in columns representing work status.
A tracker view is always associated with exactly one (defining) tracker, but (public) views of template trackers are inherited by derived trackers and also applicable there.
A tracker view can only narrow the field of vision (to a subset of tracker items and a subset of item attributes). It is not possible to join information from other (related) trackers.
Tracker Views (Report based)
Report based Tracker Views are available only from codeBeamer 9.0.0
From codeBeamer 9.0.0 you are able to define report based Tracker Views on Table View, Document View and Cardboard View. All of these three views contains the new Filter Widget in which you can define specific filters by the tracker's fields or other options, group by / order by options, the same way as you can do on the Report page. The set filters can be saved as Tracker Views (public or private) and can be used on Table View, on Document View or on Cardboard View.
See more information about the Filter Widget and managing Tracker Views here: Trackers
Tracker Views (old)
From codeBeamer 9.0.0 old Tracker Views used only for the following functionalities:
Escalation View - for Escalation rules
Reference Filter - for settings of a tracker's reference field
There are a number of implicit views, that are available when browsing items in a tracker, e.g.
(All) Open (items)
All top-level items
Open top-level items
This view shows all deleted items in this tracker and allows to restore them.
This view is only available for administrators.
All of these implicit views present a subset of items as a (tree) table.
The columns of these implicit table views consist of all tracker fields marked as list(able), where the current user has Default read access:
The field access is Unrestricted
The field access is Single and the role of the user has read access
The field access is Per Status and the role of the user has Default read access
You can neither modify nor delete these implicit views.
You can also define additional/explicit views on tracker items, e.g. via New View in the context menu of a tracker:
Per default the new view will be a Table view, but you can change the Layout of the new view:
Each view must have a unique Name (within it's scope).
The view Description is optional, but can be helpful when selecting views.
Views marked as Public are available to all project members, views that are not Public are private views of the user, that created them.
Only tracker administrators can Save or Delete views marked as Public.
But all users with access to a tracker can create a private version of a Public view:
Edit a public view and
Save as a private view with the same name.
Private views hide public views with the same name. To access the (hidden) public view, you must delete your private view.
For explicit (Table) views, you can define, which tracker fields to show as table columns:
The selected field will be added as last column, but you can change the column order via drag-and-drop.
All or selected columns can also be removed from the view (hidden) via the column context menu (right click on a column header):
If no columns are selected, then by Default all tracker fields marked as list(able) will be shown in their definition order.
For explicit (Table) views, you can define, by which fields the table rows (items) should be sorted:
By Default items/rows are sorted descending by item id (newest items first), but you can choose an explicit sorting:
Newly selected sort fields will be added at the end, but you can change the position (precedence) of sort fields via drag-and-drop and also remove sort fields via their context menu (right click on a sort field).
If multiple sort fields are selected, the precedence is from left to right.
You can sort by fields that are not shown as columns, although this is not recommended, because confusing for the viewer.
You can toggle the sorting direction of a sort field by (left) clicking on the direction indicator/icon of a sort field:
Ascending (arrow up)
Descending (arrow down)
The view condition defines, which tracker items are visible via this view.
By Default all (non-removed) items of the underlying tracker are visible, but you can restrict this to a specific subset.
The condition is a tree in Polish notation, to avoid the need for parentheses or other brackets: The operators and, or and not must be the parents of their operands.
Priority IN ("High", Highest") AND (StartDate > today OR EndDate <= EndOfNextWeek)
will be defined like this:
To add a new criteria to the condition tree, select either a grouping operator or the criteria field from the condition selector.
The new criteria will be added as new child node to the currently selected operator node.
You can move nodes to other locations in the tree via drag-and-drop.
You can copy criteria (including descendants) by pressing Ctrl and dragging a node to the new location where to create the copy.
You can edit condition criteria either via double-clicking on the appropriate node or by right-clicking on the node and choosing Edit from the context menu.
You can remove condition criteria by right-clicking on the appropriate node and choosing Remove from the context menu.
For some tracker stereotypes, there are also hard-coded views, which cannot be configured or changed.
These hard-coded views rely on a predefined tracker configuration (fields, states, transitions, choice options).
Modifying this predefined tracker configuration will in the best-case have no effect, in the worst-case (test related trackers) break the hard-coded views.
Both predefined and custom views can be duplicated.
Duplicate views do not modify but create a new view, it can be useful when you don't have the rights to change an existing view.
Set views as Default
Views can be Set as default per Tracker, when you set a view as default it will be the selected view when you visit the tracker.
You can unset a default view the same way as you set them.