+1 ... this is really needed. Or there may be another workaround? We have an automation rule that sends an email to people based on email addresses in the description field. we ould like to automatically add those email addresses as request participants even if they are not customers/portal users or licensed  users on the Jira instance. Please advise? Thank you

A workaround:

1. Go to project settings -> Automation
2. Create a rule: 
   When: Issue created
   Conditions: add conditions if you need
   Then: Edit issue fields -> adjust field Request participants (Set value)
3. Publish

If you want the users to add participants inside the form you can try the following. I haven't tried it myself but I think it should work:
First create a custom field of type User Selection (multiple) and add it to your form - that allows the users to select other users just like when they add participants. In step 2 above, adjust the field Request participants and instead of Set value you choose "Copy from.." and set that you want to Copy from the Custom field you created.

We need this feature as well.

This is a needed feature. 

Request crated 5yrs ago, and still not implemented. 
This request will end up just like the "custom domain names" feature request. ca 10yrs, thousands of votes yet no solution to be seen.

Only Microsoft and Atlassian gets away with this kind of bad support and bad service!

I really need to be able to auto-add participants to my Service Desk tickets.

All my participants are inside my business - no one is external.

And given I cannot batch 'Add Participants', this is another time-consuming job I have to do by hand...

Apparently the post function feature to allow automated adding of users to the Request Participants has been removed because of GDPR. As such, our workflow will be affected by this. Given that we are sending our emails directly from the portal, we have our own compliance to ensure all INCOMING and OUTGOING emails are archived. Therefore, we were using the POST FUNCTION to auto include the email which will in turn be archived by our onpremise solution. NOW we are stuck with no solution in sight. We cannot auto include participants and we cannot have Jira sending our emails from our system. What can we do now? Pay a high price for a onpremise Jira solution? 

Are any of these requests ever completed? 

Hi Dirk,

Exactly, i use it with organization also. In the JMWE plugin, the post-function can be conditionnally executed and so i use the condition to change the request participants based on their organization. Here is the condition i use for instance (it is specific to the plugin) :

{% for organization in issue.fields.Organizations %}
{{ "true" if organization | field("name") == "MyCustomer Organization" }}
{% endfor %}

With this i assign the request participants based on the name of their organization.

HTH,

Ludo

Hi Ludo,

thanks for pointing out the option of using a post-function. But in our scenario there are different users that need to be added, depending on the user that reports the issue.

This request came up in a Service Desk project and now you can have organizations there. That helps a lot actually: We were able to create organizations with those people we would have added as participant before.

But of course this feature is only available for Service Desk...

BR

Dir