SCS_ISSUE_TRACKER_MAINTENANCE_R1

[Astea]

wiki page: SCS_ISSUE_TRACKER_MAINTENANCE_R1 - effort: 1d

[[BackLinksMenu]]

= 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 [source:/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 [wiki: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 ==
[wiki:SCS_ISSUE_TRACKER_SETUP_R1]

== How to demo ==
Show different ticket reports, ticket and explain usage.

= Design =
Functions must be added to the [source:/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 [wiki: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 =
=== New Custom Fields ===
These functions were added into the [source:/manage/sched/sophie2-wbs.py] file:
 * '''outImportancedEffort'''
  * Overview: The function takes no arguments and generates SQL queries that insert data in the ticket_custom table. This is where the custom fields "importance" and "effort" are stored. This function was used and there is effort and importance for all issues. It will not be used again. If something needs to be changed a function that updates the fields must be used.
  * Usage:
   * Go to the sophie2-wbs.py file folder
   * In the sophie2-wbs.py uncommnet the outImportancedEffort() call
   * Execute: 
{{{
python sophie2-wbs.py | bash
}}}

 * '''outUpdateCustom'''
  * Overview: This function takes one argument: "importance" or "effort". It generates SQL queries that update the information in ticket_custom table according to the [source:/manage/sched/sophie2-wbs.py].
  * Usage:
   * Go to the sophie2-wbs.py file folder
   * In the sophie2-wbs.py uncommnet the outUpdateCustom(sys.argv[1]) call
   * Execute: 
{{{
python sophie2-wbs.py effort | bash
//this will update the effort field
sophie2-wbs.py importance | bash
//this will update the importance field
}}}

=== Unplanned Tasks ===
= Testing =
= Comments =
This task should be implemented after 2008-10-19
= Log =
[[Include(wiki:SCS_ISSUE_TRACKER_MAINTENANCE_R1_LOG)]]

Edit
Edit Log

[deyan]

Changing according to the new workflow.