You are not logged in. Click here to log in.

codeBeamer ALM
Last Modified

Search In Project

Search inClear

Trackers

Since codeBeamer 8.2.0 Test Run and Test Case tracker configuration is more restrictive - it is not possible to define Guards or modify necessary fields anymore for Test Runner but this is configurable in general.xml. To enable the configuration of these properties add/edit this option in general.xml: <testManagement disableEditingBuiltInFieldsName="false"/>

Trackers in CodeBeamer are used for

  • Managing IT processes,
  • Managing Requirements,
  • Managing Changes,
  • Managing People, relationships,
  • Managing Innovation,
  • Escalations, SLA
  • Agile (Software) Development,
  • Bug tracking

and for other purposes.

Trackers are the equivalent of Tables in a Relational Database or Classes in object oriented programming.

Tracker items are the equivalent of Rows in a Relational Database or Objects in object oriented programming.

Trackers define the

  • Structure (fields),
  • Relations to other items (in other trackers) (via reference fields, similar to Foreign Keys),
  • Behavior (permissions, aggregation/distribution rules, state transitions, events, actions, escalations, notifications, etc.),

Tracker items represent the State (field/attribute values, including history) of a specific bug, task, requirement, etc.

In addition to the configured Relations, you can also create ad-hoc Associations between tracker items and other CodeBeamer entities like other items or documents, even with external URLs.


Each Tracker has a Stereotype, which defines:

  • The basic classification for trackers and items of this type
    • Work item
      all things, that represent work, that needs to be planned, accomplished and monitored, e.g. a task to execute, a risk to track, a bug to fix
    • Configuration item
      all things needed to do the work, e.g. tools, software, models, and plans, etc., and that need to be managed (CMDB or ITIL).
    • Source code
      the result/output of accomplished work (Software Development only), that needs to be managed by SCM
  • The basic/core Structure and Behavior (only relevant for top-level/base Trackers, derived Trackers inherit that from their template Tracker)
  • The icon/symbol for trackers and items of this type
  • The available Views for trackers of this type


See here for an overview of defined tracker stereotypes.

Trackers (similar to Classes in object oriented programming) can be derived from/extend base/template Trackers:

  • Structure and Behavior of the base/template Tracker are inherited by derived Trackers.
  • Inherited settings can be overloaded/overridden in derived Trackers.
  • Derived Trackers can add own/additional Structure and Behavior.
  • The depth of the inheritance tree is unrestricted.


Trackers are type definitions and item containers at the same time (similar to database tables).

  • Therefore Trackers are a special type of Folder/Directory.
  • By default, all Trackers reside at the top-level of their Project's Documents hierarchy.
  • But you can also create Trackers in any sub-directory/folder of the document hierarchy (currently disabled via GUI).
  • Trackers provide fine-grained access control for items, item fields and state transitions, based on user roles and item state.
  • Work and Configuration Item trackers only hold work/configuration items, no files or folders.
  • Source Code Repositories (which are an extended type of Tracker) are both:
    • they are Folder/Directory for the source code files
    • they are Tracker for source code changes (commits and pushs)
  • Tracker items (in the same tracker) can build a parent-/child-hierarchy of unlimited depth.
  • Tracker items can hold any number of files (in form of attachments)
  • Trackers (including items) can be copied/moved as any other regular document (currently disabled via GUI).

Please note:

  • Work and Configuration Item Trackers at the top-level of the document tree, are only shown on the Trackers page of the project.
  • Source Code Trackers (Repositories) at the top-level of the document tree, are only shown on the SCM Repository page of the project.
  • Trackers (of any type) in sub-directories/folders are only accessible via their directory/folder under Documents, not via the Trackers or SCM Repository page.

Work and Configuration Items can be copied/moved from one tracker to another (compatible) tracker, but because structure and behavior are bound to the tracker and not the item, this always implies a type conversion (attribute mapping), and can therefore inflict data/information loss.

Tracker Summary

On the Tracker Summarypage, a summary of the number and status of all issues is displayed. When you click on a Tracker Name a list of tracker issues will be shown. This list gives a detailed overview of all issues in the tracker.

Different users can see different statistics depending on their roles.

Figure: Project Tracker Summary List

Tracker Tree

From codeBeamer 8.1.0 you are able to make Tracker structure using drag&drop functionality within the left side tree on Tracke Homepage.

By default you can see the Work items / Config items folders with the containing trackers. With Project Admin permission you are able to change this structure: creating/removing/renaming folder, drag&drop trackers/folders, make tracker hierarchy. Once you make some changes, the structure will be saved.

The trackers within the tree contains some additional information:

  • Number of tracker items (Open items / All items)
  • Last modified date
  • Tracker key

