Issue Summary

When the same custom field that is associated with Asset Object is added to both the Request Type and the Form, two undesirable issues occur for the Customer depending on the configuration used.

If you have a Form with two custom fields with the first being a required hidden custom field and the second being of type Assets Object with an AQL in the Filter Issue which is dependent on the first custom field, it will fail for unlicensed users with the following two messages: 

1. Couldn't send request:  This form contains a hidden field that does not have a valid default value configured
2. Validation failed for Insight object  

Steps to Reproduce

• Create two custom fields:

  Custom field	Type	Context
  CFA	Assets Object	"CFB"=${cfb.id}
  CFB	Version Picker (multiple versions) Multiselect Dropdown

• In a new Form, add the following:

  Custom field	Type	Linked Jira Field	Visibility	Required	Section
  CFA	Asset Objects	Linked Jira Field (CFA)	Yes	Yes	Main
  CFB	Multiselect Dropdown	Common Jira Field (CFB)	No	Yes	Hidden

NOTES: CFA contains a hidden option that matches the value stored in the CFB

• Add the Form to a Request Type
• Create an issue as a Customer in the Portal
• Create an issue as an Agent in the Portal 

Expected Results

When Customers and Agents submit the form,

• no validations should appear and,
• all values will be retained in the form after the issue is created.

Actual Results

When Customers submit the form,

• two validations appear preventing the issue from being created.

When Agents submit the form,

• no validations should appear and,
• all values will be retained in the form after the issue is created.

Workaround

There is currently NO workaround.