wiki:SCS_ISSUE_TRACKER_SETUP_R1

Version 20 (modified by astea, 17 years ago) (diff)

--

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

Analysis

Overview

Decided to try to use Ticket system more efficiently. This includes using ticket systems for every task's change to see what is the status of each task, use assign to, etc.

Task requirements

Create new ticket resolutions:

  • analyzing - Analyzing (task in analysis process)
  • analyzed - Analyzed (this means the task is analysis is done and is pending for review)
  • analysis accepted - Analysis OK (task analysis reviewed and the result is >=3)
  • designing - Designing (task in design process)
  • designed - Design ready (pending review)
  • design accepted - Design OK (task design reviewed and the result is >=3p)
  • implementing - Implementing (task is currently being implementated)
  • implemented - Implementation ready (pending review)
  • implementation accepted - Implementation OK - implementation of task passes review. The result of this review is score for the whole task's revision (SuperScore)

Task result

Issue tracker capable of handling tasks' whole process.

Implementation idea

Create the resolutions listed in Task Requirements section. Design a workflow. Try to separate PLANNED_TASKS in order to assign the designed workflow for these tasks only.

Backup first!

Use

[ticket-workflow]
accept = new,assigned,accepted,reopened -> accepted
accept.operations = set_owner_to_self
accept.permissions = TICKET_MODIFY
leave = * -> *
leave.default = 1
leave.operations = leave_status
reassign = new,assigned,accepted,reopened -> assigned
reassign.operations = set_owner
reassign.permissions = TICKET_MODIFY
reopen = closed -> reopened
reopen.operations = del_resolution
reopen.permissions = TICKET_CREATE
resolve = new,assigned,accepted,reopened -> closed
resolve.operations = set_resolution
resolve.permissions = TICKET_MODIFY
proceed = new -> analyzing
proceed = analyzing -> analyzed
proceed = analyzed -> an-OK,new
proceed = an-OK -> designing
proceed = designing -> designed
proceed = designed -> de-OK,an-OK,new
proceed = de-OK -> implementation
proceed = implementation -> im-OK,de-OK,an-OK,new
proceed = im-OK -> closed
proceed.operations = set_resolution
proceed.permissions = TICKET_MODIFY

in /home/dan/env/conf/trac.ini

TracWorkflow this document should be useful.

How to demo

Create a new PLANNED_TASK ticket. Change different resolutions.

Design

The diagram below shows what our workflow will look like. The transitions available are:

  • accept - this is when s.o. accepts to analyse, design, implement ot test a task, with this transition the task's owner is automaticly changed to self.
  • done - finnished designing, implementing, etc. It is a must to write a comment including the time spended on working.
  • review fail - the review has failed. Reasons and scores must be written as a comment. With this transition the task's owner is automaticly changed to self.
  • review ok - the review has passed. Scores and remarks must be written as a comment. With this transition the task's owner is automaticly changed to self.
  • reassign - this transition is available at any state of the issue it does not change da current state, just the owner of the issue.
  • resolve - this is a transition to finalise the issue, it leads to a closed state with a specific resolution ( fixed, invalid, wontfix, duplicate, worksforme, etc ). This is also availbla at any state of the issue.

source:/trunk/sophie2-platform/doc/uml-design-diagrams/workflow.png

Some issues may not need testing, we can resolve these issues after "implementation accepted"

Implementation

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

Testing

Log

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