All automation: Unknown fields set during edit, they may be unavailable for the project/type

[Roeland Schoppers]

Hi,

No matter the automation rule setup I try, I always get this error:

Edit issue

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -

Roadmap (customfield_10061)

No fields or field values to edit for issues (could be due to some field values not existing in a given project):

RDP-13

It's not what I want to accomplish but I went for the most basic setup to see if that could work, where I use the standard JDP field 'Roadmap' which is available without Advanced Fields, and i select the value Later

But this also throws the same error. 

What am I doing wrong here?

[Mart Postma · Accepted solution]

Hi @Roeland Schoppers 

For some fields, JPD Automation can only edit that field when referencing to the custom field ID. Even though Jira created this field "out of the box", it still treats it as a custom field (hence not referenceable by its default name).

You should add the following JSON to the field that appears when you select "> More options" on the "Edit issue" action. Do not select any field in the "Choose fields to set..." button.

{
   "fields": {
      "customfield_10061": "Later"
   }
}

 Example: 

Hope that works - let me know!

[Roeland Schoppers]

Hi @Mart Postma I still get the same error:

Another member posted a comment that they could select Roadmap and the automation worked for them. 

Bug?

[Mart Postma]

Hi @Roeland Schoppers 

That is indeed strange behaviour. Could you check under Rule details > Actor that the selected Actor for the rule execution has the correct permissions to execute such automation? Generally, the actor "Automation for Jira" should have sufficient permissions to do this. 

If that still doesn't work (or if that actor is already selected), then I would suggest reaching out to support. I had a similar issue where "Automation for Jira" needed a fix from Atlassian's side - might be the same for your issue.

[Roeland Schoppers]

@Mart Postma i checked the actor and it was set to Automation for Jira. I don't see a way of changing permissions for this role in JPD. In Jira Software it is set with correct permissions. As a test I changed actor to myself (admin) and the automation gave  a new error - which was due to the advanced code. Using the basic field Roadmap and Later the automation passed.

Do you know if its a bug if Automation for Jira fails as an actor or is there somewhere I can fix the permissions?

For now i'll leave the actor as my own user since that seems to work - thanks.

[Mart Postma]

Hi @Roeland Schoppers - That was the exact same issue I had before as well. The automation would run under my account, but not under the Automation for Jira account. At the time, I reached out to support and it looks like that only they can fix it, so not unfortunately yourself:

That being said, we identified a small issue with the permissions granted to the Automation bot on your site and are already working on a fix. As soon as I get an update from the engineering team I'll let you know!

So if you have the permissions to do so, reach out to Atlassian JPD support and link this Community thread, or ask your (technical) Atlassian site admin to do so for you. They usually don't undertake any action based on issues on the Community pages.

Hope they can help you!

[Bill Sheboy]

Hi @Roeland Schoppers 

I just tested and was able to update the default Roadmap field with a rule.

Have you checked your JPD project, and Jira site, to determine if there are multiple fields named Roadmap?

If so, you may need to rename the other one, or use an advanced edit with JSON using the correct custom field id to set the value in this rule:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-select-custom-field

Kind regards,
Bill

[Roeland Schoppers]

Hey @Bill Sheboy thanks for the answer. 

This is the only roadmap field both in Discovery as Jira Software:

I also have an automation with the same error where I name the exact field:

[Bill Sheboy]

Thanks for confirming the fields.

As I and other posters are successful with this type of rule, without changing the rule actor, I suspect there is a permissions issue or something amiss with your JPD project or the user configurations.

At this point I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/  They may see something in logging that we cannot as customers. 

When you hear back from them, please post what you learn to benefit the community.  Thanks!

[Viktoryia K_]

@Roeland Schoppers Hello!

Is this custom field used in your project? Has it been added to the request type screens? Perhaps you forgot to add a field to the required screen?

[Roeland Schoppers]

@Viktoryia K_ this is a standard/default project field that is already added to the sysem when you enable Jira Discovery Project. It is used in the project and also available as a field on the edited Idea that was to be triggered.

I looked at the screens settings but this is a Jira Software setting right? Not a Jira Discovery setting? It only shows issue types and fields that you have in Jira Software not Jira Discovery.