Setting Tracking Levels
This article explains how to set tracking levels in Agility.
Overview
After Effort Tracking is enabled, you can then define the levels of story and defect details you want to track. By default, stories are tracked at the task or test level only and defects are tracked at the defect level only. If you want to change these levels, follow these steps:
-
Click the hamburger menu
> Admin > Configuration > System. -
Make sure that Effort Tracking is enabled and select a tracking level for Backlog Item or Defect in the Tracking Level section.
-
- backlog items at the backlog item level only, task or test level only, or both
- defects at the defect level only, at the task or test level only, or both.
-
Click Save.
Note that TestSets can only be tracked at the work item level and cannot be configured.
Important Notes about Tracking Levels
Tracking level settings affects the ability to edit Detail Estimate, Effort (Done), and ToDo, as shown below.
| Workitem Tracking Level | Task/Test Tracking Level | Workitem AND Task/Test Tracking Level(Note Recommended. See Warning Below) | |
|---|---|---|---|
| Backlog Item or Defect | Editable | Not editable | Editable |
| Task or Test | Not editable | Editable | Editable |
Implications of Tracking at Both the Workitem AND Task or Test Tracking Levels
Tracking at both the Workitem and Task or Test level is not a recommended setting for most organizations. While potentially helpful in some very specific environments, it does require that *all* users understand the following:
- tracking is not uniform across the organization
- the level at which their specific group should be tracking
- the customization of tracking grid views required to support their group's process
For example: Users will need to show both entry field columns and total columns to get a proper rollup at the workitem level (e.g. show both To Do and Total To Do, Detail Estimate and Total Detail Estimate) for a clear picture of where the numbers exist and should be entered.
Systems with a concentrated number of heavy users with very distinct tracking needs may have success with this setting. However, in larger organizations with many casual users, the potential confusion that comes along with this setting often outweighs any benefits.