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

[Vladislav Denisov]

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:

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?

[Bill Sheboy · Accepted solution]

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]

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]

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.

[Bill Sheboy]

To help provide context for this symptom, please post images of:

• the current, complete rule, in one single image
• the rule details at the top, showing the scope, actor, etc.
• the edit issue action
• the audit log details showing the rule execution

Thanks!

[Vladislav Denisov]

@Bill Sheboy Sorry for the late answer. He are the screenshots with information you've requested:

[Bill Sheboy]

The way your rule is written, it does this:

GIVEN an issue has linked issues
WHEN the issue transitions to Done
THEN FOR EACH linked issue of link-type Implements
          EDIT the linked issue's Summary back to same value

That is probably not what you wanted to do.  Did you instead want to do this?

GIVEN a JPD Idea has linked issues (i.e., Discovery Tickets) in software projects
WHEN a linked issue transitions to Done
THEN concatenate the completed issue's Summary to the end of "field x" in the JPD Idea

[Vladislav Denisov]

Yes, you're right except the last step.

Here is my use case:

I have JPD idea and it has tickets in Analytics and Design projects. When analysts complete the task, they'll close it with Report field filled. Then the Report field should be copied from analysts task to JPD idea. The same with Design but with other field.

I've shown the example with Summary to check that it doesn't work even with default fields.

By the way, with the flow from screenshots, trigger starts when I move linked task to Done, not the idea in JPD.

[Bill Sheboy]

Thank you for clarifying the scenario!

Your rule will need to use the multiple-project scope setting to access the issues.  Your Jira Site Admin will need to make the change in the global rule administration.

Next, do you want to concatenate the field value to the JPD Idea field or replace it?  Let's assume you want to concatenate.

• trigger: issue transitioned to Done
• condition: project is in the Analytics or the Design one
• branch: to the linked issue of the type "implements"
  • condition: issue type equals Idea (This prevents other accidental updates.)
  • action: edit the field, concatenating the value from the trigger issue
    • Let's assume the Idea field is also named Report, the edit could add a delimiter between the values.
      • {{issue.Report}}; {{triggerIssue.Report}}

What is the type of the field in the Idea which you want to update?

[Vladislav Denisov]

This didn't help me, but I've found the solution.

Because JPD has separate user permissions, the default user for automations wasn't allowed to change something. I've changed it, and now it works.

[Vladislav Denisov]

@Bill Sheboy thanks for the help and the `triggerIssue` hint.

[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]

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]

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.

[Vladislav Denisov]

@Jehan Bhathena Thanks, but I don't see Permissions page for these projects. It works for projects with "Company managed software" type, but doesn't for "Team managed software" or "Product Discovery".

[Jehan Bhathena]

Oh ok, I haven't tested this on a Team Managed project yet.

Let me check if I can find anything for that and get back to you.