JPD automation fails when the actor is Automation for Jira

[Marek Stracanek]

Within our company, we have JPD product set up and when setting up automations, none of them seem to work and they always fail with an error, e.g.:

Edited issue successfully, however some of the set fields aren't available. Fields ignored:

Source Team (customfield_10226)

Upon playing around and trying all possible scenarios, I found out this problem only applies to the case when the actor is Automation for Jira.

Upon reading similar posts and questions on this issue in the community, it seems like Atlassian support can do something on their end, to make sure Automation actor is included in the JPD groups.

Therefore - could someone help me please?

[Bill Sheboy]

Hi @Marek Stracanek -- Welcome to the Atlassian Community!

First, a disclaimer: I am just another Jira user and have no business relationship with Atlassian or any of their marketplace partners.  With that out of the way...

Yes, I believe this symptom is a side-effect of the licensing model for JPD where the usually, all powerful Automation for Jira user still does not have enough permissions to do some things related to Idea issue types.  (And in my opinion, they [Atlassian] probably do not want that user to generally have such permissions as it would allow bypassing paid license seats.)

I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/

Kind regards,
Bill

[Marek Stracanek]

Thanks for your response, unfortunately we do not have a tier, where we can create a support ticket for JPD, so I am putting my hopes into the power of community, where some of the Atlassian folks might read it and help out.

[Bill Sheboy]

The normal workaround for this scenario is to change the rule actor to a user with Creator permissions.

If that does not help, please post the following for context and perhaps the community will have more suggestions:

• an image of your complete rule in one single image for continuity
• images of any relevant trigger, actions, conditions, and branches
• an image of the audit log details showing the rule execution, with all of the areas expanded

Other possible causes are: the field is not on an issue edit view, there is a workflow validator, or for multiple-project rules, the rule scope is incorrect.