which version of JIRA SD do we need to have this feature " When a unregistered user sent an email to Service Desk email channel, the email will be converted to a request and an invitation link will sent out to the sender to notify them."

I have JIRA v7.1.2, does not support for unregistered users.

Thanks Matthew. I realise this is a difficult problem but hope you guys can come up with a solution

Hi seumas.dunlop

Your issue is, as you say, a bit of a mixture of JSD-270 and JSD-2373.

The problem is that while we can detect that an issue is related by subject / headers, if someone currently is not either an agent, the reporter or a participant on the issue, then it is a security issue to add them.

We are currently investigating some possible solutions, but due to the security considerations, it might not prove to be simple or something that can be addressed in the near future. But we are aware of the issue.

Regards
Matt
JIRA Service Desk developer

This change will be a big help but I don't think it covers what is probably a bigger problem to us. Customers often email our service deskand copy their own distribution group. Service Desk can add the distribution group as a request participant but then when someone from within the distribution group replies it creates a new issue because that user isn't a request participant. What we really want is for the new email to be added to the existing issue (because it matches on the subject line) but that clearly raises some security questions.

Will this change help in that situation? Is this something you have considered or have logged somewhere else? We really need proper group support as discussed in JSD-270 but there will still be some customers who stick to email and I can see this problem staying. Not having a proper merge function makes dealing with these duplicates a real overhead.

The solution that has been implemented here, is as discussed above:

• For a public signup enabled service desk
• When processing the email for create / comment, it will check all TO / CC addresses and if they do not exist, new customers will be created and invited to the service desk, and added to the issue as Request Participants.
• In addition to this functionality through email, in the customer portal request details, if allowed by permissions, customers can also invite new users by entering their email address
• both of these are only with public signup, and the request security is configured to allow customers to manage participants

Regards
Matt

Ok great!
I added som comments in JSD-988 aswell.

Hi roger.oberg

I have created a new Suggestion at JSD-2262 for providing a way to action unprocessed mail from within Service Desk.

Please feel free to add any additional details to that ticket.

Regards
Matt

Thanks.

In regards to the rejected email flow, currently those messages can be identified in the mail audit log, and the actual messages are preserved in the database. They will be deleted after 6 months from the database.

The ability for an agent to inspect the rejected email messages and action them, sounds like a separate concern. Would you be able to create a new suggestion for that?

Matt

I agree that in the case of mis-typing an Issue ID, you shouldn´t be added automatically as participant. However that doesn´t mean that email shouldn´t be processed as a ticket, it is still an email sent to the servicedesk which the user expects to get an answer to.
So in this case, I think either a new ticket should be created, or as I suggested before, some sort of approve mechanism where the agents can verify if it is in fact a valid comment request which should be added to an existing ticket or if it should treatad as a new ticket.

Thank you for your reply.

In regards to the scenario of mis-typing an Issue ID, I think there would be security implications, if I can send random email messages with different ID's, and then have access to other peoples tickets.

I believe that a participant should only be added if the email is from an existing participant, the reporter or an agent.

In regards to the notification, I would recommend also watching JSD-988 for updates, and adding any additional details to that issue.

Regards
Matt