Changes between Version 2 and Version 3 of SCS_ISSUE_TRACKER_MAINTENANCE_R1

Timestamp:

10/10/08 17:13:05 (17 years ago)

Author:

astea

Comment:

--

SCS_ISSUE_TRACKER_MAINTENANCE_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.)^
+This task includes maintaining the issue tracker. 
 
 == Overview ==
 New custom fields might be needed and they must be filled with auto-generated information from the [source:/manage/sched/sophie2-wbs.py] file.
+These custom fields may be usefull:
+ * importance - this field will be usefull for sorting out wiki pages.
+ * effort - the effored planned for the issue.
 
 == Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
+The new fields must be consistent, and scripts for updating them must be provided.
 
 == 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.))^
+An easily maintainable tracker. 
 
 == Implementation idea ==
-These fields may be usefull:
- * importance
- * effort
-They must be added into the trac.ini file and the database must be updated, a python script that generates sqlite script might do the tric.
+The new issue fields must be added into the trac.ini file into the [ticket-custom] section. The database must be updated, a python script that generates sql script might do the trick.
+
 
 == Related ==