Brief summary of this article:
Feature in Targetprocess is one of the key entity types in the data model.
A Feature is a high-level requirement. In most cases, Features are required for large and medium Projects; in small projects, features are optional. A Feature is larger than a User Story, and one Feature may contain several User Stories. Features can be assigned to a Release and Team Iteration.
Features are denoted by green color.
Terms
The following custom terms and aliases are frequently used for Feature entity:
- Strategic Theme
- Activity
- Post
- Portfolio Epic
- Initiative
- Program Feature
- Goal
- Campaign
- Deliverable
More on custom process terms: Rename Terms (Entity Types).
Parent Entities
Feature always belongs to a single Project. It is listed in Project field in Info panel. Parent Program of the Project is automatically inherited by a Feature.
Feature may belong to single Release. It is listed in Release field in Info panel.
Feature may belong to single Epic. It is listed in Epic field in Info panel. Project and Release of the parent Epic may differ from ones of its Feature.
From 3.13.0, a Feature can be linked to a Team Iteration in the same way a User Story, Bug, or Test Plan Run can. It’s possible to set Team Iteration for Features either manually or to calculate as the Team Iteration of the latest User Story in the Feature. So you can plan Features by Team Iteration then build views with Features cards and Team Iterations as an axis, etc.
Nested Entities
Feature may have multiple nested User Stories. They are listed on User Stories tab. A User Story may be related only to a single Feature.
Feature may have multiple related Bugs. They are listed on Bugs tab. A Bug may be related only to a single Feature.
Bugs in Targetprocess can be related to Features directly, or within intermediate User Stories, or both ways.
Direct parent Feature of a Bug and parent User Story's parent Feature may be two different Features.
Bugs that have no direct relation to a Feature and are related to it within intermediate User Stories only, are not displayed on Bugs tab of the Feature detailed view. Set up dedicated hierarchical list view to track bugs of this kind: List view for Bugs per Feature.
Effort and Progress Calculation
Total Effort of a Feature having at least one User Story is always equal to total Effort of its User Stories. Effort of nested Bugs is not included.
Total time spent of a Feature is always equal to the total time spent on its User Stories. Time spent on nested Bugs is not included. It is not possible to submit Time record to a Feature directly.
It is possible to set up custom calculations and get total Bugs count, effort, time spent, cost displayed per Feature. Learn how: Metrics for Bugs in User Stories and Features.
Reports
See also:
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.