v.2.2 - Subversion, Time Sheet
All the features described below appeared in TP 2.2 (Feb-5)
Subversion Integration
Subversion integration solves two problems:
- Reduce time developers spent on putting data into TargetProcess
- Bind bugs with code, so it is possible to review changes right from TargetProcess
How it works from developer side? For example, you've fixed the bug and spent four hours on it. Here is the list of usual actions you should perform after the bug fix:
- Commit change into source control system with comment that includes bug id
- Go to TargetProcess and find fixed bug
- Add the same comment to the bug
- Change bug state to Fixed
- Optional (add spent time on bug)
With subversion integration all you need is type short message when committing changes: "bug #745 state:fixed time:4 comments: there was a problem in controller logic". All the other things TargetProcess will do itself.
So you have all revisions related to bug as well as all files. You may view file content or differences between selected and previous revision:
Weekly Time Sheet
In general time tracking is "hard-to-setup" practice, since developers do not like add spent time. Most common arguments are "It is waste of time", "I am spending 15 minutes per day to add time! It is more than an hour per week and half a day per month!" So time addition should be as simple as possible. Time sheet in TargetProcess makes that really, really simple. It will take no more than 5 minutes to report spent time: one place, no reloads, no hassle.
Printable Reports
Easy printing is very important feature for agile project management system. TargetProcess provide flexible ways to print lists of entities. For example, it is possible to print user stories with all associated bugs, test cases, tasks, time records and other details. Printable view is highly customizable.
Test Cases Library
Often you test cases that can be reused in different projects. For example, login functionality is almost the same in all projects as well as login testing. So you may create several test cases for "login user" feature and save them in test case library. Then you may select test cases and copy them into another project. Also the library supports tags categorization and filtering.
Report: Bugs Progress (active/closed)
Bugs progress chart shows open/closed bugs dynamic. It answers the following questions:
- Is bug fixing dynamic positive or negative?
- How many bugs have been added each day?
Report: Iteration Burn Down Chart
Burn Down chart shows implementation progress during iteration. It tracks when user stories and bugs have been closed and shows remaining effort.
Release Notes
Release Notes contains all changes for release (completed user stories and fixed bugs).
Simple Active Directory Integration
Remember fewer passwords is always a good thing. TargetProcess supports windows authentication starting from v2.2