SKETCH BOARD

Goal
Improve the UX for forms so that users are aware that the data will be lost if the project switcher is changed or if they hit cancel. Consider removing the switcher from the top of the forms and adding it as a field below.

Background
Users lose all data when navigating away from forms in the console.

If a user navigates away OR selects cancel when creating or modifying a workload / operand in either form or yaml view they lose all data filled in.

In addition, when the project/namespace is changed in a form, users are navigated back to the list view instead of changing the name space and continuing with the current edit/create form.

The complaint is the loss of data especially in the larger forms. How can we improve the UX so that users are aware that the data will be lost? Can we remove the switcher from forms to help prevent this and add it as a field below?

We should capture what the Dev perspective does today to deal with these issues. The Dev perspective may disable the selector in some forms. So if we did that, there might be a precedent. But we need to double check. Should we repeat their approach or is there a better way to handle this across the console?

Other ideas:
1) disable the project selector in form views and or
2) Display an “are you sure confirmation” after filling in a form and either cancel or navigate away from the dirty page.
3) Would removing the switcher from the top of the form to a field allow users to switch projects in context without losing the data?

There is an older story that captures some of this sentiment as well: https://issues.redhat.com/browse/PD-567