Set STAKEHOLDERS in JSM incidents via Automation

[Tim Finch]

Hi,

I am using the Stakeholder system field in Incidents.

JSM is tied to Assets.

In assets we have objects for each client' (company) and an attribute 'Stakeholders' which is a multi-user attribute.

I want to create an automation rule that auto populates the STAKEHOLDERS in the JSM incident based off the company set and drawing from the object attributes.

If this was a normal user select field I can do this. But I cant seem to find a way to do this for the STAKEHOLDERS field.

Anyone have any ideas?

[Bob Boursaw]

Hey Tim, Julian, 

Stakeholders cannot be set via automation (directly) at this time, but we do have a couple of feature suggestions that you may want to follow and vote-up that are related.

• JSDCLOUD-14383 - Stakeholders field can't be set automatically
• JSDCLOUD-14359 - Include Stakeholder to automation action targets

The first one includes the following workaround.

Workaround:

The REST API Add stakeholders can be used alongside Send Web Request action in Automation to accomplish this for now.

Have a good one!

Bob

[Julian Xhokaxhiu]

Hi,

I'm trying to accomplish the very same thing. I found out we can set Stakeholders using the Automation Edit Issue action. Problem is that despite Automation saying that it did add Stakeholders successfully, the ticket has 0 Stakeholders set unless I set them manually in the ticket.

Can please someone from Atlassian help on this? Doesn't make much sense to me to provide an automation that does just not work. Looks like a bug to me at least.

Thank you in advance and best regards,
Julian