Help with Automation in Jira Product Discovery - "Unknown fields set during edit" erro

[Vyshnavi S]

Hello, Atlassian Community!

I’m working on an automation rule in a Jira Product Discovery project where fields are created directly within the project, rather than using traditional custom fields.

Goal of the Automation:

Whenever the field Compliance is set to Yes, I want the field Compliance Score to update to 1. Conversely, if Compliance is set to No, then Compliance Score should update to 0.

Problem:

When running the automation, I receive the following error:

Edit issue Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Compliance Score (customfield_10106) No fields or field values to edit for issues (could be due to some field values not existing in a given project): MDP-3

Since Compliance Score is a field created directly in this Jira Product Discovery project (not a traditional custom field with a customfield_ ID), I suspect the automation may not be recognizing it correctly. I have tried selecting Compliance Score directly in the Edit issue action within automation, but the issue persists.

Has anyone encountered this in Jira Product Discovery projects, or does anyone have advice on how to properly reference these project-specific fields in automation rules?

Thanks in advance for any insights!

[Gary Spross · Accepted solution]

@Vyshnavi S , it's been suggested to me to utilize the "Advanced fields" section of the edit issue component, specifying the field by it's custom field identifier, as opposed to selecting the field from the drop down. This is necessary because fields created within this project are unique to the project (as you already know) so the selected field from the drop down may not actually be the field contained within the associated project.

You can determine the field id via the Rest API call: 

https://instance_name.atlassian.net/rest/api/3/issue/issue_key?expand=names

In the "Advanced fields" section of the edit component, you would put something like this:

{
     "fields": {
       "customfield_12345": 1
     }
}

[Nick Haller · Accepted solution]

Hi @Vyshnavi S ,

It could be the Automation for Jira (A4J) user is not granted JPD permissions. This has been a minor issue with some customers. Engineering is aware, and hopefully has a fix soon. In the meantime, try adjusting the Actor of the automation to someone with JPD permissions, and retest.

Feel free to share a screenshot of the automation if the suggestion above does not work.

Also - out of curiosity - what field types are both the Compliance (Yes/No), then Compliance Score (0/1)?? I could try testing on my end with something similar.

[Vyshnavi S]

Compliance is a short text field where as Compliance Score is number field in jira product discovery project

[Nick Haller]

Thank you! I tested in my instance with the same field types, and got this automation to work as expected using an IF/ELSE component:

1. WHEN: Any changes for Compliance field
2. IF: Compliance field contains "Yes"
3. THEN: Edit Compliance Score = 1
4. IF/ELSE: Compliance field contains "No"
5. THEN: Edit Compliance Score = 1

Personally I would consider using different field types for each of these, but every use case is different! For example I may have the Compliance field be a single-select with "Yes" and "No" being the two options. And I may have the Compliance Score be a checkbox field. Here's more about JPD fields in general.

Regardless, this should be configurable! Again, try reviewing the rule above to yours, and/or adjusting the Actor to see if that makes any difference.

[Vyshnavi S]

After adjusting the Actor of the automation to someone with JPD permissions that is me project admin, This rule is working Thanks for the help :)

[Nick Haller]

Glad to hear! Sorry for any inconvenience on this too - not an easy thing to identify, especially with the error shown. Hopefully engineering has a fix for this soon.

[Gary Spross]

@Nick Haller ,

Could the fix not be to just add the "Automation For Jira" account into JPD. same as it is in place for Jira & JSM, even Team-managed projects of those products?

[Nick Haller]

@Gary Spross ,

I don't believe it is. Ideally it'd be possible to manage the A4J user within your site, but this is only something Atlassian Support can complete at this time. And the A4J user cannot be added to a JPD project either:

Although you may not be able to search for the A4J user in your site's UI, it's still possible to find them using the GET ALL USERS API. After this command,

Copy the A4J user's accountId >>

Click into any user within your site >>

Within the URL, replace the current user's accountId with the A4J user's accountId

And you should be able to access the A4J user in your site. But again, I don't believe you'll be able to manage them such as adding them into other groups, and instead will be met with errors.

[Gary Spross]

@Nick Haller , sorry, I didn't mean for the customer to have to add the A4J user to the JPD projects. I meant for Atlassian to include the A4J user (or the permission "Project Role (atlassian-addons-project-access)") to the backend JPD project permissions.

However it's currently configured for Jira or JSM Team-managed style projects to work with automation using the A4J account as the actor. The A4J user isn't added individually to Jira or JSM Team-managed style projects, yet somehow automation rules using the A4J actor can run against them.

[Nick Haller]

That's basically the issue some customers are facing with the A4J user, and this user not being (by default) added into the JPD users group - so they are not being granted product access. 

[Gary Spross]

Seems like it would be a "quick fix" for Atlassian. The framework already exists for TMP's in Jira & JSM. Implementing this would be one less issue for customers to have to worry about.