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

When Email Requests are turned on, gray lines appear at the top of the JSM Customer Notification template for that JSM project.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 5.4.30, 5.12.13, 10.3.0, 10.4.0
    • Documentation & IX

      Issue Summary

      When Email Requests are turned on, gray lines appear at the top of the JSM Customer Notification template for that JSM project.

      Steps to Reproduce

      1. In a JSM project, navigate to Project settings > Customer Notifications and click on Email templates.
      2. Turn on Email requests following the documentation for Receiving requests by email & Managing the email channel
      3. Navigate back to Project settings > Customer Notifications then click on Email templates.
        The content of the Email requests is updated with an additional "Reply above this line" along with a line on the top of the template.
        <div class="jsm-reply-marker-hint">
            Reply above this line.
        </div>
        

      4. Remove or relocate the jsm-reply-marker-hint tag in the notification template.

      Expected Results

      A better UI description of the grey line needs to be included because the grey lines are part of the Reply-to mechanism built in with Customer Notifications when Email Requests are turned on.

      • UI description that the grey line cannot be removed in the Customer Notification template.
      • Option to either tie the grey line to the jsm-reply-marker-hint tag (moving the tag would also move the line), or remove the jsm-reply-marker-hint to avoid confusion.

      Actual Results

      There is no description of the grey line. Attempts to move or remove it do not work, and it always renders in the notification email regardless of what is put in the notification template.

      Workaround

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

              Unassigned Unassigned
              dgedda@atlassian.com Devisree Gedda
              Votes:
              4 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: