nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Vladislav Denisov_thd1hf

Hello!

I'm trying to set an automation to copy fields from the linked task to the main one in `Product Discovery` board

Got this error:

Action details:

["10021","10025"]

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

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

The whole rule looks like this:

Screenshot 2024-11-20 161306.png

I've tried to set it in the UI for WPT-709, and found such HTTP request:

`{"fields":{"customfield_10163":"https://test.com"}}`

So it uses the same custom field ID.

What am I doing wrong?

Accepted answers

Bill Sheboy

Hi @Vladislav Denisov

Automation rules defined in one scope / project trying to update issue fields in another project sometimes have problems accessing the field for edits using the dropdown field selection.

Have you tried using advanced edit with JSON to change the field using its custom field id?

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

Kind regards,
Bill

All comments

Jehan Bhathena

Hi @Vladislav Denisov

From the above automation, is WPT-709 the linked ticket? or the ticket that triggered the automation?

The error that you get may also be due to lack of permissions, can you check your permission to verify if Automation for Jira has permission to edit your issue?

Would also suggest adding a "Log Action" to verify the Issue on which the action is being taken, so that you can debug it in times of an error.

Vladislav Denisov_thd1hf

Hi @Jehan Bhathena

Yes, WPT-709 is linked ticket.

> The error that you get may also be due to lack of permissions, can you check your permission to verify if Automation for Jira has permission to edit your issue?

Could you clarify how to check it? I have both projects enabled in Global Automation -> My automation -> Projects.

Vladislav Denisov_thd1hf

Screenshot 2024-11-21 124122.png

Here are the details from "Audit log". I'm making a transition for WA-56 and it should trigger field change for WPT-709. WPT project has Report field with ID 10163.

Jehan Bhathena

Hi @Vladislav Denisov

Reference: https://support.atlassian.com/automation/kb/automation-for-jira-permission-issue/

Check for the group Atlassian-addons-project-access, and if it's present in your permission scheme.

Bill Sheboy

Hi @Vladislav Denisov

Automation rules defined in one scope / project trying to update issue fields in another project sometimes have problems accessing the field for edits using the dropdown field selection.

Have you tried using advanced edit with JSON to change the field using its custom field id?

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

Kind regards,
Bill

Vladislav Denisov_thd1hf

Hi!

Yes, I've tried, but had the same error.

Bill Sheboy

Have you confirmed that is the correct field's custom field id? You may do that using this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

In your case, the field appears to be in the Jira Product Discovery (JPD) Idea issue, and so please check an example Idea from that project.

Have you checked if there are any workflow conditions / actions for that transition which could impact the edit?

Vladislav Denisov_thd1hf

Yes, I've checked the field ID both with API and using Network tab in browser while changing value in UI. Moreover, I've tried to make changes with common fields like summary, but it didn't work and had the same error.