0023326: preventing data loss - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0023326	mantisbt	other	public	2017-09-07 10:45	2017-09-20 17:01

Reporter	helfy022	Assigned To	atrol
Priority	high	Severity	minor	Reproducibility	N/A
Status	closed	Resolution	no change required
Product Version	2.5.1

Summary	0023326: preventing data loss
Description	Hello, 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. Thanks, Ryan.
Tags	No tags attached.

atrol 2017-09-07 11:18 developer ~0057638	The issue has been reported often by users There are various discussions on the MantisBT bug-tracker that touch on this topic Please provide issue numbers for that.

helfy022 2017-09-07 11:32 reporter ~0057639	Hi Atrol, 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: https://www.mantisbt.org/bugs/view.php?id=12492 https://www.mantisbt.org/bugs/view.php?id=3729 https://www.mantisbt.org/bugs/view.php?id=13246 https://www.mantisbt.org/bugs/view.php?id=11693 https://www.mantisbt.org/forums/viewtopic.php?f=2&t=11450 Thanks, Ryan.

atrol 2017-09-07 11:45 developer ~0057641	Is there anything that should be added to http://mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.troubleshooting.errors.2800 ?

helfy022 2017-09-07 12:09 reporter ~0057642	Hi Atrol, 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? Thanks again, Ryan.

atrol 2017-09-10 06:33 developer ~0057654	some users have reported success in preventing the issue by increasing the "Refresh Delay" user preference Does it stand to reason that such an update would indeed help with the data loss issue? I tried decreasing "Refresh Delay" to reproduce the issue, but didn't succeed. So adding a hint in admin guide might just confuse users.

helfy022 2017-09-11 09:42 reporter ~0057678	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. Ryan.