Solution phases and task states - their visibility depends on the user rights. We distinguish them as follows:
- Solution phases are user, company or workspace administrator defined phases that a task may be in.
- Task states are the standard task states that each task can be in
- wait for a reaction of the
- Owner - The task in this state will be added to the reaction tasks of the owner of the task. A statement is required from the owner. By expression we mean a comment, which when published by the owner will cancel this task state and automatically switch to the previous state or solution phase.
- Project, team, workgroup - a task in this state will be added to the reaction tasks of the project, team or their workgroups. These tasks will appear in the "Task to react" tab in the project details. These tasks are then available in the meetings of that project, team or their workgroups. WARNING: if a task is in the status waiting for a reaction from the project, team or their workgroups, it does not mean that all members of the project, team or their workgroups have this task in their reaction tasks. The visibility logic of the teams for this feature is governed by the team setup:
- The user will be shown teams with Task reaction visibility set to "All Users",
- An internal user will see teams with Task response visibility set to " Internal users of the company",
- External user will see teams with Task response visibility set to " External users of the company".
- To cancel this state, you can manually cancel it in the menu of the same button. Canceling this state returns the task to the previous state, or to the previous phase of the solution, and ignores the automatic rules for the solver that would be executed by default when manually switching.
- Suspend - the task is in a suspended state, it is not available in any action tasks, but can be additionally viewed via the view (link to views). There are several options available when setting the suspension:
- Unlimited suspension - the task will be permanently suspended and needs to be intentionally searched for,
- Suspend for this week - the task will be suspended until the end of the current week, it will be activated (i.e. the status of the task or the phase of the solution that preceded the suspended status will be set) the day after the end of the week,
- Suspend for this month - the task will be suspended until the end of the current month, it will be activated (i.e. the status of the task or the phase of the solution that preceded the suspended status will be set) the day after the end of the month,
- Selection of a specific date - the task is activated (i.e. the status of the task or the solution phase that preceded the suspended status is set) the day after the selected date,
- TIP 1: The date can be typed manually and confirmed with the ENTER button,
- TIP 2: In the footer of the suspend window, it tells us the date when the task will be active in case of the selected date,
- To cancel this state, you can manually cancel it in the menu of the same button. Canceling this state returns the task to the previous state, or to the previous phase of the solution, and ignores the automatic rules for the solver that would be executed by default when manually switching.
- Request closure - this task state is available if we enable the function "Only task with a closing request can be closed " in the workspace settings. In this case, the job owner is asked to close the task and can accept or decline the closure,
- Close - a task in the closed state is considered successfully completed. In the workspace settings, you can set additional rights on who can close the task. In a closed or cancelled task, only records with private or internal privacy can be added (for an external user, neither private nor private). Exceptions are to-do and subtasks, which cannot be added at all,
- Request for cancelation - this task state is available if we enable the function "Only task with a closing request can be closed" in the workspace settings. In this case, the cancellation of the task is requested by the owner of the task, who can accept or decline the cancellation,
- Cancel - a task in the cancelled state is also considered completed, but this state is different from the closed state. It is assumed that a cancelled task has no meaning. in the workspace settings it is also possible to set additional rights for who can cancel a task and also whether we want to cancel a task based on a cancellation request.
Buttons for changing the phase of solving the task and the state of tasks are complemented by the button for taking over the solution, “Assign me” - after pressing it, the solver is automatically set to the user who pressed the button.
