Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-4103

Handle users who reply via email from a different address

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Duplicate
    • Component/s: None
    • Labels:
      None
    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

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

      Even at our fairly small company, it's surprisingly common for a user to sign up with their company email and use that to create cases in our Jira Service Desk web screens. Then at some point down the line their email address changes or they have multiple emails pointing to the same inbox.

      Then, when we add a comment and they are notified, the notification goes to their original email (which they get), but when they respond, their email client sends the response using their new email address. When this happens Jira Service Desk create a new separate case.

      It's difficult for us to track all the cases and comments and it's difficult for our customer to understand that they now have multiple Service Desk accounts and their issues are spread across the two.

      What can be done about this? My thought is in a Service Desk account, allow us to specify alternate alias emails for that user. They wouldn't be used to send anything out, but would be allowed for incoming messages so they don't create a new issue each time they comment.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              williamw William Wynn
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: