JPD automation to update field when status changes

[Fiona Lauchlan]

I'd like to create automation so that when a ticket is transitioned to a certain status, a certain field option is populated.

I receive a failure message that there are unknown or no fields set 

I have tried When Issue is transitioned to..(certain status)

and Then Edit issue Fields (and selected the relevant field and option) but it does not work.

[Bill Sheboy · Accepted solution]

Hi @Fiona Lauchlan -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

* in which project is your rule: the JPD project, a different one, or global
* an image of your complete automation rule
* images of any relevant actions / conditions / branches
* an image of the audit log details showing the rule execution
* explain what is not working as expected.

Kind regards,
Bill

[Fiona Lauchlan]

Hi, this is in JPD
Here are 2 images of the 2-step automation rules I created;

I receive the following audit log error

This is the following issue message i receive in audit log

[Bill Sheboy]

Thanks for that information, Fiona.

Have you checked if there are other fields named Roadmap in your site, and the rule is possibly trying to update the wrong one?  Your Jira Site Admin can help check that.

You could use this how-to article with an example issue, such as PRODM-460, to confirm the rule is trying to update the correct field: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

The essential steps are to lookup the issues fields using a browser tab to call the REST API, and then search for your field on the page, such as with CNTRL-F.

The audit log shows the rule trying to update customfield_12401, so compare that to what you see.

[Fiona Lauchlan]

thanks. After some investigation I've finally discovered the issue...  I needed to have myself assigned as 'actor' in the actor field, rather than 'automation for Jira' being assigned, so there was a licenced Jira user associated to the automation.

[Bill Sheboy]

That makes sense as JPD requires the user to have Creator permissions to make most changes.

Which user was the actor originally?

[Fiona Lauchlan]

it was just set as automation for Jira, so not set user

[Bill Sheboy]

Yes, I believe that is a known problem / behavior with the built-in Automation for Jira user and JPD projects...the built-in user normally has enough elevated permissions to do anything, but not for always for JPD.