|
| 1 | +================= |
| 2 | +Project templates |
| 3 | +================= |
| 4 | + |
| 5 | +Templates allow you to create new projects with predefined settings, reducing the need to manually |
| 6 | +set up similar projects repeatedly. |
| 7 | + |
| 8 | +Creating templates |
| 9 | +================== |
| 10 | + |
| 11 | +To create a project template, an existing project is required and used as a base to be converted |
| 12 | +into a template. Converting a project into a template transfers the entire project's properties to |
| 13 | +the template. This includes the project’s stages, tasks, sub-tasks, and their respective |
| 14 | +configurations, such as planned dates, statuses, assignees, and more. |
| 15 | + |
| 16 | +Access the settings of the project that you want to convert into a template: go to |
| 17 | +:guilabel:`Projects`, hover your mouse on a project card, click the :icon:`fa-ellipsis-v` |
| 18 | +(:guilabel:`fa-ellipsis-v`) icon on one of your projects, and click on :guilabel:`Settings`. Review |
| 19 | +and adjust the project’s properties to ensure it reflects your desired template setup. |
| 20 | + |
| 21 | +Once your project is ready, click the :icon:`fa-cog` (:guilabel:`cog`) icon and select |
| 22 | +:guilabel:`Convert to Template`. The :guilabel:`Template` banner indicates that the project has been |
| 23 | +successfully converted into a template. |
| 24 | + |
| 25 | +.. warning:: |
| 26 | + Converting a project into a template will also archive the original project used to create the |
| 27 | + template. To keep in your database a project that you want to convert into a template, duplicate |
| 28 | + the project and convert the copy into the template: go to :guilabel:`Projects`, click the |
| 29 | + :icon:`fa-ellipsis-v` icon on one of your projects, and then click :guilabel:`Duplicate`. Then |
| 30 | + convert the copy into the template. |
| 31 | + |
| 32 | +To edit a template, go to :menuselection:`Projects --> New`, and click the |
| 33 | +:icon:`fa-pencil` (:guilabel:`pencil`) icon next to the name of the template that you want to edit. |
| 34 | +Make the changes according to your needs, and click :guilabel:`Save`. Editing a template does not |
| 35 | +affect the projects that were previously created from it. |
| 36 | + |
| 37 | +To delete a template, go to :menuselection:`Projects --> New`, and click the |
| 38 | +:icon:`fa-trash` (:guilabel:`trash`) icon. Click :guilabel:`Ok` to confirm. Deleting a template |
| 39 | +does not erase projects that were previously created from it. |
| 40 | + |
| 41 | +Using templates |
| 42 | +=============== |
| 43 | + |
| 44 | +To create a new project from a template, go to :menuselection:`Projects --> New`, and click on a |
| 45 | +template in the :guilabel:`Project Templates` section. Enter a name for your project. Optionally, |
| 46 | +add a :guilabel:`Customer`, a :guilabel:`Planned Date`, and set up the task creation email. Then, |
| 47 | +click :guilabel:`Create Project`. |
| 48 | + |
| 49 | +Templates can also be used when creating a project directly from a sales order. To do so, the |
| 50 | +project template must be set as :guilabel:`Billable` first: click on :menuselection:`Projects --> |
| 51 | +New`, and click the :icon:`fa-pencil` (:guilabel:`pencil`) icon next to the name of the |
| 52 | +template you want to edit. Then, click on the :guilabel:`Settings` tab, tick the |
| 53 | +:guilabel:`Billable` checkbox, and click :guilabel:`Save`. Once this is done, you can use a template |
| 54 | +to automatically create a project when a product is sold: Go to the :guilabel:`Sales` app, click on |
| 55 | +:menuselection:`Products --> Products --> New`. Select :guilabel:`Service` as the |
| 56 | +:guilabel:`Product Type`, and choose :guilabel:`Project` or :guilabel:`Project & Task` in the |
| 57 | +:guilabel:`Create on Order` field. Then, select a :guilabel:`Project Template` and click |
| 58 | +:guilabel:`Save`. |
| 59 | + |
| 60 | + |
| 61 | +Project roles in templates |
| 62 | +========================== |
| 63 | +Templates enable you to pre-select specific roles for tasks within your template, making the |
| 64 | +selection of assignees faster during the creation of a new project using a template. |
| 65 | + |
| 66 | +Go to :menuselection:`Projects --> New`, and click the :icon:`fa-pencil` (:guilabel:`pencil`) |
| 67 | +icon next to the name of the template you want to edit. Then click on the :guilabel:`Tasks` smart |
| 68 | +button, and on one of the tasks. In the :guilabel:`Project Roles` field, type or select the roles |
| 69 | +that you want to perform this task, then click :guilabel:`Save`. |
| 70 | + |
| 71 | +Create a project based on this template: go to :menuselection:`Projects --> New`, and click on |
| 72 | +the name of the template. The :guilabel:`Create a project from template` form then includes |
| 73 | +:guilabel:`Project Roles`. For each of them, you can select assignees by clicking on the |
| 74 | +:guilabel:`Assignees` field. This automatically dispatches the right tasks to the right employees. |
| 75 | + |
| 76 | +Task scheduling in templates |
| 77 | +============================ |
| 78 | +In a project template, task scheduling can be automated according to the planned dates specified |
| 79 | +within the template. |
| 80 | + |
| 81 | +.. important:: |
| 82 | + Project and task planned dates are not saved when converting a project into a template. These |
| 83 | + require to be added to the template after it is created. |
| 84 | + |
| 85 | +On the project template, define the :guilabel:`Planned dates` for both the project and each task. |
| 86 | +When tasks have planned start dates in the template, Odoo calculates the number of working days |
| 87 | +between the project’s start date and the first scheduled task. This time window is referred to as |
| 88 | +the *delta*. |
| 89 | + |
| 90 | +When a new project is generated from this template: |
| 91 | + |
| 92 | + - The system uses the project’s start date as a reference. |
| 93 | + - Each task’s start date is automatically planned according to its delta. |
| 94 | + - If no start date is set on the new project, the current date is used as the default start date. |
| 95 | + - Task end dates are then determined automatically by Odoo’s scheduling algorithm. |
| 96 | + |
| 97 | +.. note:: |
| 98 | + To ensure that all project roles and tasks are planned without conflict according to the team’s |
| 99 | + availability and workload, the scheduling algorithm calculates the end date of each task based on |
| 100 | + the allocated time, while also considering task dependencies and assignee’s availability, working |
| 101 | + schedule, time off, and public holidays. |
0 commit comments