Changes between Version 4 and Version 5 of SCS_ISSUE_TRACKER_MAINTENANCE_R1


Ignore:
Timestamp:
10/13/08 16:14:20 (17 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SCS_ISSUE_TRACKER_MAINTENANCE_R1

    v4 v5  
    22 
    33= Analysis = 
    4 This task includes maintaining the issue tracker.  
    5  
    64== Overview == 
     5This task includes maintaining the issue tracker and testing the new workflow. 
     6== Task requirements == 
     7The new fields must be consistent, and scripts for updating them must be provided. 
    78New custom fields might be needed and they must be filled with auto-generated information from the [source:/manage/sched/sophie2-wbs.py] file. 
    89These custom fields may be useful: 
    910 * importance - this field will be useful for sorting our wiki pages. 
    1011 * effort - the effort planned for the issue. 
    11  
    12 == Task requirements == 
    13 The new fields must be consistent, and scripts for updating them must be provided. 
    14  
     12Should discuss and test the new work flow at the end of this week (2008-10-19). Should be decided what will be the process. 
    1513== Task result == 
    1614An easily maintainable tracker.  
    17  
    1815== Implementation idea == 
    19 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. 
    20  
    21  
     16The 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. In the next weekly should be discussed observations of the new workflow. 
    2217== Related == 
    23 ^(Here you can add related tasks that could be useful or helpful.)^ 
     18[wiki:SCS_ISSUE_TRACKER_SETUP_R1] 
    2419 
    2520== How to demo == 
    26 ^(In this section you must add instructions for the demo of the task.)^ 
    27  
     21Show different ticket reports, ticket and explain usage. 
    2822= Design = 
    29  
    3023= Implementation = 
    3124^(Implementation results should be described and linked here (from the wiki or the repository)^ 
    3225 
    3326= Testing = 
    34  
     27= Comments = 
     28This task should be implemented after 2008-10-19 
    3529= Log = 
    36 ^(Link the log of the task here)^ 
     30[[Include(wiki:SCS_ISSUE_TRACKER_MAINTENANCE_R1_LOG)]]