As a consultant, I have been exposed to many different development methodologies and processes. In most cases, assignments are performed by a person that is aware of staff resources and distributes tasks according to the availability of these resources.
Continue reading…
how to
Being able to easily and quickly segregate data by various criteria is a requirement of any product that claims to be “easy to use.” For example, product management is interested in commonly reported issues and feature requests during product planning, but nearing the end of a release cycle they’re focused on critical issues that could delay the release. QA wants to see test runs yet to be executed or those that need to be re-run and development wants to see approved requirements that are ready for implementation. All of these scenarios create the need for distinct and re-usable “views” of the artifacts in TestTrack. This is where TestTrack’s tabbed views can make life much simpler for you as a user.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponThe list report grouping stylesheets, introduced in TestTrack 2009, have been tremendously helpful to customers looking to slice data by various attributes, such as hours worked by product/component.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Did you know that you can hide the Workaround tab on the Edit Defect window in TestTrack Pro if it’s not part of your issue tracking process?
The Workaround tab hides itself if the only field on the tab, the Workaround field, is hidden.
All you have to do is set the field security privileges for the Workaround field to Hidden for each security group that doesn’t need to see the Workaround tab.
Steps
1. Select View > Security Groups… .
2. Edit… a security group to hide the Workaround field.
3. Don’t forget to reload the project by selecting File > Switch Project… to see the results!
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
