Hello 7260236ab89d, is there any workaround or any progress on this issue? Thank you!

+1

Any updates here?

utilizing object manipulation tab

With the new paid "workarounds", this might not get any traction. Effectively, you can save AQL queries using either the "Dashboard Gadget for Assets" in Jira or "Macro for Assets" in Confluence. I find these work very well, but they carry an additional cost. 

We just migrated from on-premises and discovered after that saved filters is not possible. What's going on? No dashboards? No reports? This is essential functionality! Come on, Atlassian. You forced us to the cloud, now make it worth our while and additional $$$$$ you're charging us.

Saving AQL queries for later reuse offers several important advantages:

Saving time: Saving AQL queries means you don't have to rewrite complex queries every time they're needed. This saves time, especially for frequently used queries.

Accuracy and consistency: By recording AQL queries, you guarantee the consistency of the results obtained. Once a query has been tested and validated, you can be sure that the results will be the same every time it is run.

Reusability: Saved queries can be reused in different contexts and by different people, promoting collaboration and productivity within a team.

Documentation: Recorded queries also serve as documentation for future analyses or for other team members. They can help to understand the logic behind data processing and the methods used.

Easier maintenance: When modifications are needed, it's easier to make them to a saved query, rather than manually searching for and modifying all occurrences of the same query in the code.

Control and traceability: By recording the queries used in an application or system, you can better control and trace the actions performed on the database, which is essential for security management. 

In short, recording AQL queries offers an effective way of managing and optimizing the database query process, improving productivity, consistency and traceability of operations carried out.

We also believe that this missing feature is frustrating.
It is unthinkable to have to create a report manually every time, without the possibility of saving it.
I would ask you to prioritize this issue.

We are currently deploying Assets in Cloud version in our organization with thousands of hardware assets and many more to be added in software. It is practically essential to have the possibility of using saved filters. I hope this solution is developed as soon as possible.

Can you at least do something simple like accept an iql query parameter so we can save our own saved searches in a browser favorites?

https://yourinstance.atlassian.net/jira/servicedesk/insight/object-schemas/40?typeId=147&view=list&iql=Name=My%20Object%20Name