Users

Only Project Manager can have access to the wizard button.

Master project

You can define a master project linked to the business requirement.

The master project will be the parent of any project created via the wizard.

Procedure

1. Create multiple BR linked to one or several master projects

2. fill in the deliverables lines and corresponding resources lines (RL)

3. Properly define your RL description, time and assignee (used for task creation)

4. Confirm and Approve the Business Requirements

5. At that stage you can either

1. Create the project in each business requirement via corresponding button

2. Go to the master project and create the projects for all BR related to the master project

1. The wizard is triggered and you can select the following option regarding the hierarchy of projects

1. Parent project for creation

2. Create sub-projects for Business requirements

3. Create sub-projects for Deliverables

4. Create sub-projects for Child Business requirements

Example

eg: if a master project contains the following BR:

BR1
|
|- Deliverable Line 1 (DL) containing 2 Resource Lines (RL):
|  |
|  |- RL1
|  `- RL2
|
BR2
|
|- DL2
|  |
|  |- RL3
|  `- RL4
|
|- DL3
|  |
|  |- RL5
|  `- RL6
|
|- BR3 (Sub BR of BR2)
   |
   `- DL4
      `- RL7

In the Project creation wizard (above image), if no option is selected:

• No sub project created

• 7 tasks are created in the master project (for RL1~RL7)

If option 1 is selected:

• 3 sub projects (parent is Master project), one per BR

• 7 tasks are created for

  • in project linked to BR1 (2 tasks for RL1 and RL2),

  • in project linked to BR2 (4 tasks for RL3~6),

  • in project linked to BR3 (1 task for RL7)

If option 2 is selected:

• 4 sub projects (parent is Master project), one per DL

• 7 tasks are created for

  • in project linked to DL1 (2 tasks for RL1 and RL2),

  • in project linked to DL2 (2 tasks for RL3~4),

  • in project linked to DL3 (2 tasks for RL5~6) and

  • in project linked to DL4 (1 task for RL7)

If options 1+2 are selected:

• 7 sub projects (parent is Master project), one per BR and one per DL

  • BR1 sub-project contains DL1 sub-project,

  • BR2 sub-project contains DL2 and DL3 sub-projects,

  • BR3 sub-project contains DL4 sub-project

• 7 tasks are created for

  • in project linked to DL1 (2 tasks for RL1 and RL2),

  • in project linked to DL2 (2 tasks for RL3~4),

  • in project linked to DL3 (2 tasks for RL5~6) and

  • in project linked to DL4 (1 task for RL7)

If options 1+3 are selected:

• 7 sub projects (parent is Master project), one per BR and sub-BR

  • BR1 sub-project

  • BR2 sub-project contains BR3 sub-projects,

• 7 tasks are created for

  • in project linked to BR1 (2 tasks for RL1 and RL2),

  • in project linked to BR2 (4 tasks for RL3~6),

  • in project linked to BR3 (1 task for RL7)

If options 1+2+3 are selected:

• 7 sub projects (parent is Master project), one per BR, sub-BR and DL

  • BR1 sub-project contains DL1 sub-project,

  • BR2 sub-project contains BR3, DL2 and DL3 sub-projects,

  • BR3 sub-project contains DL4 sub-project

• 7 tasks are created for

  • in project linked to DL1 (2 tasks for RL1 and RL2),

  • in project linked to DL2 (2 tasks for RL3~4),

  • in project linked to DL3 (2 tasks for RL5~6) and

  • in project linked to DL4 (1 task for RL7)

Contributors

• Eric Caudal<eric.caudal@elico-corp.com>

• Alex Duan<alex.duan@elico-corp.com>

• Xie XiaoPeng<xie.xiaopeng@elico-corp.com>

• Victor M. Martin <victor.martin@elico-corp.com>

Maintainer

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

To contribute to this module, please visit https://odoo-community.org.