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

Currently my team opens up Mutiple tab's when viewing tickets, they are manually pausing the clock between tabs'.

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.

It would be preferred to have different level of administrators. Some examples would be: Administrators that can only modify Email templates Administrators that can manage Specific to organisation items and customers Administrators that are allowed to manage integrations/advanced settings/Email accounts or not

If User is accidentally set to the ability to see this - then it could lead to data breaches. If there was an option to disable this in the security config it would be helpful.

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

The documentation for HaloPSA is nearly unanimously the biggest gripe everyone has with the product, and better documentation has been promised for ages. Let the community help take some of the burden off the Halo team. I'm thinking something that uses tech like Git to version-control, PR, and allow for an easy review process. Markdown support would help us make it readable. And something with the ability to link other pages or issues. CakePHP has some of the best documentation of any project we've ever used. I think it's autogenerated by SphinxDocs reading the Github Repo This would be a HUGE help to the platform as so many of us see things in Halo and have no idea what they do. Letting customers and fans drive documentation and having it be in a controlled environment will ensure that documentation is customer-driven, accurate, and relevant.

Could you please build a Microsoft Copilot Connector that allows interaction with all the data in Halo?

Projects need stages to group tasks Tasks need to be ordered No way to bulk slide task dates if there is no date to start with. Calendar view needs to be more interactive, drag/drop tasks, etc It would be nice to see all notes on child tickets at the parent level. ...in other words, I should be able to look at the top level project and see a summary of all the notes/conversations that are happening on each task.

Sometimes a ticket can relate to multiple knowledge base articles. It woule be very beneficial to be able to link multiple KB articles to a single ticket.

I would like the option to add a user to multiple sites. we are a school society with 24 schools and have users which work on multiple schools.

Have the possibility to add multiple end-users to tickets. For example we have a manager and his employee that both need to see a certain ticket.

Allow more depth knowledge base settings, Allowing sub categories within an existing parent category Linking articles to customers, one or multiple without having to grant a customer a whole category in Halo article template types - templates for agents to select from when adding articles

It would be awesome to have integration for Keeper password manager to sync the licenses into our customers license list. This helps with the invoicing for the customer.