...
- if developer is finished with development, (s)he puts the issue up for review. Field 'code reviewerCode Reviewer' must be left empty. Field 'Fixed in Version(s)' must be set. The developer also must check if all subversion commits are reflected properly in the issue.
- reviewer picks up issue and assigns herself/himself as reviewer.
- start progress:
- reviewer indicates when (s)he starts working on reviewing the issue.
- stop progress:
- reviewer indicates when (s)he stops working on reviewing the issue. This step is optional is (s)he decides immediately on the next state for the issue, see below.
...
- this state can be reached in 4 situations:
- review was okay.
- issue was resolved after as a result of a pair programming effort.
- issue is not reproducable.
- developer is waiting for client (with reason as described in the comments of the issue).
- an e-mail will be sent sent to the reporter of the issue
closed:
- this state can be reached in 2 situations:
- testing was successful.
- issue is a duplicate.
- tester must not reassign the issue.
- an e-mail will be sent to the reporter of the issue and to the product owner(s).