Skip to content

[Feature Request]: HaloPSA Integration: Add 'ticket source' #321

Description

@jjlee21

Please confirm:

  • I have searched existing feature requests (open and closed) and found no duplicates.
  • **Me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

The integration into HaloPSA works really well but when I create a report to look at the source of tickets I can see DattoRMM, SaaS Alerts, Web, Meraki Webhook, Manual, Phone, email, etc.

At present, CIPP generated tickets appear in Halo with a request source of Manual. This makes them difficult to distinguish reliably from genuinely manually created tickets for reporting on, SLA analysis and customer service reviews.

It would be great if the Halo integration would provide a configurable request source, for example, I can create new sources and so would create “CIPP”, and submit that value whenever CIPP creates a ticket.

Benefits for MSPs

Unfortunately this is more a cosmetic or nice to have improvement and wouldn't have a huge amount of benefit other than help MSPs be able to report better on where their tickets originated.

Value or Importance

Very much a nice to have, but if others using Halo, then they might like the ability to report on how many alerts CIPP raises for each customer.

PowerShell Commands (Optional)

No response

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions