Summary

The notification template formatting is inconsistent. JIRA Cloud sends notification with header at the top while the notification triggered from REST API end point (/rest/api/3/issue/<ISSUE_KEY>/notify) has header at the bottom.

Replication Steps

1. Trigger a notification from JIRA via normal means by performing an issue notification.
2. Check out the notification from JIRA. The header of the notification will be at the top.
   
3. Now trigger another notification from JIRA via '/rest/api/3/issue/<ISSUE_KEY>/notify'.

   curl -D- --request POST \
     --url 'https://kingdom-hearts.atlassian.net/rest/api/3/issue/DI-28/notify' \
     --user 'vchin@atlassian.com:<API_TOKEN>' \
     --header 'Accept: application/json' \
     --header 'Content-Type: application/json' \
     --data '{
     "htmlBody": "The <strong>latest</strong> test results for this ticket are now available.",
     "subject": "Latest test results",
     "textBody": "The latest test results for this ticket are now available.",
     "to": {
       "voters": true,
       "watchers": true,
       "groups": [
         {
           "name": "jira-software-users"
         }
       ],
       "reporter": false,
       "assignee": false,
       "users": [
         {
           "accountId": "557057:dd697c0d-6cc7-429e-b8a1-4ccab4c19347",
           "active": true
         }
       ]
     },
     "restrict": {
       "permissions": [
         {
           "key": "BROWSE"
         }
       ]
     }
   }'
   

4. You will notice that the header is at the bottom for this new notification.
   

Expected Result

Both notification from JIRA and JIRA REST end point should have header at the top of the notification.

Current Result

JIRA notification has header at the top while JIRA REST end point notification has header at the bottom.

Workaround

None so far.