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

Do not add customer with same email address as the one used to fetch emails as a request participant.

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Low Engagement
    • None
    • Customer Portal
    • None
    • 1
    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Problem

      If there is an existing user with the same email address as the one set up as the email channel, the user will be added as the Request Participant for every request created from the email.
      This is as outlined in Adding request participants.

      If you create or respond to a request via email, add a request participant's email address in the TO or CC fields. The participant receives an email notifying them that they have been added.

      Suggestion

      Do not add the user who has the same email address as the one set up as the email channel as a Request Participant automatically

      Workaround

      Disable the user in JIRA if the user account is not in use except for the email channel

      Original description

      This is similar to JSD-2298 but the scenario is creating a comment by replying to a notification email.

      Scenario:
      1. Reporter creates an issue via email. There is a customer user with the same email address as the one used by JSD to fetch emails.
      2. Reporter receives a notification email from JSD.
      3. Reporter replies to the notification email. This reply creates a comment.
      4. The customer user with the same email address as the one used to fetch emails is added as a Request Participant.

      Expected result: at step 4, do not add this user as a request participant. It is unnecessary. This user is no longer added as a request participant when the issue is first created via email, as per the issue noted above. I think the same handling should be applied when responding to email notifications.

      I did raise this as a support issue, and was told the functionality is working as intended but that I could raise a feature request.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              a676f12b3159 Cathy Rivard
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync