Request participants without pre-selecting user

Question

Hello everybody,

I'm trying to edit the customfield_10028 known as Request Participants automatically created by Jira, but I can't edit it without pre-selecting the value, I have tried using the edit fields advanced configuration (it had a correct value for the email):

{
"update": {
"Request participants": [
{
"add": {
"accountId": "example@email.com"
}
}
]
}
}

Is it something possible to be done? Im getting an error:

Specify a valid value for customfield_10028

Thanasis Nikolaou · Accepted Answer

Hey @Suporte JRetail

Your JSON structure is fine — the problem is the value. accountId has to be the Atlassian account ID (an opaque string like 5b10ac8d82e05b22cc7d4ef5 or 712020:xxxx-...), not an email address. Jira sees an email where it expects an ID and throws exactly that "Specify a valid value" error.

* If it's a fixed user, skip the JSON entirely: the normal Edit work item action lets you pick Request participants from the list and handles the ID for you.
* If it's dynamic, use a smart value that resolves to an ID, e.g. {{issue.comments.last.author.accountId}} — Atlassian's KB on this is here: Manage request participants with automation.
* If all you have is an email, you can look the ID up with GET /rest/api/3/user/search?query=email@example.com (in a rule that'd be a Send web request action, then read the accountId out of the response).
* Quick way to grab an ID manually: open the user's profile in Jira — the account ID is at the end of the URL.

Note: the user also has to be a valid customer/agent on that service project, so even a correct accountId can be rejected if they can't access the portal.

Gor Greyan · Accepted Answer

Hi @Suporte JRetail As @Thanasis Nikolaou mentioned, the accountId must be the Atlassian Account ID rather than the user's email address. The following JSON should work once you replace with a valid Atlassian account ID: { "update": { "Request participants": [ { "add": { "id": "" } } ] } }