This article describes how to build a single Targetprocess view that would display features with all nested bugs.
A Feature in Targetprocess 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.
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. It may be a problem as there is no transparency when you review the backlog and some Bugs may miss your attention.
The guide below describes how to build a hierarchical list view showing both kind of Bugs distributed per Feature.
Typical setup of the list view is the following:
- 1st hierarchy level: Feature
- 2nd hierarchy level: User Story
- cards: Bug
Here is how the view looks like in expanded state:
Using Customize Cards you can bring counters of Bugs to User Story and Feature levels. As a result you can quickly see which Feature has bugs inside and which one hasn't them.
The hierarchical Feature > User Story > Bug list shows bugs under user stories only when a bug has relation to the parent story's feature as well. Bugs with blank 'Feature' field are always hidden.
In general empty hierarchy lanes in the list view cannot be hidden. This capability has not been implemented in Targetprocess yet. However advanced filters can hide user stories and features with no bugs from this list view. As a result you focus only on work items that worth to attract your attention.
How to set it up
- 1st hierarchy level: Feature
- Filter: ?Bugs.Count > 0
- 2nd hierarchy level: User Story
- Filter: ?Bugs.Count > 0
- cards: Bug
We are done. Here is how the view looks like now:
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.