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

Anyone ever see TopLeft's implementation for ConnectWise or AutoTask? Enough said. Kanban boards is one of the reasons we came to HaloPSA in the first place. But it is pretty much useless without being able to change the order of the tickets in a column? I mean you can drag and drop the ticket in the kanban board / column, but it doesn't stay there?

Currently, we have to add one by one of the items to Project. It would be great if we could choose multiple items or add them all by clicking one button to a project. because some orders may have 100 items in one order

Allow customers to approve their quotes in the portal, instead of only approval or reject via email link. This feedback is a key theme direct from many of our customers.

Ticket Custom Field Groups is an incredibly helpful feature, please could we have the same ability to combine asset fields into "groups" to make building out an a large asset management structure more efficient. We could then build Asset Field Groups in advance, and then add the fields groups to each asset type instead of having to build the fields lists from scratch for each Asset.

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

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.

Selecting multiple tickets currently, clicking edit provides a list of single-functions. There should be an option to Edit bulk where multiple items can be changed from one screen like ticket type, category, priority, status, including an option to add a Public or private note

It would be nice to have a full visual report builder in composite reports that allowed you to visually design it without needing to know HTML. It would also be great if there was some investment into an online repository of report styles with Halo creating a standard out-of-the-box one that is simple, elegant and visually appealing to the client's eyes. Reports are something that is hugely important, however, the lack of design for non-technical people makes Halo reporting not the ideal choice. Most of the time, we would like to add commentary to our reports to explain why certain result are the way they are. The ability to export to word would also be a great feature, as it would allow us to export the data and then we could add the required commentary.

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

Have the ablility to create a recurring invoice template which can have all line items added but only bill/show on the invoice where they is a quantity. Also in the template have the Quantity being able to be set by Assets / Licecnce / User / Subscription The Idea behind this if we add a new product to the customer "office365 E3" Licence via Pax8 we dont need to go and add the item to the customer.

I would like to change the favicon that is shown on the customer portal – right now it’s the red haloPSA favicon which doesn’t match our color scheme at all. Replacing it with our own custom icon preferred, alternatively the ability to set a HEX color code for the existing icon would be a 2nd option Also when going to our portal the loading circle is blue at first, and then changes to our green, is there any way to fix that? Right now the favicon is red, the initial loading circle is blue, and then finally things change to green, which is a pretty bad mis-match of colors Additionally, it would be great to have the option to repeat a background image vertically, right now we had to make a fairly large image in height to have it work on every possible screen/mobile device, but the caveat is that the background image takes a second or two to load in. If we could just have it repeating on the Y axis that would solve the problem, but I was told that it's not possible, even by custom CSS at this time.

Every view is useful and that's why you added all these views. Unpaid invoices, sites & users for a client, etc. Why can't I export them? We all agree they are very useful and concise collections of business data, but we're limited to seeing 50 rows and we can't export it. It's useful! You know it's useful! You put it in the application! Let me have the data! Thanks

It would be good if the "Holiday" event types synced to Exchange calendars with Microsoft 365. As it stands the "Appointment" event type synchronises to calendars, but holidays do not.

wouldn´t it be great, to have the same login for the https://support.haloservicedesk.com/portal/ and https://ideas.halopsa.com/ and to be able to create an Idea from a ticket, so that dev could not only read the idea, but also the support case which lead to the feature request?