Project

General

Profile

Actions

Feature #37571

closed

mgr/dashboard: Highlight RBD configuration options in add/edit form

Added by Patrick Seidensal over 5 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Component - RBD
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

When editing or creating the RBD configuration of a pool or image, it is not clear which setting will be submitted if the user decided not to set a value, after he changed the input field and it hence has been marked as "dirty" (unless he immediately clicks on the reset button next to that field).

If the user edits a configuration and it has previously been set to "0", the user won't know that this is not the default value provided but the local value set for the image/pool unless the field is highlighted or otherwise marked as manually set.

By highlighting the changed input field, the user could simply use the "reset" button to revert those changes.


Related issues 2 (1 open1 closed)

Related to Dashboard - Feature #37936: mgr/dashboard: Inherited values aren't shown in add/edit of an RBD imageNew

Actions
Follows Dashboard - Feature #36191: mgr/dashboard: Add support for managing RBD QoSResolvedPatrick Seidensal

Actions
Actions #1

Updated by Patrick Seidensal over 5 years ago

  • Due date set to 09/27/2018
  • Start date changed from 12/07/2018 to 09/27/2018
  • Follows Feature #36191: mgr/dashboard: Add support for managing RBD QoS added
Actions #2

Updated by Patrick Seidensal over 5 years ago

  • Due date deleted (09/27/2018)
  • Start date deleted (09/27/2018)
Actions #3

Updated by Laura Paduano over 5 years ago

Patrick Nawracay wrote:

When editing or creating the RBD configuration of a pool or image, it is not clear which setting will be submitted if the user decided not to set a value, after he changed the input field and it hence has been marked as "dirty" (unless he immediately clicks on the reset button next to that field).

If the user edits a configuration and it has previously been set to "0", the user won't know that this is not the default value provided but the local value set for the image/pool unless the field is highlighted or otherwise marked as manually set.

When editing the QoS options of an RBD image and it actually was configured to inherit option X from the pool, this value is currently not being reflected in the edit-mode of RBDs - Patrick and I discussed about how to make this more clear within the UI - an option would be to display the actual (inherited) value below or above the input field. Another option would be to display the inherited value within the input field with the explicit hint that this value is the one inherited from the pool.

By highlighting the changed input field, the user could simply use the "reset" button to revert those changes.

Actions #4

Updated by Patrick Seidensal over 5 years ago

  • Related to Feature #37936: mgr/dashboard: Inherited values aren't shown in add/edit of an RBD image added
Actions #5

Updated by Patrick Seidensal over 5 years ago

  • Status changed from New to Rejected

Issue #37936 will also resolve the problem described in this issue.

Actions #6

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 139 to Component - RBD
Actions

Also available in: Atom PDF