Issue Summary

This is reproducible on Data Center: (yes)

The REST endpoint /rest/insight/1.0/iql/objects/ was modified during the re-branding to Assets to: /rest/assets/1.0/aql/objects/ 

both endpoints are supposed to be interchangeable - and they are: /iql/ ⇄ /aql/ . 
The same goes for the paths including /assets/ ⇄ /insight/ .

The issue is with the end point parameters - these are NOT interchangeable, and aql is not a documented parameter.

Documentation for the IQL endpoint here - indicates the following param: iql=<IQL query>

Documentation for the AQL endpoint here - indicates the deprecation of the iql param, and introduces a new param: qlQuery=<AQL query>

Customers assume the IQL and AQL are interchangeable, as part of the re-branding to Assets, and try to call: /rest/assets/1.0/aql/objects?aql=objectType=<nnn>

the aql param is not documented, but the query will return a response with objects, not corresponding to the AQL.

Steps to Reproduce

1. In a working environments, with a few schemes and Object types use Postman or any http client to query the following endpoints:
2. <Jira>/rest/assets/1.0/aql/objects?iql=objectType=<nnn>
3. <Jira>/rest/assets/1.0/aql/objects?aql=objectType=<nnn>

Expected Results

2 - returns objects from OTID nnn

3- returns a 40x error to indicate the param is not valid, or, return the correct set of objects for OTID nnn

Actual Results

2 - returns objects from OTID nnn

3- returns a set of objects, not necessarily belonging to or in the same schema as OTID nnn

This behaviour may cause the user to believe they are getting correct responses, while they are actually not - and this may affect reporting / automation and data integrity in other applications

...

Workaround

Use the latest documented method:

<Jira>/rest/assets/1.0/aql/objects?qlQuery=objectType=<nnn>

or the previous:
<Jira>/rest/insight/1.0/aql/objects?iql=objectType=<nnn>