Changes between Version 163 and Version 164 of ProjectInformation


Ignore:
Timestamp:
12/09/10 19:11:47 (11 years ago)
Author:
Pat Tressel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectInformation

    v163 v164  
    105105 * Try to reproduce the problem reported in the ticket:
    106106  * If the bug is still there, and the description of how to make it happen is clear, just add a comment saying you verified that it's still there.
    107   * If the description of how to make the bug happen is clear, and the bug is gone, add a reply to the ticket with what you did to test it, and "resolve" the ticket as "invalid". (The person who reported the bug can still reply and reopen the bug if they want.)
     107  * If the description of how to make the bug happen is clear, and the bug is gone...
     108   * If there are also suggestions for improvements, and those haven't been done, add a reply that you've verified the bug is gone, and change the type to "enhancement".
     109   * Otherwise, add a reply to the ticket with what you did to test it, and "resolve" the ticket as "invalid". (The person who reported the bug can still reply and reopen the bug if they want.)
    108110  * If the instructions to cause the bug to happen aren't clear, try to figure out what the reporter meant -- try to find the bug yourself. If you can reproduce the bug, add better "how to reproduce" instructions.  See the [wiki:BugReportingGuidelines Bug Reporting Guidelines] for what makes a good bug report.
    109111  * If you can't figure out what the ticket means, add a reply that tells the ticket reporter what info would be helpful.