Trac Ticket Workflow

Trac is the wiki and issue tracking system that is the most used for my software development projects. Let me share few hints about its ticket workflow, especially about the statuses, the roles of the participants, and let me give an example of the workflow config. But if you are interested in other things like Trac plugins, source browser, customizing, etc, let me know.

All the information given below regards the workflow described at the end of the article. The original Trac workflow is missed vital features like the support for ticket verifying, or the required ticket statuses range, so I do not use it in my projects.


The description of the main statuses:
  • new - the ticket has been created;
  • in-progress - the developer has began to work with the ticket;
  • fixed - the ticket is fixed (the problem issued in the ticket is solved);
  • verified - the ticket is verified (tester or PM has verified that the ticket is fixed correctly);
  • closed - the ticket is closed (it's not required to care about the ticket more).
Testers/PM have to do either of these things:
  • add comments for the ticket (with some clarifications, explanations, etc);
  • return the ticket into the work (via "ticket need to be re-worked" option) if they see that the bug/problem have not been fixed correctly;
  • verify that the ticket is fixed correctly (via "mark as verified" option);
  • create a new ticket with suitable description.
If testers/PM return the ticket into the work, they should add some comments to help the developers understand that they has done incorrectly.

Developers have to do either of these things:
  • accept the ticket for fixing (in that ways others can see on which tickets the developer works on);
  • set a suitable status for the ticket (fixed if it has been fixed, invalid if there are some problems preventing from the ticket been fixed, etc);
  • reassign ticket to other participants (for example, to other developer who is responsible for the problem issued in the ticket).
There can be other roles and actions, but it is not strict, and can vary in different cases. You can create your own workflow, which can be more suitable for your company or for the way you prefer to work.

In conclusion, let me give an example of the Trac ticket workflow (it should be specified in the trac.ini file):

[ticket-workflow]
accept = new -> in-progress
accept.name = accept ticket
accept.operations = set_owner_to_self
accept.permissions = TICKET_MODIFY
leave = * -> *
leave.default = 1
leave.operations = leave_status
reassign = new, in-progress -> new
reassign.operations = set_owner
reassign.permissions = TICKET_MODIFY
reopen = closed -> new
reopen.operations = del_resolution
reopen.permissions = TICKET_CREATE
resolve1 = fixed, verified -> closed
resolve1.name = resolve
resolve1.operations = set_resolution
resolve1.permissions = TICKET_MODIFY
resolve1.set_resolution = Done, Invalid, Duplicate
resolve2 = new -> closed
resolve2.name = resolve
resolve2.operations = set_resolution
resolve2.permissions = TICKET_MODIFY
resolve2.set_resolution = Invalid, Duplicate, WontFix
resolve3 = in-progress -> closed
resolve3.name = resolve
resolve3.operations = set_resolution
resolve3.permissions = TICKET_MODIFY
resolve3.set_resolution = WorksForMe, Invalid, Duplicate, WontFix
setfixed = in-progress -> fixed
setfixed.name = mark as fixed
setfixed.permissions = TICKET_MODIFY
setinprogress = verified, fixed -> in-progress
setinprogress.name = ticket need to be re-worked
setinprogress.permissions = TICKET_MODIFY
setverified = fixed -> verified
setverified.name = mark as verified
setverified.permissions = TICKET_MODIFY

Comments

Post a Comment

Popular posts from this blog

Web application framework comparison by memory consumption

Memory consumption is slightly specific to my area of software development now, but I did some research recently and maybe these results can be useful for others. Of course, I know that precious comparison is very difficult to carry out, but actually I needed only overall picture. And let me admit that results are pretty interesting and even frustrated (at least for me). As a basis I took so-starving project, and measured initial RSS (Resident Set Size) of the each process (local development webservers). Platform: x86_64 Linux (latest Ubuntu with all updates). As a reference, here is the RSS of the interpreters in interactive console mode: Interpreter Version RSS (kB) stackless python 2.6.4 3916 ruby (via irb) 1.8.7 4664 python 2.7.1 5624 php 5.3.5 6924 v8 (via node.js shell) 2.5.9.9 8796 One more reference - the most simplest WSGI app ( example  in the Python documentation). It's RSS: 7336 Kb , so I assume it's almost impossible to consume l
Read more

Python vs JS vs PHP for embedded systems

UPDATE (07/18/17): The original article was written in 2011 and pretty much outdated, I've updated the numbers and conclusions. I've got a question about which programming language is preferable for the website development for embedded systems (with limited resources). Here is my small investigation in a table form. Please note that the question was about only these 3 programming languages - there are better candidates for the embedded systems now (for example, Rust). The Memory and Performance overhead numbers are based on the n-body benchmark and calculated as relatives to "C gcc #4" measurements. Python 3 Node.js PHP Memory Overhead x7.62 x29.04 x8.53 Type System Strong Typing Weak Typing Weak Typing Vulnerabilities 220 1411 5626 Performance Overhead x78.31 x2.82 x30.12 Documentation Excellent Excellent Average C Bindings Excellent Average Poor Code Readability With PEP8 it can be almost perfect ESLint enforces very good style PEAR Coding Stan
Read more