Jira Automation Fails To Run

Nigel Bogle February 21, 2024

Hi Folks,

At this point, I feel I am going around in circles having tried various things to solve this issue.  

I should say from the outset, I am a newbie to the site but love the product.

Today I setup my first automation in Jira Product Discovery and it runs as follows:

Once an issue changes from status A to status B I want to set a value in a new custom field I have created.  


However, if the Actor is set to 'Automation for Jira' the rule fails with the following error:

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Deferment date (customfield_10063)
No fields or field values to edit for issues (could be due to some field values not existing in a given project): STOR-6

If I set the Actor to my user and try then the automation runs perfectly.


Seems to suggest permissions on the 'Automation for Jira' user. 

So, I looked at the Default permission scheme (the only one I use) and even though ALL permissions have the 'atlassian-addons-project-access' project role assigned, the automation fails to execute.

if any kind soul can resolve, there's a coffee available or a large whiskey. 🥃

Your help would be MUCH appreciated.

Sending you all my best,

Nigel.

3 answers

1 accepted

1 vote
Answer accepted
Nigel Bogle February 23, 2024

⭐️ I have an update for all watchers on this thread…

This is primarily to help others who may be having the same issue and to save hours going in and out of screens trying numerous combinations, setting permissions, flicking switches and generally driving yourself crazy wondering what’s going on.  

Ironically, if you are not entirely sure what you're doing, particularly when messing around with things like permissions, this could actually exacerbate the situation!

Thank you to everyone in the Community who took the time to consider the problem and offer their advice on how to fix the issue. 🙏🏻

 


Note: I should also point out that this update is not a 'fix all' scenario.  I.e. There may well be settings in your system that are not set as they ought to be and need changed as suggested in other answers.  

This is simply to offer a ray of hope for those people who, like me, are new to the product and who had tried all the helpful things those more expert than I had kindly suggested in their answers previously.


 

As of this morning, I’ve had an update from the super helpful support team at Atlassian, and they appear to have resolved the issue by making some changes under the hood. 👏🏻

Quote from Atlassian Support Team Member:

I had reached out to the team and the user group for JPD has been added for automation for Jira. Could you please check if it is working now for you?

I am very grateful to all concerned at Atlassian for their help with this.  

My JPD automations now run as required using 'Automation for Jira' as the Rule Actor.

 

I hope this proves helpful to anyone else in a similar position.

Have a great weekend all.

Nigel. 

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 23, 2024

so glad they were able to get you fixed up

Like Nigel Bogle likes this
0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 21, 2024

Hi Nigel,

This is not an error with the user permission but access the custom field itself. Make sure the custom field is on the Edit screen for the project. If you can edit the field on the screen then that's a good indication the rule should work to update the issue. 

Nigel Bogle February 22, 2024

Good afternoon from Ireland, John. ☘️

 

If I open the JPD issue the field that needs to be edited is there and I can change the value.

It seems odd that the automation works every time if I set the rule actor to MY user but when I set the actor to ‘Automation for Jira’ the automation fails consistently with the message I posted from the Audit Log.

Granted, the message refers to the inability to find the field yet it still feels like permissions somewhere given my lived experience of it working for one user and not another as the rule actor.

I’d be grateful for your further insights.

All good things,

Nigel. 

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 22, 2024

That's very baffling since you are on a Free site and there should be no Permission limitations at all. 

Can you share a screenshot of your rule, especially any details related to that field? 

Like Nigel Bogle likes this
Nigel Bogle February 22, 2024

Thanks, John. 🙏🏻

I’ve just had a message from the support team and it reads…

“Checking on our end we can see that indeed the user used for Automation isn't included in the JPD groups and we're working on having it corrected!”

Sounds like there’s an issue under the hood and I will keep you posted.

 

I am grateful for the community support.

Sincerely,

Nigel.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 22, 2024

Ah, so something on the JPD side. That makes sense because it is so new. Glad they uncovered that and getting it fixed. 

Like Nigel Bogle likes this
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 22, 2024

Greetings!

My hypothesis is there may not be a quick "fix" for this with automation rules, as that would allow customers to bypass the licensing model for JPD (which is different from both Jira Cloud and Automation packaging limits).  For example, a rule could be triggered to change an Idea issue by a user who is not a Creator for JPD.

I suspect our vendor will either:

  • recommend customers change the rule actor for JPD-impacting rules to that of a user with a Creator license
  • wait a long while to assess how many customers are using rules with JPD, and at time decide if the Automation for Jira user's permissions should be broadened to include JPD Creator

Kind regards,
Bill

0 votes
Bailey Hecksel February 21, 2024

Nigel - this may or may not help, but I would start with the "permission helper". You can hit your period key to pull up a quick-navigation menu (as an admin) and search for the permission helper there.

Once you have the permission helper open, select the "Automation for Jira" account, choose any issue that falls under that project, then choose the "edit issue" permission and click Submit.

2024-02-21 17_42_23-Permission helper - JIRA.png

If that tells you the account does not have permissions to edit issues in that project, I'm guessing that will lead you to your answer.

Hope this helps!

Nigel Bogle February 21, 2024

Hey Bailey.

Thanks for the suggestion.  I’ve just tried pulling up the “permission helper” and started to type “automation for Jira” into the user but no matches.  It just shows me actual users as opposed to built-in users.

Am I doing something wrong?

Nigel Bogle February 21, 2024

As an addendum to my last message, I noticed the account in your screen shot was ‘automation’.

Have you had to setup this account as a specific user?  I was under the impression that there was a built-in account.

Apologies in advance for the clumsy nature of the question.  Comes with being a newbie I guess.

Thank you again for your collaboration on this.

Nigel.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events