[hfe_template id='1680'] Project Management Configuration | HALO

Project Management Configuration

In this lesson we will cover:

– Overview in Project Management Configuration in Halo

– Points to consider when setting up projects in Halo


Associated Administrator Guide:

For an initial ‘baseline’ set up of HaloPSA, very little work will be needed to manage Projects. In fact, it’s not uncommon for clients to simply use Service Requests to track smaller Projects as part of a Phase 1 implementation of HaloPSA.

For phase 1, you can head to Configuration>Project Management & disable the ‘Budgets’ module (this will likely be enabled for phase 2).

Overview

Here’s a quick overview of Project Management in HaloPSA & some potential points to consider when it comes to an initial implementation:

Project Management in HaloPSA leverages Parent-Child Ticket relationships. You have:

  • The (parent) Project Ticket, used to provide insight into the Project schedule & gives a high-level overview of the current progress of the Project as a whole
  • The (child) Task Ticket(s), used to detail the day-to-day activities which need to be completed in order for the Project as a whole to be a success.
  • The Project Ticket is assigned to the Project Manager – they will then schedule each individual child Task & assign them to respective technicians. 
  • The Tasks are assigned to Project Consultants – within these Tasks, Project Consultants will add their notes & time, just like one would with support Tickets. 
  • The above is more applicable for larger Projects, with many components needing to be completed by different techs. For smaller Projects, there is nothing wrong with simply creating a Project Ticket with no child Tasks & adding all of your time/notes to the Project Ticket.

Points to Consider

To start with, there’s two primary points to consider: 1) where do I want my Projects displayed? And 2) Who can Projects be assigned to?

Point 1 will be one of two answers, either:

  • You’ll want Projects displayed with your Support Tickets (so techs have fewer places to look to see what work they need to do) or,
  • You’ll want Projects displayed in a Separate area (to better distinguish the different types of work you do on a daily basis)

By default, Projects are displayed in their own separate area. So you wont need to make any changes if you are looking to keep it this way. If you wanted Projects to be displayed in the same area as your Support Tickets, head to Configuration>Tickets & disable the ‘Areas’ module. This will then merge the ‘Service Desk’ & ‘Projects’ areas into a single ‘Tickets’ area, where all of your Support Tickets & Projects will be displayed.

For point 2 (who can Projects be assigned to), all you would need to do is make sure the relevant technicians are members of the ‘Project Management’ & ‘Project Consultants’ teams, for assignment of parent Projects & component Tasks, respectively.

For more detailed information on how to set up your projects in Halo please see our Project Management course. 

[hfe_template id='2416']