Configuring an Assets custom field's project context breaks the field when trying to edit it using an Automation rule from a project not added to the field context

Issue Summary

Configuring an Assets custom field's project context to be restricted to only certain projects causes the Assets custom field not to be editable using automation rules triggered from a project that is not in the field project scope.

Steps to Reproduce

Field setup:

1. Create an Assets custom field called Test Assets Field
2. Configure the custom field context to a single project, such as TEST
3. Ensure the field is associated with a field configuration screen on the TEST project

Automation setup:

1. Create this rule as a global rule so that it can be executed from multiple projects
2. Create an automation rule using the Manual trigger
3. Add a Create issue action to create a new issue, configuring it to use the TEST project with the Issue Type that the Test Assets Field was associated with
4. For the field use an AQL query to set an Object that matches an Assets Schema that you may already have in place, such as:

"Application name" = Jira

Trigger the rule:

1. Navigate to another project, such as SUPPORT
2. Find an existing issue and using the Actions menu find your automation rule
3. Execute the rule from the SUPPORT project ticket

Expected Results

The automation rule sets the object that matches the name Jira

Actual Results

The issue is created but the Assets custom field is not set, with the audit logs showing an Internal Server Error:

Create issue
An error occurred while requesting remote information
Internal server error
Issues created successfully
TEST-26

Workaround

The following article covers two workaround methods:

• Automation action returning Internal Server Error when editing Assets custom field

At a high level these are:

1. Use issue related branches to edit the Assets custom field on the most recently created issue
2. Add the source project that triggers the automation to the Assets custom field's context