This duplicates JRA-14031, which is Planned for 4.0.

A variation on this is: click on the Comment operation, start entering a comment, then navigate using the browser arrows. If you navigate back, the comment edit page is no longer there, you just get the original page and you've lost whatever you put into the comment field. As this involves data loss, I think it should minimally have an alert telling you you are about to lose what you've typed in.

As an additional comment on this issue, I feel Atlassian needs to review the hotkeys. Some very common hotkeys which leverage "typical" (IE, Moz, FFox, etc) menu hotkeys are getting overridden by JIRA and may be causing more negative value than necessary.

An example just happened to me. I religeously use ctrl+e then a or l to mimick Edit-Select All clicks. This has lost several very lengthy issue dialogs (add comment) for me since in JIRA that puts the issue in edit mode with no recourse to recover the text that was being typed.

Since JIRA is operating inside a browser container I would think a good improvement would be to honor any known hotkeys which browsers offer to the user.

I get the "opportunity" to do issue edits because I am in the administrators role for our JIRA implementation and not all users may experience this issue if the edit link does not exist.

There are some othe rplaces this would be very useful. Specifically the bulk change page.

When we do bug scrubs, we'll usually bulk change all of them, going through each and checking boxes for the ones we want to postpone. This can take an hour. One false move and boom! The browser goes to another page and you lose all that info. Same thing for later steps - if you go to another page before you've committed the bulk changes, all those checks could be lost.

Please add a yes/no dialog when the user tries to navigate away from any of these pages.