Changes between Version 20 and Version 21 of SCS_ISSUE_TRACKER_SETUP_R1

Timestamp:

10/09/08 17:10:37 (17 years ago)

Author:

astea

Comment:

--

SCS_ISSUE_TRACKER_SETUP_R1

@@ -65 +65 @@
 The diagram below shows what our workflow will look like.
 The transitions available are:
- * 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.
+ * accept - this is when s.o. accepts to analyse, design, implement a task, with this transition the task's owner is automaticly changed to self. When accepting testing the owner will not changed.
  * done - finnished designing, implementing, etc. It is a must to write a comment including the time spended on working.
- * 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.
- * 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.
+ * review fail - the review has failed. Reasons and scores must be written as a comment.
+ * review ok - the review has passed. Scores and remarks must be written as a comment.
  * reassign - this transition is available at any state of the issue it does not change da current state, just the owner of the issue. 
  * 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.