Enforce the applicants to supplement the most important information to execute the task using task templates, and define the default subtasks to be performed depending on the type of task.
Have you ever participated in an assigned project that lacked essential details? An applicant reporting the task, a month ago, cannot remember the details and again you have to go back to the topic, losing valuable time to find the problem. This results in the downtime for both the applicant and the performer, who wants to start work, but cannot, because basic information is missing.
Task template module comes with help. This module will certainly be useful to everyone and will accelerate the work of both the applicant and the contractor. The task template, apart from the basic parameters such as the name, the assigned project also contains additional fields required to complete during the task submission, and a list of subtasks that will be automatically added to the assigned project. Additional boxes/fields can be of different types:
- text box,
- yes/no checkbox,
- numeric field,
- pre-defined field (user defined dictionary),
- check box (single and multiple),
- multi-line text box (textarea),
- user check box,
In order to better illustrate, please imagine a trivial situation in which a certain person reports an error on the website. He/she gives the name and description in a traditional way. The employee responsible for bug fixes opens the application and rejects asking for more details, such as the name of the browser used and the address of the URL where the problem occurs. The task returns to the applicant. Further steps are probably well known.
Now let's move on to the Fortask application. For tasks, a template was created with the name "Error on the website". The applicant selects this template, proceeds to the next step and is asked to complete the additional fields. He/she selects the name of the web browser from the list and pastes the URL where the problem occurs. Then user adds a task, in which, the following subtasks appear immediately:
- Fix the error,
- Test run request,
- Update the version on the server.
Assign each of the subtasks successively to the programmer, software tester and IT specialist. Everyone performing the task know exactly what is their job and what are the necessary details to in order to complete this ticket.
Of course, the above situation is just a simple but apt example. Naturally, you can easily implement task templates and automate work in every field.
Below is a short video presenting the configuration of the task template described by the example above:
Moreover, we will show you how to add a task with template:
Find out what the other features do
Create a free account