UX cleanup: group quick actions, Actions and Feature Commands?

I just wondered, what the community thinks about refactoring “quick actions”, “Actions”, “Feature Commands” combined into an “Actions” dropdown or a dedicated “Actions” tab?

Negatives:

Quick actions would be obscured, if moved to an “Actions” dropdown or would be obscured and require an additional click, if moved to an “Actions” tab.

Positives:

The div with class “controls” would look cleaner or possibility to make “object-meta-info-control collapsible-control” obsolete.

Balancing the “tabs primary-nav nav” div, that looks a bit anemic, with the service tab’s “content” div, that looks chaotic and overladen.

No more searching and scrolling for “Actions” and “Feature Commands”.

PS: I Also just noticed the duplication of functionality and danger (accidentally exposed passwords!) of “Action” inspect and the Source Tab in the IcingaDB.

2 Likes