Switching between Overall Settings and Parameters tabs in Deployment Configuration loses changes

Bug #1626787 reported by Dan Trainor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Switching between Overall Settings and Parameters tabs in the Deployment Configuration dialogue results in changes being made between these two tabs without clicking "Save Changes" to be lost.

Changes should be persistent in the dialogue between switching tabs and committed as one change set when "Save Changes" is pressed, permanently saving the changes.

To demonstrate this, click on the Edit Configuration button. Then, change any option from its default state. Switch to the Parameters tab, then back to the Overall Settings tab. Observe that changes to the Overall Settings tab are changed.

Tags: ui
Revision history for this message
Jason E. Rist (jason-rist) wrote :

Workaround: save in Overall Settings before switching.

Changed in tripleo:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Jiri Tomasek (jtomasek) wrote :

The selection made in Overall Settings drive the list of parameters in Parameters tab. Overall Settings needs to reflect actual configuration state, if GUI persisted unsaved changes there, we'd need to resolve another problem - how to let user know that he made changes there but did not save them. I am not sure we want to go this far with how we complicate things.

We're hitting the UX problem which is introduced by including those 2 views as into a single modal.

Suggestions on the solution are highly welcome

Jiri Tomasek (jtomasek)
Changed in tripleo:
assignee: nobody → Jiri Tomasek (jtomasek)
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
assignee: Jiri Tomasek (jtomasek) → nobody
importance: High → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.