Hello

Assume I have a project as

- Fleet Disposal

- - Van Disposal

- - - Data Collection

- - - - Spare Parts

- - - - - Task 1

- - - - - Task 2

- - - - Mileages

- - - - - Task 1
- - - - - Task 2

My question is what is best practice as far as using Projects all the way until Spare Parts and Mileages or make it as Tasks with a Parent task etc?

Meaning is it better to have many projects or less projects and compensate for that using tasks with Parent Tasks?

Thx
OOzy

Hi,

this depends on what you try to accomplish.

Pro projects

• Projects give you the option to limit who can see the included information (such as work packages) (by only adding people who should have access to the project as project members or limiting their permissions in certain projects (via roles)).
• Projects allow you to enable different custom fields and therefore customize the attributes displayed for work packages

Contra projects

• Increased complexity through multiple projects.
• More complex to filter across multiple projects.

An alternative approach is the use of versions for Spare Parts and Mileages which allows you to filter based on versions and also visualize the different categories e.g. by using the backlogs plugin.
You can also see visually see the progress of these categories (if this is important for you) by navigating to the Roadmap (which shows all versions and their progress).

Best,
Robin