Ticket #1517 (closed planned_task: obsolete)

Opened 17 years ago

Last modified 15 years ago

SCHEDULE_WBS_DEPENDENCIES_R1

Reported by: Astea Owned by: todor
Priority: 3 Milestone: M02_PRE2
Component: SCHEDULE Version: 2.0
Keywords: Cc:
Category: SUPPORT Effort: 2
Importance: 99 Ticket_group:
Estimated Number of Hours: Add Hours to Ticket:
Billable?: Total Hours:
Analysis_owners: todor Design_owners: pav
Imp._owners: pav, todor Test_owners:
Analysis_reviewers: pav Changelog:
Design_reviewers: todor Imp._reviewers:
Test_reviewers: Analysis_score: 3
Design_score: 0 Imp._score: 0
Test_score: 0

Description (last modified by pacitu) (diff)

Error: Macro BackLinksMenu(None) failed
operator does not exist: text = integer
LINE 1: ...,author,text,comment,readonly FROM wiki WHERE name=1517 ORDE...
                                                             ^
HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.

Analysis

Overview

Our workflow was affected of bad tasks sorting due to the lack of dependences between the tasks. If we manage to organize the list of the tasks for this iteration we could save a lot of time and our work will be more purposive and easy.

Task requirements

For this revision of the task you must:

  • Sort the tasks for this iteration
  • (optional) Sort the tasks for the next iterations
  • Put dependences in the tickets

Task result

The result of this task must be sorted wiki page for this (and if possible for next) iteration.

Implementation idea

Think about the integration between the sorting and the wiki ticket system.

SCHEDULE_WBS_DEPENDENCIES_R0

How to demo

Open the iteration page. The tasks must be sorted according to their dependencies and priority.

Design

We have to do the following:

  • manually sort the tasks for this iteration
    • sort them by order from 10 to 99
    • start with default 10 value for each of them
    • some tasks can be with equal value
  • create "order" field in manage/sched/sophie2-wbs.py and use it to sort the tasks for this iteration
  • use the "order" field to sort the other tasks if we have enough time
  • put dependencies in the tickets using the result of the manual sort

Implementation

We've ordered the tasks in sophie2-wbs.py , for now we won't use the tickets. In this implementation we:

  • Created list with the ordered tasks for this iteration.
  • Added imp (importances) for the tasks from this iteration in sophie2-wbs.py
  • Exported ordered tasks for this iteration from the python file
  • the function doing this is outIterationWiki(currentMilestone)

Testing

Comments

Log

Error: Macro Include(wiki:SCHEDULE_WBS_DEPENDENCIES_R1_LOG) failed
current transaction is aborted, commands ignored until end of transaction block


Edit
Edit Log

Change History

comment:1 Changed 16 years ago by todor

  • Owner changed from Astea to todor
  • Status changed from new to analyzing

comment:2 Changed 16 years ago by todor

  • Status changed from analyzing to analyzed

comment:3 Changed 16 years ago by todor

  • Status changed from analyzed to analysis_accepted

comment:4 Changed 16 years ago by todor

  • Status changed from analysis_accepted to designing

comment:5 Changed 16 years ago by todor

  • Status changed from designing to designed

comment:6 Changed 16 years ago by todor

  • Status changed from designed to design_accepted

comment:7 Changed 16 years ago by todor

  • Status changed from design_accepted to implementing

comment:8 Changed 16 years ago by todor

  • Status changed from implementing to implemented

comment:9 Changed 16 years ago by todor

  • Status changed from implemented to implementation_accepted

comment:10 Changed 16 years ago by pacitu

  • Status changed from implementation_accepted to closed
  • Resolution set to fixed
  • Description modified (diff)

Review: 3.5 by Pap. The task was done good and when needed. No dependencies were added for the tickets due to 150% timeboxing.

comment:11 Changed 16 years ago by deyan

  • Status changed from closed to s3c_implementation_ok

Closed status should not be used

comment:12 Changed 16 years ago by pavlina

  • Design_owners set to Pavlina
  • Imp._owners set to Pavlina
  • Analysis_reviewers set to Pavlina
  • Analysis_score set to 3
  • Test_score set to 0
  • Design_score set to 0
  • Imp._score set to 0

comment:13 Changed 16 years ago by todor

  • Design_reviewers set to todor
  • Imp._owners changed from Pavlina to Pavlina, todor
  • Analysis_owners set to todor

comment:14 Changed 16 years ago by deyan

  • Design_owners changed from Pavlina to pav
  • Imp._owners changed from Pavlina, todor to pav, todor
  • Analysis_reviewers changed from Pavlina to pav

Batch update from file newimport.csv

comment:15 Changed 15 years ago by deyan

  • Status changed from s3c_implementation_ok to closed
  • Resolution changed from fixed to obsolete

Batch update from file query-obsoleted.csv

Note: See TracTickets for help on using tickets.