Feature Ideas

In the settings screen it is currently only possible to search settings for a /section/ (i.e. 'integrator'). Given the vast complexity of the HALO product and the fact that a great number of settings that might be considered related are not actually grouped together, the organic way in which settings are added, and the typically very lacking documentation, please make it possible to search the actual setting 'labels' and descriptions. i.e. I should be able to search for "new user" and at least be able to click through to the exact location of, if not see the current state of, all the setting options with the string "new user" in their title or in-line help text

A full functioning mobile app that doesn't require you to go to the browser version on your phone for 90% of your needs.

We heavily use to-do's as a way of creating checklists on common steps. However, a lot of our clients require unique custom checklists. We use IT Glue currently for this and it allows not only a to-do, but it allows that to-do to be expanded detailed steps (written in HTML). What I would like to see is the following To-dos have their own tab in tickets and not just a sidebar. To-do's can be expanded to show links or steps (See screenshot of Glue) To-dos once completed hide from the list To-do's that can be associated with a client site and be templated To-Do templates can be grouped

Having the ability to pull the catalog, availability, and pricing drastically decreases the time spent on drafting quotes/proposals. Not only does it allow you to quote faster, but it will help when following up on quotes to see if the product has changed in availability or price. Finally, it helps to reduce human errors within the quote/proposal since it is pulling directly from the distributor. Seeing Ingram Micro, D&H, and Tech Data would be a game changer for this PSA.

The HTML editor chosen for use across HaloPSA lacks and has a terrible time copying data from Word Docs. I would love to see an improved or replace HTML editor across HaloPSA, especially in Knowledge Base Articles.

we use the Unifi Hardware stack for most of our networking as the controller for this is free and doesnt require a subscription. this controller uses standard Rest api to collect information. (www.ui.com) I have currently created a powershell based integration that collects all sites and hardware from the unifi controller and updates them via api in Halo. However, due to api throtteling this process is quite prone to error. It would be realy nice to have this as a proper integration. This api is Documented here: https://ubntwiki.com/products/software/unifi-controller/api

It would be really useful to be able to write an email in Outlook and pick the correct ticket number from a list or search, add time in and then send to Halo through the normal copy in the mail delivery email address as usual. The reason this works much better is: a) People don't ignore direct emails from people in the same way as they ignore automated emails from a PSA system b) The formatting used is much better and doesnt break as with the current output from Halo(and you can paste in other items without the formatting getting screwed too) You could use the same mechanism to book in ticket updates, appointments from tickets and tasks/notes from tickets to work from.

One of the biggest complaints I have received about Halo's Knowledge Base is navigating between articles and FAQ groups. It would be extremely helpful to have both a forward/back button within the KB. And to have the FAQ group path for each article, with the ability to select any FAQ group in that path to jump to.

To better manage Holiday/Leave requests, it would be a good idea if there was an email triggered to the approver to notify that there was a Leave request pending. Currently the only option to see what needs to be approved is in the approvals tab. However not all managers have HALO open all day but more than likely have access to emails to be notified of the request and then can action accordingly. It is just a small adjustment but would make a big difference to managing the approval requests.

The NinjaRMM integration isn't pulling all devices from Ninja regardless of their offline status. What this means is that after a few days, a device is marked as inactive in Halo. This is problematic because we have clients who will have devices offline for a couple of weeks and they are becoming inactive in Halo. We use device counts for invoicing so we are not getting a proper match between devices in Ninja and devices in Halo. At a minimum, if a device is in Ninja (even if it's offline) it should be retrieved by the Halo integration. However, an option to choose this behavior or customize the number of days for a device to be offline would be an even more dynamic solution.

currently you can't, but you can on a single-select please add it so that at the very least we can use 'contains' or 'doesn't contain'

currently it doesn't work on project tickets...... project consultants need access to KB articles too, despite what they might think ;-)

It would be valuable if we could support ToDo list per ticket stages. At present, I have been able to implement new ToDo list via new template however I have to trick the system with the Closed status in order to prevent the ticket from moving to the next stage if items haven't been completed.

Currently you can only have one Closed Ticket Status. This doesn't really suit how we work as we sometimes Cancel tickets which are raised in error, where as any tickets which are brought to a successful conclusion are 'Resolved'. At the moment when we Cancel tickets, they still show in the User Portal under Open Tickets as the Status itself is classed as an Open status, not closed. We're using the only Closed status we have available as Resolved.

Would like the ability to map asset types in Ninja to asset types in Halo. For example, in Halo all our current assets and items are filtered where asset type is called workstation or server. However, Ninja brings servers across as Windows_Server. This means we have to go and update all our reports as well as all our items where the quanity is mapped to device name is server.