Issue Summary

Assets custom fields can use the Issue Filter Scope (AQL) configuration to filter the data returned based on the value of another custom field. When referencing an Assets custom field in this way, specific attributes can be identified such as ${customfield_12345.label}.

This occurs either when referencing the same custom field in multiple custom fields or when making a reference to the same field twice in the same field, if the references are not aligned, this can cause the form creation to fail due to malformed AQL that the issue creation sends to Assets.

This has primarily been identified when the referenced data uses special characters including spaces. The issue was seen when using Assets custom fields in a Jira Service Management Form.

Steps to Reproduce

1. Create an Assets custom field called Field One, say the id for this will be 12345
2. Create another Assets custom field called Field Two, in this case we'll use id 56789
3. The attribute set in Field One should use a special character in the label or have a space in it, example Test One
4. On Field Two using the Issue Filter Scope (AQL) filter use the following AQL:

   Service IN ${customfield_12345.label} OR Service IN ${customfield_12345}

Note how the same filter uses customfield_12345 in the filter but one uses .label while the other does not.

Expected Results

The issue is created with the Assets data selected.

Actual Results

The data is missing from the Assets custom field due to a backend error

Workaround

Ensure that references in the filter scope align where all the fields use the same reference format. In the example above the following should fix it:

Service IN ${customfield_12345.label} OR Service IN ${customfield_12345.label}