Version 4 (modified by deyan, 17 years ago) (diff) |
---|
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:
- Analysis
- Analysis review pending
- Design
- Design review pending
- Implementation
- Implementation (task) review pending
- Testing pending
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. 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
Related
TracWorkflow this document should be useful.
How to demo
Create a new PLANNED_TASK ticket. Change different resolutions.
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository)
Testing
Log
(Link the log of the task here)