new issue:
- set components to indicate the kind of issue, for example 'D-RainfallRunoff' and 'UndoRedo'.
- mandatory settings: 'Affects version(s)', 'Priority', 'Build Number'
- optional settings: 'Fix version(s)', 'Customer'
assign issue:
- this state can be reached in 4 situations:
- developer assigns issues to her/himself
- someone assigns issue to other person. That person will be notified by e-mail.
- issue is reopened after review. The developer will be notified by e-mail.
- issue is reopened after testing. The developer will be notified by e-mail.
- start progress:
- developer indicates when (s)he starts working on the issue.
- stop progress:
- developers indicates when (s)he stops working on the issue. This step is optional if development is done and the issue is put up for review immediately by the developer.
review:
- if developer is finished with development, (s)he puts the issue up for review. Field 'code reviewer' must be left empty. Field '
- 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.
resolve:
- this state can be reached in 4 situations:
- review was okay
- issue was resolved after pair programming
- 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
