Feature Ideas

I know this is petty, but this is the dumbest UX in the universe. Please move these notifications somewhere else.

For us, being new to HaloPSA, one of the things that frustrated us the most was the lack of good documentation when it comes to integrating with the system. It would be nice if this could be improved a ton, as we now have to try and reverse engineer how the system is set up to do.

When “Allow the choice of ticket on the quick time screen to log against” is enabled, the “Log as Work Time” option disappears from the timer. We need both options available together so agents can: Log internal work time, such as meetings, training and administration. Log time against an existing customer or project ticket directly in there timesheets.

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

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.

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.

We would like to send notifications from Halo to Teams chat for agents (e.g. mentions etc.) but based on the Guides and our tests Webhooks only allow sending notifications to channels, not chat TeamsBot does not have the option to receive notifications

Mass Edit is deployed in a few modules only and does not allow to edit all field (including values from connected module). This functionality is necessary to all modules, especially to Tickets, Customers/Sites/Users, Assets, Knowledge Base, Agreements, Suppliers, Products, Offers, Orders, Invoices. Batch edit by CSV is not sufficient.

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

When editing an appointment that exists, the agent cannot be changed. Currently, you have to delete the appointment and create a new one for the new technician. This is inconvenient and sends out cancellations and new appointments.

customers have multiple relationships with us under 'settings\Assigning and Account Manager'. currently only one of those is filterable using 'Accounts I Manage' I'd like filter options for all of those options.

Enhance the existing Halo MCP ticket tools so they can correctly create and manage tickets that belong to projects. Currently, an AI agent can create a project and subsequently use Create Ticket to create project tasks, but the tool does not expose the required Parent Project / Parent Ticket relationship. This means the AI can successfully create both records while failing to establish the project hierarchy between them. The MCP schemas for relevant ticket tools should expose fields such as: Parent Ticket ID Project ID Parent / child relationship Project task type Milestone, where applicable Ideally, Halo MCP should understand when a ticket is being created as a project task and ensure the relationship with its parent project is represented as an explicit, strongly typed input. This would improve both project automation and general hierarchical ticket scenarios while allowing AI clients to use Halo’s existing ticket tools more reliably.

Halo’s MCP integration works well for many ticket-related scenarios, but Project Management currently has limited tool coverage. We would like to use external AI agents such as Microsoft Copilot Studio to create, investigate and manage HaloPSA projects using structured MCP tools. A practical example is project creation. An AI agent can create the project ticket, but when it subsequently creates project tasks using the standard Create Ticket tool, it cannot provide the parent project relationship. The tasks are therefore created without being linked correctly to the project. It would be valuable to introduce dedicated Project Management MCP tools such as: Search Projects Get Project Create Project Update Project Get Project Overview / Health Get Project Tasks Create Project Task, including Parent Project ID Update Project Task Get/Create/Update Milestones Assign project tasks Get project progress Get project budget and time usage Get project risks and health Where general ticket tools are used for project entities, the MCP input schemas should expose project-specific relationships such as Parent ID / Project ID. This would allow an AI agent to create a project and then continue building the complete project structure correctly, rather than treating projects and project tasks as unrelated tickets. More comprehensive Project Management MCP support would make Halo’s MCP endpoint much more useful for project assistants, project managers and AI-driven workflow automation.

Expand the built-in Halo MCP tool library so AI agents can work with more HaloPSA modules without requiring custom integrations or report-based workarounds. The current MCP system tools provide useful functionality for areas such as tickets, knowledge, users, assets and service catalogue. It would be valuable to extend the same structured tool approach to additional Halo modules. Suggested areas include: Projects: Search ProjectsGet ProjectGet Project TasksGet Project MilestonesGet Project ProgressGet Project Budget / Time Usage Customers: Get Customer OverviewGet Customer ServicesGet Customer AssetsGet Customer Open Tickets Contracts, recurring services and billing: Search ContractsGet ContractGet Recurring ItemsGet Billing / Invoice Basis Information The goal would be to make the MCP endpoint a comprehensive AI interface to Halo, using clearly defined and strongly typed tools rather than requiring AI clients to understand the full Halo REST API.

When a user-defined MCP tool is configured with "Get Report Data", Halo should expose the report's filterable columns as optional MCP tool input parameters. Today, report-based custom tools can be exposed through MCP but the generated inputSchema contains no properties, even when the underlying Halo report has filterable columns. For example, a Project Overview report may contain a filterable "Ticket ID" field. An MCP tool such as CF_Project_Overview should be able to expose an input such as project_id / ticket_id, allowing an AI agent to request data for one specific project. Ideally, Halo could allow administrators to select which report filters should be exposed to MCP and provide: Parameter nameDescriptionData typeRequired/optionalMapping to the corresponding report filter This would make Get Report Data significantly more useful for AI agents and avoid returning large unfiltered report datasets.