Bug 1027246 - [Usability] RFE: data should not be lost after form is sent and request failed on server side
Summary: [Usability] RFE: data should not be lost after form is sent and request faile...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console - UX
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: EAP 6.4.0
Assignee: Catherine Robson
QA Contact: Pavel Jelinek
eap-docs
URL:
Whiteboard: Usability
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 12:19 UTC by Jakub Cechacek
Modified: 2019-08-19 12:49 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:49:38 UTC
Type: Task
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-298 0 Minor Open Data should not be lost after form is sent and request failed on server side 2018-04-08 11:32:10 UTC

Description Jakub Cechacek 2013-11-06 12:19:32 UTC
For some actions, it is possible to lose data entered into form / wizard. This generally occurs whenever there is a failure on server side after sending a form containing invalid data (due to missing client-side validation or no possibility to validate users input). 

An example of such action would be a creation of new datasource with existing name. Regardless the error, "New Datasource" wizard is closed after clicking on "Done" button in the last step and everything is lost.

Action as "closing wizard" or switching form back to view mode should happen only after receiving server response with no errors.

Comment 1 Harald Pehl 2013-11-06 19:53:40 UTC
Postponed to EAP 6.3

Comment 2 Heiko Braun 2014-07-09 11:38:17 UTC
In agreement with Catherine we've decided that UX issues will be tracked separately.

Comment 3 Jakub Cechacek 2014-07-21 06:21:39 UTC
Issue moved under the UX component. 

Also moved to 6.4 as this issue is still valid for 6.3. Use ack flags to decide whether we want to go through with it or not.

Comment 4 Catherine Robson 2014-08-01 17:34:16 UTC
UX to bundle this into the wizard design w/ validation & checking work for EAP 7.

Comment 5 Heiko Braun 2014-08-25 13:27:31 UTC
 I't s not a bug nor a UX issue: The data is send to the server and then refreshed. Regardless if the operation fails or not, the most recent data is fetched. I would close this as rejected.


Note You need to log in before you can comment on or make changes to this bug.