7.5.5. Frequency
While defects may be very severe, they may not happen frequently, while bugs as insignificant as spelling errors may be seen constantly. The frequency at which an error occurs may play a big part in determining when it needs to be fixed. For that reason, AgileTrack allows defects to be classified by frequency and for that to be taken into account when planning iterations.
It sometimes takes a while to get a feel for the frequency of a defect, but it is often useful in classifying the issue and making good decisions about what is important.
![]() |
1. AgileTrack Overview
2. Installation 3. Server 4. User Interface 5. System Configuration 6. User Management 7. Issues
7.1. Types
8. Projects7.2. Issue List View 7.3. Creating Issues 7.4. Templates 7.5. Classification 7.6. Assignment 7.7. Status/Completion 7.8. Time Tracking 7.9. Comments 7.10. Attachments 7.11. History 9. Iterations 10. Releases 11. Queries 12. Reports 13. Integration APIs 14. Troubleshooting |
AgileTrack
Put your development on the AgileTrack
Put your development on the AgileTrack
In addition to Importance and Urgency, defects can be classified using the fields Severity and Frequency. The classification fields are imprecise, but allow general ranking and classification of issues. Iterations should be used for fine tuned planning. It is up to your team to decide how valuable are such fields, and how to best classify issues in AgileTrack.