Problem Statement:

As a developer, I want to validate my Asset data based on a Custom Field before trying to add or update an Assets Object, Attribute, or other value, using a singular API

Summary:

When working with Jira's Assets API, users wish to be able to validate the data before trying to create or edit an Object, object attributes, or similar.

As apart of this, they want to be able to use a singular API endpoint to pull in relevant details based on a custom field used by issues in Jira, without having to work between Jira and Assets specific API endpoints

Suggestion:

Developers should be able to use Assets Object API Endpoint to check an Assets Custom Field to determine if the object exists first. 

For example:  The endpoint /assets/1.0/aql/objects should be able to check to see if an object exists based on a custom field in Jira.

Impact:

This would simplify the API flow in Jira, and Assets, allowing for more efficient coding. In turn, this saves time and resources to achieve a data-integrity goal

Work Around:

Currently, you must use Jira's Issue or Search API endpoint to discover if there is Assets Data in the given Assets Custom Field. 

Then, you can use that data to query the Assets API to learn more about the object