v.2.12 - Burn Down Charts, Custom Reports
All the features described below appeared in TargetProcess v.2.12 (January-14)
New Release Burn Down Chart
Problems: "I want to see scope creep during release. It will help to identify whether we have problems with team productivity or is it just new features constantly added to the release".
Solution: New burn down chart shows added/removed work in iterations.
New Iteration Burn Down Chart
Problem: "Iteration burn down chart should show us forecasted iteration date based on our progress. Also it should show scope creep."
Solution: New iteration burn down chart that shows both added/removed and forecast work. Bugs are included to the report as well.
Custom Reports: Inner Lists
Problem: "We want to create complex reports with more details. For example, I want to create a report that shows user stories from current iteration and I want to see all open bugs, open tasks and failed test cases for each user story".
Solution: Implement inner reports. Now you can create inner reports efficiently and see all the related information on one page.
Custom Reports: Inline Edit
Problem: "If I want to change something in a report I should navigate to view, then click edit and change something. It takes too much time".
Solution: Enable inline editing in custom reports (Excel-style).
New Audit History (that tracks everything)
Problem: Burn down charts require better history data.
Solution: Implement new audit history mechanism that tracks all changes.
Search in Help Desk Portal
Problem: "I want to post a request, but maybe a similar request already exists. There should be a way to find it."
Solution: Add search functionality into Help Desk Portal and allow people to search for requests based on keywords.
Other Improvements
- Installer improvements (Check database conection button, Database backup confirmation step).
- FCKeditor integrated as a rich edit control.
Known Issues
- TargetProcess does not work on VMWare on 64-bit Windows platform.
- Upgrade to v.2.12 will fail in the following case: suppose, you have installed TargetProcess with Russian culture. You add entities and start using the product. Then you decide to change culture to English. In this case audit history conversion will fail (it will skip entities with incorrect date format). As a result, some audit history information will be lost.