Top Menu

Jump to content
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    Home
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      OpenProject ID Google

Side Menu

Collapse project menu
  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Expand project menu
General discussion
  1. OpenProject Community
  2. OpenProject
  3. Forums
  4. General discussion
  5. Project or Workpackage Hierarchy best practices

Project or Workpackage Hierarchy best practices

Added by OOzy Pal over 9 years ago

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


Replies (1)

RE: Project or Workpackage Hierarchy best practices - Added by Robin Wagner over 9 years ago

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

  • (1 - 1/1)
Loading...