Changes between Version 1 and Version 2 of BoostCon2008BugReporting


Ignore:
Timestamp:
May 20, 2008, 10:35:39 PM (14 years ago)
Author:
Marshall Clow
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BoostCon2008BugReporting

    v1 v2  
    1414By Accepting the ticket, he agrees that it is really a bug, and it is correctly assigned. Once that happens, the ticket moves to ....
    1515
    16 State "Accepted": Here, the ticket has an owner, and the Triage team and the owner have agreed who that is. When aticketbug reaches "Acceptance", it needs to have an assignee, a milestone, a priority, and a classification (Bug/Support Request/Feature Request). From here, ticket may be closed in all different manners (Fixed/Invalid/WontFix/etc), or they can be assigned to someone else, in which case they go back to "Assigned", until the new "owner" accepts it.
     16State "Accepted": Here, the ticket has an owner, and the Triage team and the owner have agreed who that is. When ticket reaches "Acceptance", it needs to have an assignee, a milestone, a priority, and a classification (Bug/Support Request/Feature Request). From here, ticket may be closed in all different manners (Fixed/Invalid/WontFix/etc), or they can be assigned to someone else, in which case they go back to "Assigned", until the new "owner" accepts it.
    1717
    1818The idea here is that no one will get ticket w/o their consent (acceptance). However, the other side is that ticket should not spend a lot of time in the "Assigned" state - they should be accepted on a timely basis.