Improvement - Custom report (Dropdown in menu)

[Birkaransingh94]

I wanted to raise a couple of user experience issues with the interface when accessing custom reports in view mode (non super user).

Firstly it is not obviously there is a drop-down menu here and it looks on first impression there is only one report.

Secondly, once established this is a drop-down menu, it can be very cumbersome to access the reports at the bottom of the list. On my screen, there are two scroll bars – one on the list and one on the overall Matomo screen.

If only using the scroll contained within the list, you cannot get to the bottom and see the last few reports

If you then click on the overall scroll bar to see the bottom of the drop down the Matomo screen re-sets and you lose everything.

Please, can this be looked at and improved?

[bx80]

Thanks for the suggestions @Birkaransingh94, UI improvement feedback is always welcome! :+1:

[Stan-vw]

My suggestion would be to split this into 2 tickets:

1. Make a new ticket for the issue that it's not clear that some items in the left hand side menu are dropdowns (needs design research on best way to visualise)
2. Reword this ticket into just the issue regarding the scrollbar of the dropdowns of the left hand side menu not being height-aligned with the size of the browser window, leading to a dual scrollbar (doesn't require any design work, and can be planned relatively quickly would be my estimate)

Would that work?

[sgiehl]

A dropdown for menu item will be shown for items that are created by the customer, but only if they exceed a certain amount. This is currently the case for things like dashboards, goals, custom reports,... So every improvement around this is actually global, as it will also affect all other menu items. The dropdown currently has a max-height of 400, so if there are too many items a scrollbar might be shown.

Splitting this issue sound fine to me. But we need a clean decision on both, what exactly we should change. Simply aligning the dropdown height with the browser window might not work if e.g. the dropdown is displayed at the end and there is not enough space for it. In that case we might need a minimum height maybe and maybe need to scoll the element to view port, or instead open the dropdown upwards instead.

[Stan-vw]

Agree with your points @sgiehl , which is why I suggest to split them:

1. the dropdown needs design research because it'll impact things globally, and it's a Matomo specific design
2. you're correct that there's some more nuance than I made it out to be, but there's existing best practices around this. In case the dev team needs some help we can certainly involve design, my guess would be it isn't a larger piece of design work, such as checking if Matomo wide we should expect any downsides.