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

To be able to customise the columns shows under the self service portal asset list At the moment, you can customise the tickets and projects, but not the asset list. quick win

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

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.

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.

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

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?

It would be helpful to have an integration with Docusign so that we can create a quote within HaloPSA and have it send out through Docusign when we go to send the quote. Then, it would need to sync back the status of the signature, as well as the signed document once all parties sign the document.

Looking at a use case where items on a PO were received but the information was input wrong so they essentially need to be undone. I.e., cost/price, quantity, etc. It would be nice to be able to un-receive and un-consign to be able to edit the PO line item and re-receive the stock.

When we add our ninja agent before the stock is fully received (or if there's a mistake in the serial number), we end up with two assets. This most often occurs when we install ninja/rmm on an endpoint which creates an asset, then we receive/deliver the asset from a PO afterwards, which also creates an asset. I'd like to be able to retain the purchase information from the PO'd asset and everything else from the RMM synced asset. Or, if there's ever a field merge in question, just ask which of the two should "win". I currently do this manually via the API that copies data from the RMM synced asset into the purchased asset, then deletes the RMM synced asset.

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.

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

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.