You can open the trackers from the tree the following ways:

  • If you double click on a tracker, the tracker page opens in the same tab.
  • If you use the middle button of the mouse, the tracker page opens in a new tab.
  • Right click context menu Open option: click opens tracker in the same tab, middle button click opens tracker in a new tab.

The right click context menu of the tracker tree nodes gives you some useful functionality: Customize, New Item, Rename, Workflow Diagram, Configuration Diagram etc.

Please note, that the tracker tree structure/hierarchy does not define any tracker inheritance!

Tracker Tree configuration

Clicking on the gear icon on the top of the tree opens the tree configuration overlay. Currently there is one setting option: Show Hidden Trackers. If set, the tree will contain a Hidden Trackers folder.

Permissions and license types

See license information in:

Issue List

The tracker issues list provides detailed information about a tracker.

The heading P refers to Priority. The meaning of the color-coded dots is not editable. The Legend: red is for highest priority issues; orange for high; yellow for normal; green for low; and blue for lowest priority issues.

Figure: Tracker Issue List

Filter Widget

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

  • Filter button: click the Filter button to add filters. You can select from the Default fields (Status, Priority, Start Date, etc.), from the Common Reference Fields (e.g. Release, Subject, etc.), from custom fields of the tracker if present, and from the other filtering option. Filters types described here: Reports
  • Group by button: click on the Group by button to group the issues. You can display groups up to 3 levels the same way just like on the Reports page.
  • Order by button: click on the Order by button to define sorting. You can select up to 3 levels of ordering options.
  • Search input: type any text for filtering issues using a full-text search. This will find the typed pattern in any text fields of the issues.
  • GO button: click on GO button to display the result of the selected filters.
  • View Menu button: click on View button to manage filters (views).

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).

View 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.

View types:

  • Public Views: pre-defined views of the tracker (Open, All Items, All Unresolved, etc.) and custom public views. User can save public views only with Views - Admin permission. Public views are displaying for all of the members of the project.
  • Private Views: only displaying for the user who saved the private view.

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.

Save new View
  • Select the desired filters, optionally add Group by / Order by options
  • Click on the View Menu
  • Click on Save as...
  • Type the name of the view (if you have permission to admin views, Public View checkbox appears in the overlay, check it if you would like to create a public view)
  • Optionally add a description of the view

  • Click on Save button
  • The saved view will immediately appear within the View Menu

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.

Manage fields

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 field 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.

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.

Searching for Working Items

Use full text search in the Search field to find tracker issues. Enter the search text pattern and click on GO. From codeBeamer 9.0.0 you can combine full text search with the selected filters, group by/order by options.

Submitting a New Work item

To submit a new issue:

  1. Click on New,
  2. Provide a one line summary for the Issue in the mandatory Summary field
  3. Enter a more detailed explanation in the mandatory Description field,
  4. Set the values of the other non-mandatory fields, as required,
  5. Click on Save.

The required fields are marked by red color, fields with view-only permissions are grayed (marked by gray color). After submitting the new issue, you can follow up using attachments, associations or in other ways using the options described below.


Figure: Submit a New Issue.

Adding Details, such as Comments, Attachments, Associations and Reminders

For each Issue you can assign attachments, comments and associations, and more, using the tabs under Details, near the bottom of the Issue display.

Figure: Issue Details: such as Comments, Attachments, History

Breadcrumb navigation

From 8.0.1. there is a new functionality on Tracker Item details page. Below the header where the Summary is displaying, there is a breadcrumb navigation stripe. You can see here the upstream references of the current isseu in 3 levels. You see 3 items per level, if there are more reference items, the other items are visible under the context menu.

Adding Comments

You can add comments to an issue by clicking on the Add Comment link under the Comments tab, under Details. From 8.0.1 the comment edtor will be visible on page inline, otherwise this results in a normal wiki edit pop-up window. Click Save when finished entering the comment.

Adding Private Comments

You can add comments to an issue by clicking on the Add Comment/Attachment link. You can select a specific role from the Visible for pop-up so that your comment is visible only for the members in the selected role. This feature allows you to designate information as suitable for external or internal users. For example, when a customer submits an issue, developers can discuss an issue internally with private comments and reply to the customer when they come to a common understanding.

Figure: Private Comments

Delete or Edit Comments

Delete or Edit comments by selecting Delete or Edit from the tool-tip menu at the far right of the comment's line. You will be asked to confirm a delete.

Figure: Delete and Edit in Issue Details Comment-Tab Tool-tip

Adding Attachments

Attach screenshots, images and binary documents to an issue using the Attachments tab. Attach up to three documents at one time.

Adding Associations and Dependencies

You can associate tracker issues with other tracker issues, forum topics, documents, source files, commits or external URLs. For example, an association enables you to define relationships between project plan documents and requirements, tasks or bugs.

