The reply-to is not respecting the request-type while sending notifications

XMLWordPrintable

    • 2
    • Severity 3 - Minor
    • 21

      Issue Summary

      When there are multiple email channels set for a single project, the 'reply-to' in the notification email seems to set the first email channel irrespective of the 'request type' of the issue.

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Create a JSM project
      2. Configure two/more email requests from Project settings >> Email requests as shown in the screenshot below -
      3. Now, create an issue from the customer portal for the first request type.
      4. Wait for the 'Issue created' notification. The reply-to in the email is the first email address configured on the Email requests.
      5. Now, try to create another issue from the Customer portal with the second request type.
      6. Wait for the 'Issue created' notification.

      Expected Results

      The reply-to has the correct email address from the Email requests set in the reply-to header.

      Actual Results

      Which over 'Request type' is selected during the issue creation. The notification email has the first email address configured in the Project settings >> Email requests filled in the reply-to field.

      The replies to the notifications will still get added to the correct ticket since the issue-key is present in the email.

      Workaround

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

              Assignee:
              Benjamin Suess
              Reporter:
              Sandhya Thottamkara
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: