Assets custom field "We couldn't fetch any objects for this field" error in Jira Service Management Cloud
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
Jira users encounter difficulty selecting objects from the Assets custom field within the Jira issue view. Customers also face challenges in selecting objects from customer portal, as they are met with an error message stating:
"We couldn't fetch any objects for this field."
Diagnosis
The error may vary depending on the location:
Where the error appears | Message shown | Check |
|---|---|---|
Jira issue create screen, edit issue, or Forms screen |
| Remove attributes that no longer exist in the Assets custom field configuration filter, and ensure the AQL query is valid. |
Issue transition screen |
| Check the filter and ensure the AQL is valid. |
Customer portal view |
| Ask your team or admin for support. |
Cause
The configuration of the custom field for assets is invalid because of missing attributes.
Note: AQL filters only work with attributes that are defined in the schema, not with attributes imported directly from data files. Verify the schema to ensure the required attributes exist.
Solution
Within the Assets object/s field configuration, note the configured Object Schema and the attributes used in these fields:
Filter scope (AQL)
Filter issue scope (AQL)
Allow search filtering by these attributes
Object attributes to display on issue view
Open Assets in a new tab, navigate to the object schema, and open the object type configured in the custom field. Select Attributes, then compare the attributes defined in the schema with those configured in the custom field. If an attribute is missing from the schema, return to the custom field configuration, select Edit Assets object/s field configuration, update the AQL, or remove the missing attribute from Allow search filtering by these attributes and Object attributes to display on issue view, and select Save.
Reference:
Was this helpful?