Project

General

Profile

Bug #47714

Feature #47072: mgr/dashboard: Usability Improvements

mgr/dashboard: Implement an expert setting

Added by Stephan Müller 5 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
dashboard/usability
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

To simplify forms implement an expert setting that if disabled hides not mandatory fields in the forms as the first step.

How should it look like?
Maybe on the top right an expert slider on the form and on the top panel. As it will have impact on what a users sees in the future.

Tip before getting to deep into the implementation please ask in the stand up if that's path we want to go down.

History

#1 Updated by Stephan Müller 5 months ago

  • Description updated (diff)

#2 Updated by Lenz Grimmer 5 months ago

  • Tags set to usability
  • Parent task set to #47072

#3 Updated by Ernesto Puerta 5 months ago

Great! I remember Patrick & I already discussed this previously, but I don't find any tracker. I'd suggest to rename this as 'simple mode' (as the 'expert' is the current one, right?). We discussed about having simple-medium-advanced/expert, but I think having just a simple-expert toggle would make things easier.

#4 Updated by Nizamudeen A 5 months ago

  • Assignee set to Nizamudeen A

#5 Updated by Nizamudeen A 4 months ago

  • Assignee deleted (Nizamudeen A)

#6 Updated by Patrick Seidensal about 2 months ago

I don't think we should implement this as a setting to be configured on each form separately. And ultimately this is a setting that prevents users from making mistakes, not only to hide possibly complicated or dangerous settings. I'd also vote for making this the default setting. Users should see the simple and easy interface first, which prevents them from making crucial mistakes and should need to change a setting to see more complex and potentially dangerous settings.

That also means that I wouldn't necessary hide all settings that are not mandatory, but those whore are rarely used, hard to understand and/or potentially dangerous. What exactly that means would need to be determined.

Also available in: Atom PDF