Figure: Associate Tracker Issues with Other Artifacts

If an association is made, a comment can be added for the association in the comment field below the association definition, and above the attachment selection. Note that this is a comment for the association, not the whole issue, and the text is only stored and redisplayed if an association is made.

Find artifacts to associate using the tabs:

  • history artifacts from your recent activities,
  • search results from the search tab or
  • URLs.

The following artifact types can be associated:

  • Tracker Issues,
  • Source Files,
  • Documents,
  • Dashboard / Wiki pages
  • URLs (CodeBeamer internal or external).

The association type can be:

  • depends on
  • superordinate to
  • subordinate to
  • related to
  • derived from
  • violates
  • excludes
  • invalidates
  • copied from

You can select Current HEAD from Baseline selector, if you want that the association should belongs to the last version of the item. You can use also Propagate suspects with normal or reverse direction.

Using configuration files new association types can be added.

Select the check box of a document, Tracker Issue, URL, Forum topic or Source File to be associated. Add a comment. Then click the blue Add button to add the new association. If a related-type issue association has been made, it will appear under the Related Issues tab in the details of the issue.

However, selecting a association-type of parent, child or depends will not change any of the Children tab contents in any of the associated issues. Instead, please use the Children tab to define dependencies.

History

Since release 6.0, codeBeamer issues are versioned. Every change (editing, commenting, workflow transition) results in a new issue version, identified by a unique version number.

The History tab now does not longer show the change history, but the version history of the issue.
By clicking on a version number, you can display this historic version.




Only the current version (head revision) of an issue is editable (depending on issue status and user permissions).
Concurrent editing operations are now detected, only the first user to commit his changes will succeed, all other users editing the same revision will be rejected ("Attempt to update non-head revision").

Reminders

When viewing an issue, the more menu tooltip makes it easier to add comments, attachments, associations, tags and children, but you can also create a 'Reminder' of the issue, using the tooltip's link.

Figure: more Tooltip Menu with Reminder Selection

When Reminder is selected, the following pop-up window appears:

Figure: Reminder Window

In the pop-up, you select the amount of delay before you receive an email reminder of the issue. The Reminder function is dependent on having the Escalation Module. Other types of notifications can be sent based on complex conditions of the issue: see Escalation Management: Service Level Agreements (SLA) for more details. A Reminder is also dependent on how your project calendar is defined in the project's Admin area. For example, if your Project Calendar's Default Business hours end on Friday at 17:00, and you make a Reminder with a delay of 1 hour, you won't see the reminder until the Default Business Hours start again, typically on Monday morning. See Administering Projects for more information.

Editing Issues

Issues are typically updated during the project's lifetime. Users with different roles like project manager, architect, developer or contractor can change the status, priority and severity of issues based on their roles and permissions. For example a customer can submit a bug, but he or she can view only the bugs that were submitted by him or her. A support engineer can view and edit all bug submissions, then assign them to one or more developers, and later a test engineer can close the Issue.

Figure: Edit an Issue.

If you assign an issue to members, they will be notified about the assignment action as well as about all the changes that will be made to the issue in the future by other users.

You are not notified about your own changes.

When a user starts editing an issue it automatically gets locked so the other users cannot edit it. The other users will see a notification in the issue breadcrumb.

The item is automatically unlocked when the locking user stops the editing.

Using Cut, Copy, and Paste (Move and Duplicate)

With cut, copy and paste you can easily duplicate and move issues across trackers and projects.

Copying Issues With Copy/Paste

Copy existing issues into a different tracker in either the same project or in a different project. When the source and the destination tracker have different fields, a field mapping wizard helps associate the different fields. When the copy or paste commands are used, the duplicate issues are dependent upon the source issue. The Mass Edit feature enables deleting this dependency.

Copy and Move Issues Between Trackers

Reorganizing projects may require moving issues into different trackers. For example, move a change request entry into a task tracker. When the source and the destination trackers are different, the field-mapping wizard allows easy mapping of the source and destination fields.

The actions Copy to and Move to allow the selected issues to be copied or moved from one tracker to another tracker. Under the Children tab of an issue, children of an issue can be selected and similarly copied or moved, using the more pull down menu.

Figure: Tracker Actions Copy, Paste and Move

The destination chooser dialog only shows those trackers into which the user is permitted to add issues.

The possible target trackers are grouped by project and can be optionally filtered by type.

In a Move to operation only a single destination can be selected. Multiple destinations can be selected with Copy to . Each target tracker will receive its own copy of the selected issues.

Copy or Move Issue Children

By default, in status Closed an issue's children and associations cannot be changed.

Parent permission and status are both used to decide whether a descendant (child) issue can be moved.

