Changes between Version 1 and Version 2 of SCS_ISSUE_TRACKER_SETUP_R1

Timestamp:

10/03/08 11:02:53 (17 years ago)

Author:

deyan

Comment:

--

SCS_ISSUE_TRACKER_SETUP_R1

@@ -2 +2 @@
 
 = Analysis =
-^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^
-
 == Overview ==
-^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^
+Decided to try to use Ticket system more efficiently. This includes using ticket systems for every task's change to see what is the status of each task, use assign to, etc.
 
 == Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
+Create new ticket resolutions:
+ * Analysis
+ * Analysis review pending
+ * Design
+ * Design review pending
+ * Implementation
+ * Implementation (task) review pending
+ * Testing pending
 
 == Task result ==
-^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^
+Issue tracker capable of handling tasks' whole process.
 
 == Implementation idea ==
-^(It is advisable to include some rough implementations ideas.)^
+Create the resolutions listed in Task Requirements section. Design a workflow. Try to separate PLANNED_TASKS in order to assign the designed workflow for these tasks only.
 
 == Related ==
-^(Here you can add related tasks that could be useful or helpful.)^
+[wiki:TracWorkflow] this document should be useful.
 
 == How to demo ==
-^(In this section you must add instructions for the demo of the task.)^
+Create a new PLANNED_TASK ticket. Change different resolutions.
 
 = Design =