-
Notifications
You must be signed in to change notification settings - Fork 66
Dynamic fields lose unsaved values on work item update #3951
Comments
It is absolutely NOT okay to discard the entered data! |
@rgarg1 if the user has edited any field in the quick preview panel and has not committed to it or saved it, the moment they perform an action that calls for the closing of the panel, a warning should appear asking them to commit to the change or discard it. |
@rgarg1, I believe this issue is closed or addressed from the UX side. If yes, you can remove UX labels. @Veethika, @AshishDurgude, @sunilmalagi, @sdash-redhat, would you like to capture this UX recommendation as part of UX standards in our design wiki? |
Done @muruGanesan |
thanks @rgarg1 |
This is still an issue. |
I consider this a high priority because of Data loss. |
@openshiftio/uxd-team please provide a visual of the warning. |
I don't think we need a warning as much as auto-save. When you leave the field it should save the information. |
+1 to @joshuawilson |
@Veethika @serenamarie125 please comment ^^ |
@Veethika is the UX ready for this? |
@divyanshiGupta for now, you can just auto-save it. That is the normal use of a form. |
@joshuawilson okay 👍 |
@Veethika if we implement auto save, do you still want to have an ok button along side the cancel? In this case now the ok button does the same as navigating away. Will users expect that their input is saved if they don't press ok? Maybe they enter a value and think it will be discarded if they don't press ok and are surprised it gets saved. |
Btw I think the original issue was that editing a separate field causes data lose in an unsaved field. This is indeed a bug. The user should have the ability to go back to the first field and save or discard the value. Instead the value was thrown away unexpectedly. It had nothing to do with closing the panel. |
@christianvogt Right, my solution swayed towards the opening and closing the panel which should be addressed in a different story altogether. For this issue, the work-item should not be reloaded everytime a user begins to edit a field. |
@Veethika @joshuawilson What we do if the user chooses to navigate away is a separate issue. But when editing the same issue, we are losing data. If we fix this problem, do we still need an auto save? Or a warning about navigating away? |
@christianvogt can you close #4643 as a duplicate? |
@Veethika what is the suggested UX? |
Unassigning myself as I am not working on this issue currently as I have some other tasks on priority. |
A question for the UX team....
Consider the following scenario:
So, is it okay to lose data in the dynamic fields on an update, or the data must be retained is the question.
The text was updated successfully, but these errors were encountered: