Our users want to work quickly in AEM. However, the inconsistent button order of the menu bar slows them down. We got a number of complaints by our authors regarding the Author instance UI: Authors are irritated by the changing order of buttons throughout the DAM and Sites.
Current/Experienced Behavior:
Each content type (image, video, pdf, webpage, CF) changes the order to some degree. Our authors understand that different asset types may have different options, but the position of the buttons changes too much for them.
Improved/Expected Behavior:
Our users work mostly with Sites and expect the DAM button to be at the same location, which is hardly the case. See screenshots. We would move the options that are available to all types in front and the specific ones at the end. That should ease their situation. Either this comes by default, or our admins can configure the order of button per content type. However, we would prefer to have it out of the box.
Environment Details (AEM version/service pack, any other specifics if applicable):
Yes! I second this proposal! I might add, that in AEM assets, the order seems to change at random. One time, the (move) Button is in the middle, the next time it is to the left or hidden in the burger menu. I want to make some user guides where the users can relate the preview to what they see on their screen.
This has been reported to the engineering under the internal reference ASSETS-30744. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Hi @martinkastler@Adilos-Cantuerk thanks for the feedback; this is already fixed in the new Assets user interface, but placing common operations first and also letting users configure the buttons for their preference makes sense to allow users to work faster. We will review this internally and update this thread when we have a plan to implement
Hi @martinkastler this means we've acknowledged the issue and proposal and will be reviewing the work needed internally. You should see updates to the ticket as it enters development phase through release to GA.
