Use value of 'request participants' in a comment

[David Pontarelli]

Hello!

Using Automation for Jira, I'm trying to take the name of the person in the "request participants" field and use it in the comments. I was trying to use Smart Values to do this, but despite some of what I've found online, it doesn't appear that smart values work for the "request participants" field. I've tried referencing the value other ways with no luck some of what I tried is below.

[~accountId:{{customfield_10201.accountId}}]

{{issue.customfield_10201.displayName}}

{{customfield_10201.displayName}}

{{issue.Request Participants.key}}

I'm not very experience in this type of thing. Is this something that's possible or am I spinning my wheels?

Thanks in advance!

[Hyrum Steffensen _Appfire_]

Hello David,

I had good luck with:

{{issue.Request Participants.displayName}}

Here is a screenshot of my setup:

Regards,

Hyrum 

[Hyrum Steffensen _Appfire_]

David,

I also tried this, and it also works:

{{issue.customfield_10702.displayName}}

It seems you have already tried this. I am not sure why it is not working for you. Try printing the value to the audit log and post what you see there.

Regards,

Hyrum

[David Pontarelli]

I added the 'Log Action" step as you have above. it just shows that the rule ran successfully, but in the comment shown in the ticket, it's blank. I attached some photos below.

[David Pontarelli]

forgot the one of how it shows in the comment

[David Pontarelli]

I got it! Thanks for pointing out 'print to audit log' that helped hone in on the issue for sure. I setup a new rule to do that after it didn't show anything much when adding it to my initial rule and saw it populate correctly. 

I think the issue is something to do with the fact that I set the "Requested Participants" value just above the "add comment to issue". It was set to be copied from the trigger issue and then comment on the ticket. I'm thinking that the automation isn't realizing that the "Requested Participants" is actually set yet/it is seeing it as a null/empty value.

To get it to work I used the {{triggerissue.Request Participants.displayName}} command and that took care of it for me.

Thanks again for the help!

[David Pontarelli]

also now realizing the issue, i guess i could've used the "re-fetch issue data" operation. That was a lot of time wasted on something silly. Live and learn I guess.

[Hyrum Steffensen _Appfire_]

Glad to help, David! It always seems like there is always some "small" change that can throw off expected results. However, like you say, once a common error is known, it is easier to look for. As always, using the audit log is a great way to debug.

Regards,

Hyrum