HaloITSM Guides

Documentation to assist with the setup and configuration of the HaloITSM platform

Guides > Milestones

Milestones

In this lesson we will cover:

- Milestones Tab

- Options When Adding Milestones

- Dependencies

- Locked Tasks and Filtering by Milestone

- Configuring a Column Profile for Milestones

- Updating Milestones via Project Management General Settings

- Link the Child to a Milestone When Creating a Child Ticket from a Project

Associated Admin Guides:

Associated Guides:

Ticket/ Client Areas

HaloPSA allows for Milestones to be tracked against Projects and provides the ability to associate Project Tasks with a given Milestone.

Milestones Tab

Milestone functionality is enabled against Ticket types for which you want this feature to be used. This option will be present within the Settings tab for Ticket Types or the Details tab (if you're on the stable version 2.132.73) Configuration > Tickets > Tickets Types.

Fig 1. Enable Milestones Button on the Ticket Type

Once you have enabled this option, you will find a Milestones tab against Tickets of that type.

Fig 2. Milestones tab against Ticket

Options When Adding Milestones

In here, you can add new Milestones, including:

Providing a sensible name
Adding a sequence for sorting the list of Milestones
Adding start/end dates for a given Milestone
Allocating Tasks/child Tickets to said Milestone (Multiple tasks can be added to the same milestone)
Adding dependencies between Milestones

Fig 2. Options when adding Milestones

Dependencies

Dependencies can be set on the Milestones, granted that they are not the first milestone on the project. The tasks in milestone 2 will be locked until milestone 1 is marked as completed, adding this dependency is shown below:

Fig 3. Milestone 2 is dependant on Milestone 1 Being Completed

Locked Tasks and Filtering by Milestone

Now when viewing tasks with the Milestone 2 filter set, there won't be any tasks shown by default, because they are locked. To show the tasks that are locked, we can toggle the view as show in (Fig 4).

Fig 4. Locked Milestones can have their tasks shown by clicking on "Show/ Hide Tickets Against Locked Milestones"

You will also find that, upon enabling Milestone functionality against a Ticket type, you have the option to filter the list of Tasks based on their current Milestone, for the example shown below, filtering for "Milestone 1" will mean only the child ticket 2163 would show, as 2164 doesn't exist in Milestone 1.

Fig 5. Filtering the list of Project Tasks based on their current Milestone

The 'Dependencies' dropdown (Fig 3) allows you to specify that one Milestone is dependent on another. When a milestone is dependent on another, the Tasks associated with that Milestone will be locked (Fig 4).

For example, if I associate the 'Child Ticket 2164' task to 'Milestone 2' & make Milestone 2 dependent on Milestone 1. Then the Child Ticket 2164 would be locked until Milestone 1 has been marked as Complete.

Fig 6. Locked Task

Milestones are marked as being complete via selecting the 'Complete' option against the Milestone itself (Fig 2), or when all Tasks assigned to a Milestone are closed.

Configuring a Column Profile for Milestones

To best utilize Milestones in Halo you would want to use the table view for Column Profiles as this can group tickets by Milestones.

Fig 7. Table view for Milestones on Ticket List

To configure this column profile navigate to Tickets > Views > Configure Column Profiles > New > Add a Column Profile Name, Use, and Board Visibility.

Fig 8. The Column Profile Page for Project Views

To Set this just for the Projects Area (Areas are configured in Configuration > Tickets > Ticket Areas), we can set to the use "Projects" on the Column Profile. Checkout the guide on Ticket/ Client Areas, listed at the top of this article for more info.

Fig 9. Setting the use to Projects

The next step would be to add the column you would like to see when using this Column Profile. These are the recommended columns to add:

Fig 10. Grouping by the Milestones Column on the Ticket List and Setting The Due Date as the Primary Sort

Note: You would likely want to make the Due Date (Target Date) the Primary Sort (Ascending) and Group by the Milestone Field to get the best-looking results.

To configure this filter profile you would need to navigate to Configuration > Tickets > Ticket Types > Select 'Project Task' > Set the Column Profile for Child Tickets to the Column Profile you created in the last step, the column profile for child tickets exists under the settings tab for versions over 2.132.73:

Fig 11. Setting the Column Profile on Child Tickets (Project Tasks)

Updating Milestones via Project Management General Settings

If this below setting is unchecked and you update the date of a milestone, only other milestones that are dependant on the milestone that you are updating will be updated. When checked, updating the date of a milestone, will update the date of all milestones, regardless of whether they are dependant on each other. This will stop milestones clashing dates with one another. It is recommended that this setting is on.

Fig 12. Updating Dates for a Milestone Updates All Milestones

Fig 13. When Updating Dates for Tasks Update the Milestone Dates

When selected, the start/ end date of a milestone will be updated, such that the start date of the milestone will be the earliest start date of any task in that milestone, and the end date will be the date of the last task in that milestone. This automates the setting of milestone dates on a project.

Link the Child to a Milestone When Creating a Child Ticket from a Project

First you need to enable milestones on the project task ticket type, this can be done from the settings tab of the ticket type.