Prompt for confirm when clicking Cancel button on comment

[Babis Paravalos]

I think this used to exist in previous JIRA version. In the new UI, if you hit the cancel button the comment is removed. And because the Cancel button is very close to the Submit button, often you can miss click and instead of hitting the Submit button you click the Cancel button.

Imagine the frustration (and decrease in productivity) when you have spent 30 minutes to write a huge comment with tech details and formatting etc, and accidentally you hit the Cancel button instead of the Submit button.

I think that the user should be prompted to confirm if they want to cancel their comment, eg. some message like 'are you sure that you want to cancel the comment all text will be erased'.

I believe there will be  a few more people that this has happened to them at least once, and is not just me.

Please discuss this internally and apply this change, it's going to save many peoples' time from re writing accidentally deleted comments.

[Olivier Michel]

1 million times yes. no documentation for our server migration happening tonight. I am not writing that again.

Please add a prompt or even move the Cancel button across? They're so dam close.

[briank]

This had just happened to me. Was writing a comment but accidentally clicked cancel and had to rewrite the whole thing again. Would really like this UI issue to be fixed to avoid similar problems in the future.

[Ahmed Mutwakil]

I couldn't agree more with any of the above. Legitimately they're way too close. Why not simply put them on opposing sides? Or at least prompt when clicking cancel and there's any content. 

[Richard Quadling]

Why are changes just not continually saved? Either to local storage or the ticket on the live site.

[Babis Paravalos]

Hey Atlassian, has anyone noticed this discussion? Interested in changing this or not really?It shouldn't be such a hard change to implement!

If you have doubts, then maybe ask a UX expert to confirm that this is problematic and not very practical?

[Mike Cains]

I have lost far too many test reports to a slightly misplaced mouse click on the cancel button.

Lost a whole days work today, no way can I just make up all that data and replace everything I already typed out. 

[Jonathan Inglis]

I've just come here to see if I was the only one with this issue, quite clearly not. 

I mean there is some form of detection of unsaved content because it literally states 'unsaved changes' so why not add a confirmation on the cancel. 

Basically now I am resorting to using Google Docs to type things up just on the off chance I hit 'cancel' by mistake. 

I mean.... it's pretty poor UX / UI

[JM Sánchez]

Just happened to me! terrible, terrible interface :/

[JM Sánchez]

A tip until/if ever Atlassian decides to fix this: type Cmd+Enter to save the comment without using the mouse. You can always delete the comment later if you mistakingly save it.

[Richard Quadling]

The human version of auto-save!

[Gabor Peter]

Yes please, happened to me and my colleagues many times, a simple popup asking or an undo button to revert to edit would be great.

[Eric Smith]

I just lost another lengthy comment because of this. Please please please make this standard. 'Cancel' is too close to 'Save'. Why is a Cancel button even needed? Just delete your post.

It's ironic Jira does an excellent job saving an incomplete post in case you accidentally navigate away, but will without hesitation delete a comment if you accidentally click 'Cancel'

[Anthony P.]

> Imagine the frustration (and decrease in productivity) when you have spent 30 minutes to write a huge comment with tech details and formatting etc, and accidentally you hit the Cancel button instead of the Submit button.

Don't have to imagine, just happened to me and I stumbled upon here when I was looking for a way to recover what I did, in case I missed something.

[Eric Smith]

Sorry for your loss 😢. It's the worst