JIRA has three main states for classifying its issues: open, resolved, and closed. Open is for issues that haven't been looked at or fixed. Resolved is for issues that have been fixed but haven't been tested, and closed is for what was an issue before but is now not, and doesn't need to be looked at anymore.
With the current system, once a patch is tied into the main code, its corresponding issue is changed from 'open' to 'closed', eliminating any record of testing from the process. Patches, of course, need testing too, so why not take advantage of the 'resolved' state that JIRA gives us? Could me make a combined effort to mark patches as 'resolved' instead of 'closed' when we implement them into the code, to keep our testers aware of what still needs testing? Thanks -Trevor Trevor Oldak Quality Assurance Nexaweb Technologies 1 Van de Graaff, Burlington MA, 01083 o 781.345.5438, f 781.354.5501, c 978.790.1313 Email: [EMAIL PROTECTED] Web: www.nexaweb.com "Enterprise Web 2.0 Solutions - Thinner, Richer, Faster"
