Several assignees (developer, reviewer, tester) for tickets to Trac

Question

We recycle our workflow and look for options between jira and trac. We are all happy with Trac, but you have the following questions:

• We want every ticket to have 3 people. One of them is developing it, the other is considering it and the third person checking it. We need some preliminary options that the same person cannot develop and check / check a ticket.

• We need a separate cycle for these three people. After development and completion, it automatically proceeds to the reviewer and tester. They can individually carry out their actions and after they have been approved by the browser and tested, he proceeds to the next stage. This workflow is possible with Trac. If so, how do I do this?

Thanks Sparsh Gupta p>

Answer 1

You can do this with Trac (the team at my company does something similar), but it will require some configuration work.

First, you need the opportunity to assign three people to the ticket. To do this, add custom tab fields (enter "text") with names such as "Reviewer" and "Tester". They will be used to store the names of non-developers assigned to the ticket.

You will also want to add a new state to the workflow of the Trac Total Station to represent the state in which testing and verification is being performed. For the sake of discussion, I will call this state “verification.” Insert this state into the workflow so that the ticket moves from the assigned / accepted → check → closed.

You will also need some way for the tester and reviewer to indicate that they have subscribed to the changes. To do this, you can add two more custom fields (such as "checkbox") to the ticket. You can name these "Review Complete" and "Test Complete." These tickets will be canceled by default and the tester / reviewer will check them as soon as they have successfully completed their testing / reviewing work.

This should get you started. Regarding some of the more advanced parts of your question, you have several options.

You can add some custom javascript that will prevent the user from being listed in multiple owner fields. Javascript will run whenever the owner, reviewer, or tester field is changed. If the new value in this field matches the value in one of the other two fields, the other field will be cleared. Instead of writing custom Javascript, one of the following plugins can do this for you:

• DynamicFieldsPlugin
• TicketValidatorPlugin
• TicketSubmitPolicyPlugin

Answer 2

With a custom Trac workflow, this may be possible (depending on how much flexibility you need). Basically, you can set side effects when a status changes (for example, change the assignee).

Answer 3

I think this is a complex issue, independent of the tool you want to use. The reasons are as follows:

• If 3 people are responsible (at the same time), how does each person know when they need to do something?
• If 3 people are responsible depending on the work process, how do you set up, which person is responsible, when?
• You need to integrate this into your workflow, and JIRA or Trac cannot do this out of the box.

A possible solution may be (and no, I do not implement it for you :-):

• Define a workflow with states and transitions.
• Identify the fields developing the assignee, consider the assignee and the target assignee.
• Define in your workflow where the transfer of the real successor switches from design to validation to validation.

And yes, it is difficult and difficult to implement. But it can be worth it if you use it hundreds of times every day. In addition, an organizational decision would be sufficient when one assignee would change to the next when starting transitions.