View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0023326||mantisbt||other||public||2017-09-07 10:45||2017-09-20 17:01|
|Status||closed||Resolution||no change required|
|Summary||0023326: preventing data loss|
What are the recommendations for preventing form data loss due to timeout, duplicate form submission, etc.? The issue has been reported often by users, and we are looking for the best approaches (be they MantisBT config-, browser-, and/or preference-specific) to address the problem. We are using MantisBT core version 2.5.1 on a secure server (https), and are eager to apply any necessary changes that do not involve touching the core MantisBT configuration suite.
There are various discussions on the MantisBT bug-tracker that touch on this topic. Hoping to consolidate here the potential options, suggestions, etc. that will best combat the issue.
|Tags||No tags attached.|
|related to||0012492||closed||atrol||Complete input get lost when timeout or not filling all required fields (when using ssl/https)|
|related to||0003729||closed||thraxisp||When using the browser's back button, the form is cleared out.|
|related to||0013246||closed||dregad||APPLICATION ERROR #2800 when submitting notes|
|related to||0011693||closed||dregad||Timeout : lost of project configuration|
Please provide issue numbers for that.
Thanks for the quick response.
The users about which I speak are those using our MantisBT bug-tracker setup.
Examples of issues on the the www.mantisbt.org bug-tracker and forums to which I'm referring are as follows:
Is there anything that should be added to http://mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.troubleshooting.errors.2800 ?
This is exactly the consolidated commentary for which I was looking. Thanks!
One follow-up question - some users have reported success in preventing the issue by increasing the "Refresh Delay" user preference (e.g., up to 9999 minutes). Does it stand to reason that such an update would indeed help with the data loss issue? If so, is it worth noting in the referenced section of the admin guide?
I tried decreasing "Refresh Delay" to reproduce the issue, but didn't succeed.
Thanks, Atrol. I had assumed increasing the "Refresh Delay" would decrease the likelihood of a user interacting with a timeout (and, thus, corresponding data loss). Based on your feedback, we will not necessarily recommend that users increase the "Refresh Delay" in the hopes of preventing the data loss event.
Assuming I'm understanding everything correctly, please feel free to close this bug.
Thanks again for your feedback.