Summary

When editing the Assets macro in Confluence, if a user slightly modifies the AQL query and then clicks the Search button, the macro resets the configuration for columns to display. All previously selected columns are cleared, and the user has to manually re-enable the required columns again.
The users reasonably expect that adjusting the AQL filter (which controls which objects are shown) should not reset the column configuration (which controls which attributes/columns are shown). As a result, each AQL change forces users to redo their column selection work from scratch.

Suggestions for Improvement

• Persist column selection independently of AQL changes so that running a new AQL search (via the Search button) does not reset which columns are enabled.
• Treat AQL updates as filter-only changes, updating the row set but keeping the chosen columns and their order intact unless the user explicitly changes the column settings.