Hi,
We are using Jira Service Desk and JEMH and are trying to use emails as a primary source for our tickets. JEMH handles outgoing emails, JSD incoming. We want the CCs in the email to be request participants. They can be both existing customer emails and not existing customers in CC. From what I have read that should be the default behavior already, but right now the CC information is not saved or used at all.
The issue was not related to JEMH. It was caused by the Customer permission limiting the users to share the requests only with their organization. It needed to be "Any customer, by typing an email adress"
What version of service desk are you using? I am trying to solve this issue for my team and do not see the addressee handling field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Within your JEMH Profile -> Email -> Addressee Processing there is a field entitled: Addressee Handling
Please can you select the option 'toJSDRequestParticipants' from the list and save this change?
After this change, you should see CCs being added to the Request Participants.
However, please bear in mind that the Request Participants field can only accept users.
As this is the case, you may want to turn on Create Users within the Users section of your JEMH Profile to ensure all your customers have a user.
If you experience any problems with this functionality, please do not hesitate to open a Support Issue with The Plugin People for further assistance.
Thank you,
Elliot
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What version of service desk are you using? I am trying to solve this issue for my team and do not see the addressee handling field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This solution worked for me. It was initially configured to put the CC value in the Watchers field instead of the requests participants one, this was causing users to not have their request shared with others.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.