v.2.7 - Custom Reports, Release Planning

All the features described below appeared in TargetProcess v.2.7 (27 Dec 2007)

• Custom Reports / Report Engine
• Program Level Release Planning
• Workflow per Process
• Tasks Prioritization
• Default Priority
• Perforce Integration
• Other Improvements

Custom Reports / Report Engine

Problem: Predefined reports did not cover the range of reports that users might need.

Solution: Implement Report Engine that allows building your own reports.

Report Engine is a powerful tool that help you to extract data and present it in the most appropriate way. With Report Engine you may select columns, specify filtering conditions, set sorting and grouping of results, add summary columns and build charts.

As a result, you may create such reports like "Open user stories from current release with Passed/Failed/Not Run test cases counts" or "All user stories from current iteration grouped by state".

Program Level Release Planning

Problem: We have large product and several teams working on this product. How can we plan product release? We need a way to assign user stories and feature from product backlog to releases for each team.

Solution: Implement Program Level Release Planning area. In this are you may create releases for all projects inside program, assign user stories and feature to individual project releases, see forecasts and progress information for current releases and re-plan releases.

If you have large product and several teams it is recommend to create a single program and separate projects for each team. With Program Level Release Planning you may plan and track all project releases on a single screen, aligning all releases to meet product release.

Easy drag and drop interface, very fast AJAX-based actions, constant feedback, filters and sorting - all these features make planning very comfortable and fast.

Workflow per Process

Problem: We have different departments in our company that follow different processes. They have different workflows for user stories, for example. We want to use TargetProcess for all departments, but it is not flexible enough to make this possible.

Solution: Replace global workflow with process-based workflow to eliminate such obstacle and make TargetProcess more flexible.

In v.2.7 you may define as many workflows as required. Create new process, configure workflow and bind this process to a project. Works like a charm!

Tasks Prioritization

Problems: We want to set execution order for tasks in user story. We want to give some tasks higher priority inside user story.

Solutions: Allow people to prioritize tasks inside user story.

Prioritize tasks inside user story view or right in user stories list using drag and drop.

Default Priority

Problem: We want to have default priority for user story that differs from the one in the system.

Solution: Provide an option to configure default priority.

Perforce Integration

Problem: Perforce users can't benefit from source control integration..

Solution: Implement Perforce integration with the same functionality..

Now Perforce users can benefit from TargetProcess as well. You may change bugs state automatically; bind source code to user stories, bugs and tasks; add time records right from commits messages; view source code in TargetProcess; diff files.

Other Improvements