The actions Cut and Move to ... for issues are only enabled if the user has Edit permission for the issue's Parent in the current issue status. If the issue is the child of a parent issue, then "Edit" permission for the parent's Children (according to the parent's status) is also required.

Issues can be copied and moved using Cut, Copy and Paste and Copy to... or Move to ... functions.

This will also copy/move the descendants of the issues recursively.

Issues can not only be moved between trackers but can also be copied or moved within the issue's hierarchy. Descendants of an issue can be copied or moved to a tracker or to another issue.

In issue lists you can see the children of an issue in the Summary column. The child is shown as a folder, with another child-issue number and summary shown beside the folder, in the parent issue's Summary column. Navigate directly to the "Children" tab of the current (parent) issue by clicking on the directory icon, or navigate to the child issue, by clicking on its link.

Creating issues from templates (only requirements)

You can easily create new requirement based on an other one. Just click on Use as template under the more menu you'd like to use as a template. This will bring up the create issue page where all the fields are copied from the selected template (including the summary and the description).

Mass Editing

Mass editing can change multiple issues in a tracker, e.g. close all selected issues or change the value of the Target Release field from V1 to V2.

Deleting Issues

You can select one or more issues and then delete them all at once.

Workflows

Workflows provide better control for critical tasks or requirements where the change has strong impact on resources or deliverables. CodeBeamer trackers integrate a simple and flexible process engine to model business process workflows.

Trackers can be used with or without workflows. Trackers can "inherit" a workflow from other trackers or use their own workflows. Workflows can be customized. See State Transitions.

Hierarchical Issues' Field Value Dependencies

If you have parent/child hierarchies of configuration items or issues, you can now define dependencies between parent field values and the appropriate child field values recursively. If, for example, you wish to ensure that a parent issue is not closed until all the child-issues (children) are closed, then this dependency can be managed using one of the distribution rules defined in the following linked document. Similarly if you wish to define the parent issue's "Spent Hours" as the sum of the children's "Spent Hours" you can define this aggregation rule, too. For more information, please see Dynamic pick-list fields .

Tagging Issues

Issues can be categorized using tags, see Taxonomy: Categorizing Content with Tags.

Tracker Dashboards

CodeBeamer provides visibility and control on project status and progress. Since actions such as task completions, bug submissions, program downloads and SCM check-in actions are all captured in the CodeBeamer repository, accurate and real-time project status reports are provided at any time and from anywhere. Reports are provided on a single-project or on a multi-project level for project managers, developers and stakeholders.

The dashboard is visible only to users that have the Tracker - Report permission activated. Use the Members Tab, Roles, tool tip edit to change Tracker Report permissions for a member.

Visualization Trends and Statistics

For visualization purposes different customizable Wiki plugins are provided. You can use combinations of these plugins in different Wiki pages to build project specific or user specific dashboards. The following Wiki plugin

[{PieChart title='Open Tracker Issues by Severity' legend='false'

[{DataSet data='trackerItemsByLabel' label='severities' projectId='37' format='pieChart'}]
}]

will result in the chart:

See Data Set Plugin in Wiki Markup and Plugins There must be a blank line between the chart definition and the dataset definition, otherwise a JSPWiki 'no body text' error will result

Create or Customize Trackers

The project administrator or a user with sufficient permissions can create, delete and customize trackers. To give the entire set of users in the Project Admin role the permission required to customize a tracker, the Project Administrator can select the Member tab, then the Accounts and Roles Tab, then under the Project Admin role, select the tool-tip edit function. In the resulting chart, click the check-box for the Tracker-Admin function. This enables all users in the Project Admin role to customize the tracker. See Creating and Customizing Trackersfor information on tracker administration and customization.

Subscribe Notifications

Tracker Subscriptions

Email notification subscriptions to the whole tracker result in e-mail notification when any issue is submitted to or modified in the tracker. Select email notifications for the whole tracker by clicking on the Follow in the more context menu.

If this doesn't work, it is because the appropriate permissions are not set up. Contact your Project Administrator for help, or if you are the Project Administrator, see Creating and Customizing Trackers

Issue Subscriptions

Go to the Issue details page and click on Follow option of the more menu.

Unsubscribe Notifications

Click on the Unfollow option of the more menu. If you cannot unsubscribe, it is because your role in the project is set as subscribed. Several people may be in the same role as you, and unsubscribing all of the members in the role may not be desireable. Contact your Project Administrator for more help.

Import Data into a Tracker

See different import options in:

Customize Tracker

See customization on Creating and Customizing TrackersWatch a video on the tracker customization here.

related information Reports (Vintage),
State Transitions,
Creating and Customizing Trackers,
Escalation Management: Service Level Agreements (SLA)