Planfix use cases: Difference between revisions
From Planfix
No edit summary |
No edit summary |
||
Line 21: | Line 21: | ||
*Classroom delivery | *Classroom delivery | ||
* ... | * ... | ||
---- | |||
'''Project: Orders on eshopexample.com''' | |||
Tasks: | |||
*Order #125948 | |||
*Order #125949 | |||
*Order #125950 | |||
*Order #125951 | |||
*Order #125952 | |||
*... | |||
(About the last example: You can use the Task-Email feature to automatically upload tasks from different sources) |
Revision as of 04:59, 10 March 2019
The main entities that Planfix uses are Projects, Tasks, and Actions (more about using them). These names don't mean you can only use Planfix for project-based work. Here are some examples of project and task names that illustrate different use cases for Planfix:
Project: Opening a store at W 89th St
Tasks:
- Order furniture
- Health clearance
- Firefighters: purchase equipment
- Firefighters: get licensed
- ...
Project: Working with Office Inc.
Tasks:
- 2 printers and a fax machine
- Laptop for chief accountaint
- Meeting with boss
- Classroom delivery
- ...
Project: Orders on eshopexample.com Tasks:
- Order #125948
- Order #125949
- Order #125950
- Order #125951
- Order #125952
- ...
(About the last example: You can use the Task-Email feature to automatically upload tasks from different sources)