Issue Summary

When notifications are generated from emails containing signatures that use tables and URLs, wiki markup parsing conflicts—specifically, the pipe (|) character is used both for table formatting and within URLs, leading to incorrect rendering and errors in the notification output.

Steps to Reproduce

1. Create an email signature using a table structure and include URLs within the table cells.

1. Send an email that triggers a notification in Jira Service Management.

1. Observe the JSM customer notification , contain the full URL is displayed (sometime when safelinks.protection service is used URL can get really long), and the Customer notification template is too long and needs scrolling now.

Expected Results

Wiki markup should parse the URL and table correctly. 

Actual Results

Full are shown within the tables, causing Customer Notifications very very long requiring long horizontal scrolling. 

Workaround

If possible try a signature without using tables as a workaround