-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
None
I have noticed several issues in the database across several projects that are related to the browsers "Back" button. That is because data and state information is not saved prior to actual user execution. Any user inputed data, queries, attachment selections, etc will all be destroyed if the back button is pressed. This is extremely frustrating for me because I have a mouse with fwd. and back buttons near my thumb, and I frequently press them accidentally. I am new to Jira, but have alrady had about 3 incidents that have caused me to loose detailed bug reports. This costs the company money, and wasted time every incident. It just seems prudent to prevent this from occuring by either saving the data in a temprorary location, or by warning the user if data has been submitted, and the back button is pressed. There has got to be a way to either prevent this, or reduce the risk by warning users before it happens. This issue is too frequently submitted in Jira, and Confluence to ignore.
- duplicates
-
JRASERVER-14031 Form data lost when using back and forward web browser buttons
-
- Closed
-
[JRASERVER-10858] Back Button Destroys Data
Larry Masinter
added a comment - I think this behavior is tied to the HTTP-EQUIV directives in the standardHeader macro (shared problem with Confluence). See
http://jira.atlassian.com/browse/CONF-7457
Larry Masinter
added a comment - I think this behavior is tied to the HTTP-EQUIV directives in the standardHeader macro (shared problem with Confluence). See
http://jira.atlassian.com/browse/CONF-7457
Byron L. Spires
added a comment - An Example Scenario is this:
1.) Open New Issue and start filling in the form (Title, Build Found, Description, etc.)
2.) Lots of detail is added to the report, but not submitted.
3.) Browsers "Back" button, or other navigation button is pressed.
4.) Data is lost forever.
5.) Browse fwd, or back to the New Issue page, and all data is gone.
6.) This could also occur if a link was clicked that opens another page, or if submission of data failed for some reason.
Since users spend a lot of time submitting detailed bug reports, it really hurts if your data gets lost. It kind of encourages users to submit less detail in their reports just to get the issue in the database.
Ideally it would be nice if once you opened up a new issue all data entered would be saved in a temp location or cookie every x number of bytes entered, or every x seconds. Then you could provide 2 submission options:
1.) "Open New Issue" - that provides a clean slate.
2.) "Open New Using Cached Data" - that opens a new issue, but uses the last entry as a template.
This would also be helpful if submitting multiple issues that share some of the same information.
If you cannot implement this new feature, then at the very least you could prompt the user warning them that they will loose data if they continue, but this will not stop the data from being overwritten in the case where a shortcut, or link caused a new page to display in that window.
Byron L. Spires
added a comment - An Example Scenario is this:
1.) Open New Issue and start filling in the form (Title, Build Found, Description, etc.)
2.) Lots of detail is added to the report, but not submitted.
3.) Browsers "Back" button, or other navigation button is pressed.
4.) Data is lost forever.
5.) Browse fwd, or back to the New Issue page, and all data is gone.
6.) This could also occur if a link was clicked that opens another page, or if submission of data failed for some reason.
Since users spend a lot of time submitting detailed bug reports, it really hurts if your data gets lost. It kind of encourages users to submit less detail in their reports just to get the issue in the database.
Ideally it would be nice if once you opened up a new issue all data entered would be saved in a temp location or cookie every x number of bytes entered, or every x seconds. Then you could provide 2 submission options:
1.) "Open New Issue" - that provides a clean slate.
2.) "Open New Using Cached Data" - that opens a new issue, but uses the last entry as a template.
This would also be helpful if submitting multiple issues that share some of the same information.
If you cannot implement this new feature, then at the very least you could prompt the user warning them that they will loose data if they continue, but this will not stop the data from being overwritten in the case where a shortcut, or link caused a new page to display in that window. Byron,
Can you perhaps give me some more information about what you want saved? It sounds like you would mostly want the description box on the edit issue page to be saved?
How about if you had a javascript alert popup if you have changed anything, and you navigate away? Would that work for you?
This duplicates
JRA-14031, which is actually Planned for 4.0. (Yay!)