Version 12 (modified by astea, 17 years ago) (diff) |
---|
Analysis
Overview
This task includes maintaining the issue tracker and testing the new workflow.
Task requirements
New custom fields might be needed and they must be filled with auto-generated information from the manage/sched/sophie2-wbs.py file. These custom fields may be useful:
- importance - this field will be useful for sorting our wiki pages.
- effort - the effort planned for the issue.
The new fields must be consistent, and scripts for updating them must be provided. Should discuss and test the new work flow at the end of this week (2008-10-19). Should be decided what will be the process. Define rules for the unplanned tasks - what happens when unplanned task appears.
Task result
New fields in the wiki. Scripts that should be linked in the backup task. Wiki page UnplannedTasks describing what is done with the unplanned tasks, where and how are they added.
Implementation idea
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. In the next weekly should be discussed observations of the new workflow. Create a wiki page and define rules for unplanned tasks.(where are they added, how the sprint effort depends on their effort, etc.
Related
How to demo
Show different ticket reports, ticket and explain usage.
Design
Functions must be added to the manage/sched/sophie2-wbs.py file:
- outImportanceEffort - that generates SQL script to instert data in the new custom fields. This will be done only once.
- outUpdateCustom - that generates SQL script to update data in the new custom fields
These functions will generate SQL script that can be applied to the trac database. We are using SQLite so we can apply SQL scripts with:
sqlite3 /path/to/database "sql script"
In UnplannedTasks :
- name convention for unplanned tasks
- where to add them in the global schedule
- how to add them
- create ticket for each task, ticket requirements.
- manually in sprint page.
- rules about relationship with other tasks, if planned and unplanned overlap.
Implementation
(Implementation results should be described and linked here (from the wiki or the repository)
Testing
Comments
This task should be implemented after 2008-10-19
Log