- Reports and Dashboards
- Visual Reports
- Cumulative, Burn Up & Down Reports: Examples and Use Cases
Visual Reports in Targetprocess can process historical records. Two of the available reporting modes support past data records: Cumulative, Burn Up & Down Reports and History Changes & Transitions. Data sources for the reports are based from historical events and modification logs related to Targetprocess entities. Entities of multiple types such as User Stories, Tasks, Bugs, Features, Epics, Projects, Requests, Test Plan Runs are supported. In this article we'll describe how to filter the modification records used as data sources by date range.
Learn more about how to filter entities in the data source by other fields and properties in the other article: Filters by Entity Fields in Historical Visual Reports.
The Filters described below are applied on the Setup tab of the Visual Reports editor with History mode selected.
A historical report is built for a particular period of time. You can use one of the following fields to specify the date range:
- Release: the list of Releases
- Iteration: the list of Iterations
- Team Iteration: the list of Team Iterations
Date Range: Specifies a period of time not tied to a particular Release / Iteration / Team Iteration, for which the history report will be built.
Selected Date Range and Source Data
The filters in the Filter and Date Range / Releases / Iterations / Team Iterations areas are combined together with AND condition. Only the selected Entities that match all the applied filters are included to a historical report.
Scope of Work Selected
If you select a particular Release / Iteration / Team Iteration, then the system searches for all the Entitites that have ever been assigned to the selected scope of work. The entities may have been unassigned from the scope later - they are still present in the history report.
For each found entity, the system extracts a list of all past modifications that occurred during the times when an entity has been assigned to the selected work scope. Only modifications that occurred before the End Date of the work scope are included to the report.
An entity could be assigned to the selected work scope before its actual Start Date and these modifications are also included.
Date Range Selected
When you select a particular Date Range, the system searches for all the Entities that have been modified during this range. Then for each found entity, the system extracts list of all past modifications that happened before the End Date of the range. Some modifications may have happened before the selected Start Date and these modifications are also included.
Date Range Start and End Values
Use these system variables in the data source filters when you need to filter based on the selected Date Range.
'Date Range Start' 'Date Range End'
Hide Past Data
The following Advanced Filter excludes all the events that happened before the Start Date of the selected range:
?Date >= 'Date Range Start'
Exclude past events data from historical reports carefully. Improperly excluded data truncates details on lifecycles of entities that were processed exactly during Start Date or End Date days. Exclusions distort further calculations and aggregations such as totals and averages. As a result you get inaccurate perception of what's going on in your system.
There are two alternate practices we recommend to follow to increase the accuracy of your history reports:
- Do not apply any additional filters by Date of modification once Date Range is set.
- Filter only the entities that were fully processed (created and completed) during the selected Date Range. Exclude all the entities whose lifecycle is covered by the Date Range partially. Ensure that all data in your sample are homogeneous.
The following entity-specific filters can be used to narrow down your data source to the entities fully processed during the selected Date Range:
?CreateDate >= 'Date Range Start' and CurrentUserStory.EndDate <= 'Date Range End' ?CreateDate >= 'Date Range Start' and CurrentBug.EndDate <= 'Date Range End' ?CreateDate >= 'Date Range Start' and CurrentRequest.EndDate <= 'Date Range End' ?CreateDate >= 'Date Range Start' and CurrentProject.EndDate <= 'Date Range End'
This filter excludes the following entities from your data source:
- All entities created earlier than the Start Date of the selected range
- All entities that have not been completed by the End Date of the selected range
Hide Entities Completed Before the Selected Date Range
It may happen that small modifications are made to the done entities that were completed far in the past. When the dates of these modifications fit into the selected Date Range then these ancient entities appear in your history reports. Use the following filter in order to hide these entities:
?EndDate is None or EndDate >= 'Date Range Start'
All the Advanced Filters can be combined together within AND, OR logical conditions and brackets.
More information: Advanced Filters overview.
Filtering by Present Assignment to a Scope of Work
Use "Current" filters anytime when you need to refer to "present moment" assignments of the entities rather than to the "past" ones. Learn the difference:
|Feature||?Release is '2.0.4'||All past modifications that happened during the times when selected features were assigned to the release '2.0.4'|
|Feature||?CurrentFeature.Release is '2.0.4'||All past modifications that happened with the features assigned to the release '2.0.4' now|
a sales representative
Get a live
Let one of our product specialists create your account
and shape Targetprocess for your company needs.