|Tracker Views #815542/HEAD / v223|
Tags: not added yet
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.
Table of Contents
Filter Widget on Tracker Table View is available only from codeBeamer 9.0.0.
From codeBeamer 9.0.0 you are able to use the new Filter widget, you can use here the same filters as on the Reports page, but only for the actual tracker.
Parts of the Filter Widget
In tracker's Table View, you can add filter / group by / order by options using drag&drop. Drag one of the field label of the header of the issue list table, and drop one of the area of into the Filter Widget (Filters, Group by, Order by).
Manage Tracker Views Menu
From codeBeamer 9.0.0 you can manage (save, edit, delete) tracker views using the View Menu.
Please note, that the views of the earlier codeBeamer versions are not displaying here and not supported in Tracker Table View any more.
Click on the name of any view to load it. The saved filters, group by / order by options of the view will loaded into the Filter Widget and also, the issue list will reload according to the selected filters.
From codebeamer 21.04 the Manage Tracker Views menu changed. The views will display in a tree structure. See more information here: Organize Public Views
From codeBeamer 9.3.0, you can resize columns in the Table and Document Edit views. To resize columns, click the icon in the top right-hand side corner. When the view configuration window opens, select the checkbox in the Resizable Columns field:
You can now use the resizers to set the desired width for each column. It is only possible to change column widths for custom views, thus, you will need to create at least one custom view if you want to resize the width of the displayed columns. The width values are stored for each column (in terms of percentages) for the current view, which means that you need to save the modifications once the column width values are set.
From codeBeamer 10.1 you can use pixel-based resizable columns. Click on the Manage Views icon and you can choose the between the percent-based (as previously) and the new pixel-based resize columns options.
Using this option, the cell contents of the table will be cropped If you select pixel-based option and save the View, the column widths will be stored in pixels, horizontal scrollbar can appear.
Using percent-based resizable columns, you can add maximum 18 fields to the table. Pixel-based resizable columns does not have such restriction.
This functionality is also supported for Reports and in Document Edit View.
Save new View
Once you saved a custom view, you can manage the view using the upper action bar of the View Menu (Save, Save as..., Properties, Delete) or using the pencil / delete icons near the name of the views. If you select a Public View, you have the ability to set view as default view for the tracker by clicking the Set View as Default button near the name of the Current View.
From codeBeamer 10.0.0 you can set role based permissions for Tracker Views. The permission handling is similar as on Report page, except you cannot select the project, the roles of the current tracker's project will listed in the Save View overlay.
In this example you set READ permission for the users in Tester role for your own private view, therefore this view will be listed for Tester roles too as a Private View.
View accessability regarding the permissions is working as follows:
Show Ancestor and Descendant Items
You can also include ancestor (parent) and descendant (child) items of the tracker items in a new view. To include ancestor and/or descendant items in a view, select one of the following menu options when creating a new public or private view:
The new view will now display parent and child items of the tracker items:
The Show Ancestor Items and Show Descendant Items options are available in the Table View, Document View and Document Edit View.
If the Always Show Ancestor Items option is selected in User Preferences (see Displaying Ancestor Items by Default in Document and Document Edit View), the Show Ancestor Items option will be disabled in the View Menu in the Document and Document Edit Viewof a tracker:
If the Show Ancestor Items or Show Descendant Items option is selected, it is not possible to use the Group by or Order by functions.
In case the Show Ancestor/Descendant Items option is selected, and you are using a filter in your tracker view, child or parent items of work items will be displayed even if they do not match the filter criteria. For example:
In this example, we are filtering tracker items based on the Status: In progress value. However, as the Show Ancestor Items option is specified for this view, two parent items are also displayed even though they are in New status.
Parent/child items that do not match the filter criteria are displayed with a light red background.
From codeBeamer 10.0.0 you can use the "Show Children" option for displaying the child items as in the previous versions (< 9.5.0).
If you check Show Children checkbox, an arrow will appear before the name of the item. By clicking the arrow, the child items will load under the parent item. If some of the child items do not match the selected filter, they will get a light read background, otherwise the background of the child items will be light orange.
Filter Widget on Baseline mode
From codeBeamer 10.0.0 you can use the Filter Widget in Baseline mode of the Tracker. The result list will display versioned items, and the links of the items will point to the Baseline version of the Tracker Item. You can use Group by / Order by or Show Ancestor / Descendant items functionalities in Baseline mode also.
Some restrictions regarding the Baseline mode:
From codeBeamer 9.0.0 you can manage easily the fields of the issue list. You can add / move / remove fields, and the displaying field list is stored if you save a custom Tracker View.
Add new field
To add a new field into the issue list click one of the context menu of the header where you would like to add the field and select Add Column option. A submenu will appear where you can select which field you would like to add. The fields are grouping the same ways just on the Report Page and in the Filter Widget: Default Fields, Common Reference Fields and custom fields (Project - Tracker). If a field is already in the issue list, it will be appear with grayish color and cannot be add to the current issue list once more.
From codeBeamer 10.1 you are able to add Shared Fields to the layout, see details here: Reports
Move / Remove fields
For moving fields within the issue table, use one of the context menu Move left or Move right options or drag the label of a field and drop in an other position. While dragging, a green vertical line will help you, where you can drop the field.
Additionally, you can drop the dragged field into the Filter Widget also, in this case, the field remains in its current position, but a filter / group by / order by option will be added into the Filter Widget.
For removing a field, select Remove Column option of one of the header's context menus.
Paging - Show More../Show Less.. buttons
Table based layouts can extend the number of the Tracker Items per page:
Provided layouts: Simple Table View, Report page, Reference Selector, CBQL Table Widget (but we have to implement everywhere where is the Show More.. button).
Intelligent Table View
An Intelligent Table View for a tracker allows you to display selected upstream and downstream references for tracker items. For more information, see section Intelligent Table View.
Organize Public Views
Tracker Views (old)
Tracker Views define
In CB-9.0 and newer, the fields, format and sort order of tracker views is not longer used, only the Condition, that defines, which tracker items are visible via this view.
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.
will refer to the left/lower boundary of the period!
E.g. StartDate greater than "Today" means: StartDate >= Today, 00:00:00.
and StartDate equal "Today" means: StartDate == Today, 00:00:00.
and StartDate in "Today" means: Today, 00:00:00 <= StartDate < Tomorrow, 00:00:00.
So in most situations you should use IN instead of equal for Date comparisons!
codebeamer Knowledge Base
Services by Intland Software