Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-14812

Request created default rule email template is showing correct email template in preview but shows incorrect format in the email notification when request created from customer portal

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 5.4.11
    • 5.4.8
    • Email - Outgoing
    • None

      Issue Summary

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. customise request created email template for any ITSM project. Add below customisation.
        Project Settings --> customer notification --> default rule --> edit issue created.
      * *Issue summary:* ${issue.summary}
      * *Issue key:* [${issue.key}|${request.url}]
      * *Issue reporter:* ${issue.reporter.name}
      ${request.details}
      


       

      Expected Results

      In the preview section the formatting and bold setting is correct and same is the case when we send a test email. Please find the image given below.

      Actual Results

      When request is created from the customer portal, email notification that is sent to the customer for issue creation has incorrect format. Please find the given snapshot. Please check this bug as to why correct format is shown in preview but incorrect format is sent in the notifcation.

      Workaround

      No workaround availaible.
      Currently there is no known workaround for this behavior. A workaround will be added here when available

          Form Name

            [JSDSERVER-14812] Request created default rule email template is showing correct email template in preview but shows incorrect format in the email notification when request created from customer portal

            There are no comments yet on this issue.

              bornatowski Bartosz Ornatowski
              1d12437dc9e8 Mehboob Salim Shaikh
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: