Approving Tasks

What is approval?

Approval is the phase in task's life cycle where we specify it to the level it is needed to implement this task. So we can say that if approval is done, we have specified every possible detail and answered every possible question of developer who will implement this task.
Approval is meant to guarantee the quality of input to your developers.

The purpose of approval is to decide whether the given task has to be implemented and to make sure necessary information is present before sending it to implementation. Tasks move to the state “awaiting approval” after being added via the short form.

Here is an example of task waiting to go to implementation:

How to approve

To guarantee that the task is ready for implementation, make sure that:

the content of the task is thoroughly described
in case of a bug – the steps for reproducing, desired behaviour and current behaviour are described
with other task types – the desired behaviour is described
the type of the task is set
the right component is set
the priority is set

Finishing approval

To move the task to the state “awaiting implementation”, it is necessary to choose action “Approval is finished (task will be implemented and contains all necessary information for implementation.)”

... and here are the possible actions that could be executed:

Other actions

If the task has already been implemented, you need to choose the action “Task is implemented (change xxxx), send to verification”. It is recommended to enter the change ID, if the task was implemented through a change.

If the task is a duplicate of another task, then you need to choose action “This task is duplicate of task xxxx, send to verification”, it is mandatory to enter the ID of the duplicating task, the current task moves on to the state “awaiting verification”

Negative solutions

If you decide that this task should not be implemented, then choose the action “Task will not be implemented, send to verification with resolution” and choose one of the following resolutions

invalid
cannot reproduce – works for me
won't implement
later – in that case the task will move to state “abandoned”

Adding a comment

Additional information, ideas or opinions concerning a task can be freely added in form of a comment. User commenting a task will be automatically added to the task's “persons to be notified” and will receive a notification everytime the task is updated.