Stability of text in fields on bug report page after page reload both on website and test now app
planned
Zainab
i want to make a suggestion and I will be happy it test io can implement it, i notice that 'the bug report page on browser website and test now app' got reload if user leave the page for 3 minutes plus after write all the bug report fields with a lot of information, it stress sometimes to start and rewriting information again. I will be happy if test is cancelled implement the feature or make the bug reporting page, information stable eve7n after the page reload like all text inside [title, steps, actual results and expected results fields] not get cleared after user inputed words finish and page reload.
It will just be exactly or something like filling Google form that information will still stable unless user cleared it by themselves.
Tetiana Yezerska
planned
Tetiana Yezerska
Merged in a post:
To prevent the page from closing suddenly and causing losses while writing a bug report.
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.
Tetiana Yezerska
Merged in a post:
Save drafts / auto save
o
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
Tetiana Yezerska
Hey! Thanks for the suggestion! This problem is shared with developers, will keep you updated on this.
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.
ted
o
oppixp
ted: This is also a good idea but does not help if the browser crashes.