90325da67d46 I've had to use the Assets macro for a while now. Please, please fix the issue where it forgets column configuration if you refresh the query. The Jira macro manages just fine.

Another issue: The macro doesn't play nicely in PDF exports. If it does export, it's just the window that exports, not any data below the scroll. Perhaps an option to show all results with no scroll?

90325da67d46 Another issue. The Assets macro doesn't render markup in text areas.

90325da67d46 

I just noticed another useful data centre feature missing from this cloud macro; export to CSV.

Is there a development path for the macro?

Re col config. As a short term fix, could it run off a comma separated list? That way we could paste the column list into the macro, making config much quicker,  even if we had to paste it in every time we changed the query.

90325da67d46 Thank you for the reply, I do not like the idea of displaying all columns as then it becomes the converse and you have to remember what to remove instead of add.

What if there were two assets gadgets, one that can only return a single object type and one that could be multi-object type. Thus if there was a single object type gadget you know that if the aql is updated and the object type did not change then the columns could stay as is.

Hi 90325da67d46,

Thanks for your response.

I also feel the pain of manually re-adding the columns (and remembering what columns were there, their order, and their column width) when I made a minor update in AQL.

Regarding column selection and the trade-off, I totally agree that having relevant attributes is a better choice (as opposed to all attributes). However, can column selections be only updated (or reset) when the search returns a different Object Type? In other words, is it possible to reset column selection only if there will be a change in column selections?

This is like the best of two worlds.

Kind regards,

Milad

90325da67d46 For column config, could it run off a comma separated list? That way we could paste the column list into the macro, making config much quicker,  even if we had to paste it in every time we changed the query.

90325da67d46 Thanks v. much for reply. Most of the objects I work with have a lot of attributes, it's rare that all would be relevant in a specific context, so not sure it would be that useful to list all. As an option in rare cases perhaps.

Is there a development path for the macro?

I use a combination of Confluence, Assets, and Jira as a document management system. Documents in Confluence, metadata in Assets, and change management in Jira. I have a couple of thousand product, business, and compliance documents in the system.

Displaying a cut of document info in the document is really useful - UIDs,  ownership, distribution, and dates.

I also use the macro to generate document directories - all docs of a specific type that relate to a specific ISO standard, for example.

We're moving to Cloud, and this is going to be harder with the new macro. I may have to revert to hard coding (duplicating) info in docs  and just linking to objects. Is a step backwards, which is a shame.

Hi b3a842920f7f and 66aad649a75d ,

Thank you so much for your feedback - it’s incredibly valuable to us.

Regarding the column selection, currently, our system dynamically builds the column list based on your search results. Since the list of columns is tied to what your query returns, we reset your selection each time you search, even if you've just modified the order. We understand this can be frustrating. The alternative would be to display all columns within your selected schema at all times, allowing us to maintain your column selection regardless of your search. However, we felt this approach might be more confusing and result in an overly long column list with many irrelevant options. That said, we’d love to hear if you think this trade-off would work better for you.

As for the vertical display, it is one of our top priorities following our current efforts to enhance the performance and reliability of Assets, stay tuned for further updates in that space.

Regarding the bug you mentioned, I’ll report it to our engineering team right away.

Thank you again for your insights.

Best regards,
Mohamed Hassan

Agreed that the column config resetting when you update the AQL is a huge miss, This prevents easy copying of the page/macro and simply updating a single condition in the AQL.

90325da67d46 

Great... but (sorry):

1: Would like to display vertically

2: It forgets column config whenever you update the query, making it really tedious to use when updating 

3: There's a bug with the col config search box - doesn't work until you select/deselect a col