Incorrect rendering of STAGIL Tables field in JSM customer notifications
STAGIL Tables are not rendered correctly in JSM customer notifications. This is because third-party app fields are not supported in the built-in ${request.details} notification template provided by Jira Service Management. As a result, the table content is displayed in an incorrect format.
For more information, please refer to Atlassian's documentation on managing service project notifications: https://confluence.atlassian.com/servicemanagementserver0512/managing-service-project-notifications-1306298348.html
Is there a fix?
Unfortunately, no. This is a limitation of Jira Service Management's built-in notification system and cannot be resolved by the STAGIL Tables app.
Workaround
Instead of using the ${request.details} variable, define each field individually in your notification template. This allows you to exclude the STAGIL Tables field from the notification.
Alternative approach
As an alternative, you can configure a Jira Automation rule to send custom email notifications:
Trigger: Issue created, updated, or transitioned
Action: Send email
The email content can be customized using Jira Automation smart values to include the required issue fields.
STAGIL Tables are currently not rendered in Jira Automation emails either, as the table content is not supported by Jira's email rendering mechanism.