<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><p><strong>In this guide we will cover:</strong></p><p><strong>- Default project behaviour</strong></p><p><strong>- Have all projects created from Sales Orders be created under a Parent Project</strong></p><p><strong>- Billing when using Sales Order Parent Project Templates</strong></p><p><br></p><p><br></p><p><br></p><p><strong><span style="font-size: 14pt;">Default Project behaviour</span></strong></p><p>Projects in Halo can be created automatically from a Sales Order line, for information on how this works and how to configure this see our guide <a data-fr-linked="true" href="https://usehalo.com/halopsa/guides/2035" id="isPasted" target="_blank" rel="noopener noreferrer"><strong>here</strong></a>. Projects typically have two levels of hierarchy, the top level being the 'project' and the bottom level being the 'project task'. However, you can have as many levels of project tasks within a projects as you would like. When a project is created from a sales order the project will be created with the tasks as child tickets within this project. Additional tasks can be added to this project, or tasks of the project, from sales order lines, when additional lines are added to an existing project they are created as child tickets within the chosen project. We recommend using this functionality.</p><p><br></p><p><strong><span style="font-size: 14pt;">Have all projects created from Sales Orders be created under a Parent Project</span></strong></p><p>If you create particularly large projects from sales orders you may want to have an additional level of project hierarchy applied automatically. Such as if you are selling various related projects to a single customer, each project having their own set of tasks. You may benefit from grouping these projects together under a singular parent (or master) project ticket, but still have the tasks separated into the project they relate to. We do not recommend using this functionality unless specifically required as grouping projects this way creates a project ticket that does not require action, the ticket itself is only used to organise other project tickets. </p><p><br></p><p>In order to do this you will need to have projects created from sales order lines be created under another project template, we refer to this template as the 'parent project template'.</p><p><br></p><p>To set this up head to configuration > sales orders, see the setting 'Sales Order Parent Project Template'. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjcxODY4MTc0LWY1ZTgtNDNjMi1hYjc1LTEzNDNhMDViNTM4YiJ9.nTvTLpN_LcXksQ4CYhe1jcD94BMvGa3egXZw-fifw3o" class="fr-fic fr-fil fr-dib" width="674" style="width: 676px; height: 305.395px;" height="305"></p><p><strong><span style="font-size: 10pt;">Fig 1. Template to apply to projects created from sales order lines</span></strong></p><p><br></p><p>This setting is used have a parent project template be applied to projects that are created from sales orders. That is, any projects created from sales order lines will be created as a child ticket within this template, with their child tickets/tasks then created as grandchild tickets. Adding an additional level of hierarchy to the project.</p><p><br></p><p>As this is a global setting the template you select in this field should be very generic and not contain any child tickets. We recommend configuring a new template for this use. </p><p><br></p><p>To create a new template head to configuration > tickets > templates > new template. Name the template something like 'Master project' or 'Grandfather project' and add it to your templates project group. Set the ticket type and summary for the template, the summary can be changed to be more specific once the project is created, for now call it something generic like 'Master project'. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY1MDBkYzk4LTE2OGYtNDdmNi04YTVlLTIzNDBjODg5YzdmNSJ9.jI8OGlakNcBaMLNrwbAN1b9lFGFeHqaq-3SzU0Vk--0" class="fr-fic fr-fil fr-dib" width="857" height="509"></p><p><strong><span style="font-size: 10pt;">Fig 2. Template for master/grandfather ticket</span></strong></p><p><br></p><p>Now this template this created set this as the 'parent project template' for sales orders using the setting shown in figure 1. </p><p><br></p><p>Let's see this in action. Create a new sales order containing at least two items that have project templates linked. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImFlNGFhZWJiLTdhMjUtNDE5Mi04Yzk5LTUyNWFjMWFhYjUyYiJ9.60hqmLkXPKL86gYzdz57LSc2JY0gdTEK8JLrMZMpe0Y" class="fr-fic fr-fil fr-dib" width="1217" style="width: 1219px; height: 483.534px;" height="484"></p><p><strong><span style="font-size: 10pt;">Fig 3. Sales order containing items linked to project templates</span></strong></p><p><br></p><p>When I create a project from the first line two project tickets will be created, a ticket using the project template linked to the item on the sales order, and a grandparent project ticket. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA3Zjc1NzU0LTE1YTYtNDA3ZS1iY2JmLTMyNGNhNDM2OTQ0MSJ9.qXCu-5KrR1_vr4UuheGL7mEvigbtZH6KWW5Dbtk2n0M" class="fr-fic fr-fil fr-dib" width="1219" style="width: 1221px; height: 362.315px;" height="362"></p><p><strong><span style="font-size: 10pt;">Fig 4. Grandparent project ticket</span></strong></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImFhZjBiMTRmLTY5ZjMtNGM2Ni1iNjhmLWJkM2FjYjdiY2FmZiJ9._h6fyE-nIFoRnfOhvltNFSSqnbHEuWfBw6LrCilfV6E" class="fr-fic fr-fil fr-dib" width="1224" style="width: 1226px; height: 482.396px;" height="482"></p><p><strong><span style="font-size: 10pt;">Fig 5. Project ticket </span></strong></p><p><br></p><p>To add the second project on the sales order to this same grandfather project use the 'Create project' action on the sales order line. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImY0ZjZjMWU0LWUyNGQtNDhkYi1hMzlhLWE5ZjViYmE2YTQxZCJ9.7iG8HseOqGTlV2on7cE7YyVxBocdIgMpE8DT06iJFTI" class="fr-fic fr-fil fr-dib" width="1216" style="width: 1218px; height: 558.004px;" height="558"></p><p><strong><span style="font-size: 10pt;">Fig 6. Create project action on SO line</span></strong></p><p><br></p><p>Using this will automatically create this project under the same grandparent project as the previous line. This project will now appear under the 'projects' tab of the grandparent project ticket </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjhlNzFhY2QxLTMxZjQtNDBkMy1hY2Q5LTJkNmU5MzhlZTYzZiJ9.a-VCFFdujW8oqf_PHQ_zDq3m-A8I08vE_Hip3pHj4bA" class="fr-fic fr-fil fr-dib" width="1213" style="width: 1215px; height: 378.978px;" height="379"></p><p><strong><span style="font-size: 10pt;">Fig 7. Projects under grandparent project</span></strong></p><p><br></p><p><strong><em>Note: Only projects (items linked to a project template) on the same sales order can be created under the same parent project ticket. If you have already created the projects and later need to add another project under this same parent project ticket you will need to add the project item to the same sales order the other projects were created from. I.e. One parent project will be created per sales order. If you create projects from a new sales order these will be created under a new parent project ticket. </em></strong></p><p><br></p><p>You will have links to both the created project ticket and grandparent project ticket against the sales order line. Earlier version will only show the project ticket link. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjcwMjFiY2VkLWM5NDAtNGVjMC04OWEyLTY0YzJkNzg1MmYwNyJ9.V4j4jyBMNpScWTBbnuSRYWbSgQSYqrdk_OQBV9-mfRc" class="fr-fic fr-fil fr-dib" width="1211" style="width: 1213px; height: 543.616px;" height="544"></p><p><strong><span style="font-size: 10pt;">Fig 8. Links to project and project grandparent tickets </span></strong></p><p><br></p><p>If you have the setting 'Automatically create projects when a project template is set at item level and the item is added to a Sales Orders' (in configuration > sales orders) enabled, projects created from sales orders will automatically have a parent template applied. Projects on the same sales order will be created under the same parent project. </p><p><br></p><p><strong><span style="font-size: 12pt;">Override the Parent Project Template per Item</span></strong></p><p>You can set different grandparent project tickets to be created based on the item. This allows you to override the project template used to create a grandparent project based on the line item a project is being created from. Useful when the grandparent ticket is specific to the type of project being created.</p><p><br></p><p>To do this head to Products > select a Product > Details tab. In the field "Parent Project Template Override" choose the template you would like a grandparent project ticket to be created with when projects are created from this item. </p><p><br></p><p>In the below example when a project is created from the "Cloud Migration" item (off a sales order) a project will be created using the template "Cloud Migration". This project will be created under another project which uses the template "Migrations". </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM3NmY2N2ExLTU4ZDAtNDc4Yy1hYTM2LWY2YTU5MmU5ZmE1NiJ9.i8GuYjt-rT-Oo4Yj7GPlogJm5OfRy76ZCbVkEQGZ2AE" class="fr-fic fr-fil fr-dib" width="1081" style="width: 1083px; height: 428.868px;" height="429"></p><p><strong><span style="font-size: 10pt;">Fig 9. Override Parent Project Template on item</span></strong></p><p><br></p><p>If two projects are created from products on the same sales order, but the products have a different "Parent Project Template Override", the projects will be created under the same grandparent project. The template used for creating the grandparent project will be taken from the template assigned to the first line item a project is created from. Any additional projects created from this sales order will be added to this existing grandparent project. To clarify, only one grandparent project will be created per sales order. </p><p><br></p><p><strong><span style="font-size: 14pt;">Billing when using Sales Order Parent Project Templates</span></strong></p><p>If you are using this functionality you will need to consider how you would like your projects to be billed. The 'project hierarchy' of the ticket type set against the grandparent template will impact how the project is billed. Whether one invoice is created for all the projects under this grandparent project. Or if invoices can be created for each project under the grandparent. Refer to our guide on <a data-fr-linked="true" href="https://usehalo.com/halopsa/guides/2404/" id="isPasted" target="_blank" rel="noopener noreferrer"><strong>project hierarchies</strong></a> for information on this. </p><p><br></p><p>If the ticket type set against your master/grandparent template has the project hierarchy 'Project' only the grandparent ticket will appear in the 'Project' area of ready for invoicing. All the 'sub-projects' and project tasks under this project will be billed on a single invoice. </p><p><br></p><p>If you would like to have a grandparent/master project ticket but have the 'sub-projects' billed separately you could set the ticket type set against the master/grandparent template to have a 'Project task' hierarchy. This will result in each project under the grandparent project appearing in the 'Project' area of ready for invoicing, allowing you to create an invoice for each project. </p><p><br></p>
