Issue Summary

This is reproducible on Data Center:  (no)

In an application that interacts with an Assets custom field in Jira, there is a need to respect the range of AQL (Asset Query Language) filters that users have configured for their Assets custom field in the Jira instance.

However, there is encountered a limitation with the current Jira REST API. There is no public API endpoint that allows me to fetch the AQL filter scope for an Assets custom field. The autoCompleteUrl endpoint, which seems to use the AQL filter scope in the background, is an internal API and its usage is not recommended due to potential changes that could break my application.

This limitation poses a significant challenge the application development. Without the ability to fetch the AQL filter scope, the application cannot accurately reflect the Assets custom field configuration that users have set up in their Jira instance.

Expected Results

There is a public API endpoint that allows developers to fetch the AQL filter scope for an Assets custom field. This feature would greatly enhance the ability of third-party applications to interact with Jira's Assets custom field in a way that respects user configurations.

Actual Results

There is no public API endpoint that allows me to fetch the AQL filter scope for an Assets custom field. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available