Issue Summary

Issue cannot be created on customer portal when an Assets custom field with global context refer to another custom field not in the context of the project

Steps to Reproduce

• Create one Assets custom field A with global context.
• Create another custom field B. It does not have to be Assets custom field as long as it can be referred as placeholder in the filter issue scope of custom field A.
• In custom field A refer to custom field B value in the Filter Issue Scope (Ex. Key = ${customfield_B}.
• Set a default value for custom field A.
• Create project A and project B.
• Associate Custom field B only to project B in the context.
• Do not add those fields to any screen or request types of the 2 projects.
• Try to create an issue from the customer portal of project A. Note that an error is thrown out when clicking on create This form contains a hidden field that does not have a valid default value configured and the issue is not created:
  
• By checking the HAR file when the issue is trying to be created we observe the error pointing at custom field A. The message state that custom field A cannot find the object. Note again that nor field A or B are added to the request type:

  {
      "errors": [
          {
              "errorMessage": "This form contains a hidden field that does not have a valid default value configured"
          },
          {
              "errorMessage": "Could not find Assets object/s (TEST-1)",
              "field": "customfield_10123"
          }
      ],
      "reasonKey": "validation.error",
      "reasonCode": "400"
  

Expected Results

Jira issue should be created anyway since nor field A or B are added to the request type of the project.

Actual Results

The Jira issue is not created from the customer portal and the error message above is thrown.

Workaround

• By checking the HAR file while issue is created identify the ID of custom field affected.
• Check the affected custom field configuration Issue Filter Scope and identify the referred custom field B not associated to project A.
• Either remove the reference to custom field B or go in the configuration of custom field B and change the context to associate it also to project A.

Versions Tested

• Testing Requirements	Version	Affected Version

• Customers Reported Version

  10.3.3 - Yes

• Most Recent Bug-Fix Release

  10.5.0 - Yes

• Most Recent LTS

  10.3.x Yes

• Previous Supported LTS

  5.12.x - No