mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #4243] [Feature Request]: tables not working in HaloPSA tickets #1920
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1920
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @isgq-github01 on GitHub (Jun 10, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4243
Please confirm:
Problem Statement
We raised this with the helpdesk but they advised it was more of a feature request. Alerts that contain tables are not parsed in HaloPSA correctly, so you end up with alert text that looks like this:
Benefits for MSPs
Benefits MSPs in simpler legibility of alerts and easier to understand the information that is presented.
Value or Importance
I believe this is critical as it's making the alert rather unusable, unfortunately.
PowerShell Commands (Optional)
No response
@KelvinTegelaar commented on GitHub (Jun 10, 2025):
Are you using email to your PSA instead of the PSA option, this is how it looks in Halo when you use the PSA option:
This looks more to be a configuration issue in HaloPSA.
@isgq-github01 commented on GitHub (Jun 12, 2025):
@KelvinTegelaar I believe it might just be the app approval alerts, at least? This alert looks fine for instance.
@isgq-github01 commented on GitHub (Jun 13, 2025):
Also forgot to answer the question that yes we are using the direct to PSA option - not email to PSA
@KelvinTegelaar commented on GitHub (Jun 14, 2025):
fixed in dev
@isgq-github01 commented on GitHub (Jun 16, 2025):
@KelvinTegelaar have found the "expiring app secrets" alert has the same problem, just in case your fix was only applied to the app consent request alerts. Tried searching the dev branch but couldn't find where your changes were :)
@isgq-github01 commented on GitHub (Jun 23, 2025):
Unfortunately this issue still seems to be present for both app consent requests and expiring app secrets. Tried a fresh app consent request and it's coming through to Halo as plain text. Definitely on 8.1.0. Let me know if you need any more info? @KelvinTegelaar @Zacgoose