| | 65 | This diagram shows what the workflow will look like. |
| | 66 | The transitions available are: |
| | 67 | * accept - this is when s.o. accepts to analyse, design, implement ot test a task, with this transition the task's owner is automaticly changed to self. |
| | 68 | * done - finnished designing, implementing, etc. It is a must to write a comment including the time spended on working. |
| | 69 | * review fail - the review has failed. Reasons and scores must be written as a comment. With this transition the task's owner is automaticly changed to self. |
| | 70 | * review ok - the review has passed. Scores and remarks must be written as a comment. With this transition the task's owner is automaticly changed to self. |
| | 71 | * reassign - this transition is available at any state of the issue it does not change da current state, just the owner of the issue. |
| | 72 | * resolve - this is a transition to finalise the issue, it leads to a closed state with a specific resolution ( fixed, invalid, wontfix, duplicate, worksforme, etc ). This is also availbla at any state of the issue. |
| | 73 | |
| | 74 | [[Image(source:/trunk/sophie2-platform/doc/uml-design-diagrams/workflow.png)]] |
| | 75 | |
| | 76 | Some issues like taskas may not need testing, we can resolve these issues after "implementation accepted" |
