Tasks: Difference between revisions

From Planfix
Jump to: navigation, search
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
|description=Tasks
|description=Tasks
}}
}}
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.
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 object Settings defines the task type, where you have the following options:
The [[Objects|object]] settings defines the task type, where you have the following options:


* Add the necessary fields to the task.
* Add the necessary fields to the task.
Line 14: Line 14:
Each task must have an author and a title, while all other attributes are optional.
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.
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.
 
Tasks are the fundamental units of Planfix. In our [https://planfix.com/philosophy/ Planfix's philosophy], tasks play several roles: they are Events, Meetings, Discussions, and any other entities that are essential to your business. Tasks must have a creator and a name; the remaining fields are optional.
Tasks are generally created within a [[Projects | project]]. However, this isn't mandatory: it's perfectly normal to have a task without a project. Tasks can be moved into any available project after they have been created, or they can be moved from one project to another.
 
 
== 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

Roles and access to task

Useful links

Go To