To prevent the page from closing suddenly and causing losses while writing a bug report. | Voters

To prevent the page from closing suddenly and causing losses while writing a bug report.

planned

Enes Örsel

When closing the tab or application on some sites, "Are you sure you want to close this tab without saving the written texts?" question should be added.

February 26, 2022

Tetiana Yezerska

Merged in a post:

Save drafts / auto save

oppixp

I lost complete bug descriptions when my browser crashed or I accidentally closed the tab. Please add the option to save a draft or auto save. If I finished the description I could commit the bug via a "Commit" or "Publish" button

February 26, 2024

Tetiana Yezerska

marked this post as

planned

Tetiana Yezerska

Hey! Thanks for the suggestion! This problem is shared with developers, will keep you updated on this.

Tetiana Yezerska

marked this post as

under review

Vichapol Chutviriyacharoen

Honestly between your app and mobile web, the latter is so much better and not automatically reloaded the app. Test.io bug report took a long time to complete, having to start all over again is a literal night mare.

Tetiana Yezerska

Merged in a post:

The tester should not be able to close the page until he have saved the bug

Александра Яковлева

On the create bug page, the user when he clicks to close the page or return to the previous one should receive a warning that the page contains unsaved data and the user must make a choice to close the page or remain on it and continue creating the bug.

This allows avoiding cases when the tester accidentally presses the button "Close tab" or "Return to the previous page" at the time when it creates a bug. In this case, the tester has to create a bug again. This warning will avoid such occurrences.

December 21, 2023

ted

http://feedback.test.io/testers/p/the-tester-should-not-be-able-to-close-the-page-until-he-have-saved-the-bug

oppixp

ted: This is also a good idea but does not help if the browser crashes.