wiki:SCS_ISSUE_TRACKER_MAINTENANCE_R2

Version 1 (modified by deyan, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=TASK_NAME_HERE, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

Since there are sub-teams now a new custom field is added. Wiki is now migrated to Postgresql instead of sqlite so the functions of the previous revision of this task should be corrected or commented.

Task requirements

Functions that should be corrected in manage/sched/sophie2-wbs.py

These functions were added into the 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 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
        

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.))

Implementation idea

(It is advisable to include some rough implementations ideas.)

(Here you can add related tasks that could be useful or helpful.)

How to demo

(In this section you must add instructions for the demo of the task.)

Design

Implementation

(Implementation results should be described and linked here (from the wiki or the repository))

Testing

Comments

(Write comments for this or later revisions here.)