[GH-ISSUE #4243] [Feature Request]: tables not working in HaloPSA tickets #1920

Closed
opened 2026-03-02 13:48:11 +03:00 by kerem · 6 comments
Owner

Originally created by @isgq-github01 on GitHub (Jun 10, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4243

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

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:

Image

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

Originally created by @isgq-github01 on GitHub (Jun 10, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4243 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### 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: ![Image](https://github.com/user-attachments/assets/4f097987-7839-478b-a296-6147ce6e96b2) ### 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_
Author
Owner

@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:

Image

This looks more to be a configuration issue in HaloPSA.

<!-- gh-comment-id:2958186130 --> @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: ![Image](https://github.com/user-attachments/assets/abba207a-dbf6-4ccc-9fc1-e4b3398faa8c) This looks more to be a configuration issue in HaloPSA.
Author
Owner

@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.

Image

<!-- gh-comment-id:2965235250 --> @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. ![Image](https://github.com/user-attachments/assets/48462c4d-e3e4-447c-a537-b8666a037c51)
Author
Owner

@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

<!-- gh-comment-id:2969054945 --> @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
Author
Owner

@KelvinTegelaar commented on GitHub (Jun 14, 2025):

fixed in dev

<!-- gh-comment-id:2972990135 --> @KelvinTegelaar commented on GitHub (Jun 14, 2025): fixed in dev
Author
Owner

@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 :)

<!-- gh-comment-id:2974879155 --> @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 :)
Author
Owner

@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

<!-- gh-comment-id:2994630071 --> @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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#1920
No description provided.