Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

"Request participants" type for custom field

原口 徹 June 19, 2024

A custom field named "Request participants" is initially equipped in JSM and its type (class, object type, whatever) is "Request participants".

I'd like to make a custom field of the type to hold latest (but not all previous) e-mail recipients, but the type seems been finalized and being not available to end users.

Is there any way to create a custom field with JSM internal object type such as "Request participants" ?

 

2 answers

1 accepted

3 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 19, 2024

Hi @原口 徹 

You should be able to create a multi-user picker custom field. And then create an automation rule that updates the field to add the users from the Request Participants field whenever it changes. 

So, create the rule based on a Field Value Changed trigger. Select the Request Participants field. 

Then add any Conditions you might need. 

Then add an action for Edit issue and select the new custom field. In the blank are for the custom field put: 

{{issue.Custom Field}}

{{issue.Request Participants}}

where the text Custom Field is the ACTUAL EXACT name of your custom field (case matters!). This will make sure it keeps adding to your list instead of overwriting it every time. 

原口 徹 June 19, 2024

Hi John san,

Thank you very much for the instruction.

Honestly I was just looking for appropriate custom field type ONLY in "standard" tab and did not notice there are "all" and "detailed" tabs.

 

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 19, 2024

Great - glad you got it sorted.

0 votes
原口 徹 June 19, 2024

Multi-user picker type was not effective when the e-mail recipients are "portal only customer" in non-Atlassian Access environment.

Label type has similar appearance to "Request Participants" type, but it is not manipulatable from Email This Issue incoming mail handler.

原口 徹 June 23, 2024

Correction:

Multi-user picker type is effective even when the e-mail recipients are not yet customers. Those are automatically created.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events