Tasks: Difference between revisions
From Planfix
No edit summary |
No edit summary |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
Tasks | {{#seo: | ||
|title=Tasks | |||
|titlemode=append | |||
|keywords=planfix, tasks | |||
|description=Tasks | |||
}} | |||
A '''task''' is the most important unit of information in Planfix. According to [https://planfix.com/philosophy/ Planfix's philosophy], a task serves multiple roles — an event, a meeting, a discussion, or any other entity your company needs. | |||
The [[Objects|object]] settings defines the task type, where you have the following options: | |||
* Add the necessary fields to the task. | |||
* Specify which statuses the task passes through in its life cycle. | |||
* Configure automatic scripts and additional buttons to simplify task management. | |||
Each task must have an author and a title, while all other attributes are optional. | |||
Tasks are normally created within a project, but this is not mandatory. Tasks without a [[Projects |project]] are perfectly acceptable in the system. In addition, each task can be assigned to an available project or moved from one project to another, even after it has been created. | |||
== General information == | == General information == | ||
*[[Importing tasks]] | *[[Importing tasks]] |
Latest revision as of 14:14, 22 November 2024
A task is the most important unit of information in Planfix. According to Planfix's philosophy, a task serves multiple roles — an event, a meeting, a discussion, or any other entity your company needs. The object settings defines the task type, where you have the following options:
- Add the necessary fields to the task.
- Specify which statuses the task passes through in its life cycle.
- Configure automatic scripts and additional buttons to simplify task management.
Each task must have an author and a title, while all other attributes are optional.
Tasks are normally created within a project, but this is not mandatory. Tasks without a project are perfectly acceptable in the system. In addition, each task can be assigned to an available project or moved from one project to another, even after it has been created.
General information
- Importing tasks
- Task cards
- How to create a new task?
- Task number
- Task statuses
- Custom task statuses
- Checklists
- Subtasks
- Parent tasks
- Individual tasks for each assignee
- Task templates
- Templates for automatic tasks for new employees
- Task filters
- Gantt charts and connections between tasks
- Displaying custom fields when viewing a task
- Custom task fields
- Sequential tasks
- Overdue task
- Tasks without mandatory result checking
- Summary tasks
- Variables in task templates
- Task merging
- General chat
- Dynamic blocks
Roles and access to task
- Task assigner
- Task assignees
- Task participants
- Task auditor
- Counterparty
- Permissions in Planfix
- Table with permissions for access to tasks, by role
- Request to get access to a task
- How to restrict task access?
- Who gets notifications about new tasks?
Useful links
- Bulk task actions
- What kind of limit is there on task nesting?
- Can I move subtasks between tasks?
- What does a task's color mean?
- How quickly can I find the task I need?
- How to restore a deleted task?
- How to create a recurring task?
- How to prioritize tasks?
- How to view task work history?
- Why am I not receiving notifications about a task?
- How do I assign a task by email?
- Task email addresses
- How do I assign a task to a user from a different Planfix account?
- How do I delete myself from a task's assignees?
- Determining a task's assignee with competitive assignment
- Manual task sorting
- Quick access to recently viewed tasks