Custom Field w/ Type = 'Participants of an issue' is not updating

[Christopher Wheatley]

I created a Custom Field with a Type of 'Participants of an issue.' I need to send this field info via webhook when the Request Participants change because sending that Smart Value only provides the Jira UIDs. However, the custom field does not seem to update when I modify the Request Participants. Is there a lag? Does this field type simply provide a snapshot in time that does not change?

[Piyush Annadate _ACE Pune_ · Accepted solution]

Hi @Christopher Wheatley ,
Welcome to the Community !!
Participant field will have an auto update when reporter, assignee, etc have an update.

To fetch the details - you can just use 
{{issue.customfield_<id of field>.displayName}}
example: 

{{issue.customfield_10333.displayName}}

 Note: You cannot fetch email address, you have to fetch email address using account ID and user rest api. 

[Christopher Wheatley]

Hi @Piyush Annadate _ACE Pune_

This is certainly helpful to know that displayName is available for the Request Participants field and unforntunate that emailAddress is not -- I need both.  Thanks for your reply!

[Christopher Wheatley]

@Piyush Annadate _ACE Pune_ , I just tried a quick test out of curiosity to try get the email address from Request Participants and it worked!  In other words, email address IS available via Smart Value in the Request Participants field. It doesn't necessarily answer the issue I was asking in this post (why isn't the other field updating with the native functionality) but that is moot at this point as this solves the problem that had me create the custom field in the first place!

The JSON payload I'm sending via web request is:

{
"issueKey": "{{issue.key}}",
"participants":[
{{#issue.customfield_10035}}{
"displayName": "{{displayName}}",
"email": "{{emailAddress}}"}{{^last}},{{/last}}
{{/issue.customfield_10035}}
]
}

[Piyush Annadate _ACE Pune_]

Oh ,yes I can see the Email address in the json. 

[Akhand Pratap Singh]

Hello @Christopher Wheatley ,

Good day, Welcome to Atlassian Community

1.  Request Participants change because sending that Smart Value only provides the Jira UIDs.

--> Can you confirm the smart value you are using

2. The custom field does not seem to update when I modify the Request Participants.

--> Are you using any Automation Rule to sync both the fields? If not, I suggest creating an Automation Rule to sync Request Participants with your Custom field

 Please let me know, if you need help in establishing the rule.

[Christopher Wheatley]

Hello @Akhand Pratap Singh

1. The challenge here is that the custom field I created SHOULD be syncing the Participants due to it's type -- but, it's not.  I have a ticket in with Atlassian support as well.  The JSON delivery of the via Smart Value is working perfectly, it's just inaccurate:

{
"issueKey": "{{issue.key}}",
"participants":[
{{#issue.customfield_10438}}{
"displayName": "{{displayName}}",
"email": "{{emailAddress}}"}{{^last}},{{/last}}
{{/issue.customfield_10438}}
]
}

2.  I am not using an Automation Rule at this point to sync the fields, just the native JSM functionality.