-
Suggestion
-
Resolution: Fixed
-
None
-
None
-
2
-
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
OK, so you've seen this one before. I believe JRA-36670 contains the most thorough discussion of the issue.
I'm raising this as a bug because that is exactly how the behavior feels to the end user.
Let me be clear. I get that the UX books say that every element should be aligned to the user's expectation, and that behavior should be consistent throughout the system. That's well and good, and to Krzysztof Piwowar's point in the above-mentioned ticket.
In this case, your feature (quickly back out of a text box or close modal by pressing escape, without any confirm prompt) clearly and painfully violates the following user expectations:
- That data (changes) will not be lost. This is a completely reasonable expectation.
- To cite a clear example of this...If I'm using MS Outlook and I click to write a new email, a new window pops up. If I have made no changes, pressing 'esc' will quickly close the window.
- However, if I have made any changes, I am PROMPTED whether I want to close the window or not.
- A feature should not frustrate users or unnecessarily cause them additional time and effort.
- Judging by the number of bug tickets raised for this issue, and my own experiences, it's clear that this feature is causing frustration and additional investment of time.
I type quickly, and sometimes, things happen that break my flow. For example:
- If I bring up a right-click menu, I may instinctively press escape to close it out. Instead, I lose all my work. In fact, I just did this before deciding to write this ticket.
- Behavior is not consistent between the "create ticket" modal and the edit ticket page.
- ie if I click out of the edit box on the edit ticket page, my work is saved. However, if I click out of a text box in the create ticket modal, my work is NOT saved. Sometimes, while working quickly, I forget that the behavior is not the same.
- Thus, if for any reason I press escape while the modal is active, I lose all my work.
- If another app pops up while I'm writing, I may tap 'esc' a few times (again, instinctively
). This will cause me to lose all my unsaved work in the ticket.
So, either:
a) This is a bad feature that should be removed.
or, more likely,
b) JIRA is missing a feature to check for changes, and prompt the user to confirm changes if they have been made.
The latter would take all the pain away, while presenting the user with a predictable and efficient experience.
I sincerely hope that this feedback can help your product team improve the feature set. JIRA is an incredible piece of software that I use for most of my day. I can't imagine life without it. However, I'm one lost chunk of work away from doing all of my writing in Word or a 3rd party editor, and only copying it to the ticket once it's complete. This would be a pain, but far better than losing my work on a semi-regular basis.
- is related to
-
JRASERVER-36670 Hitting Escape key while editing issue description loses contents
-
- Closed
-
-
-
- Gathering Impact
-
-
- Closed
- relates to
-
- Closed
-
JSRTE-585 You do not have permission to view this issue
- mentioned in
-
Page Loading...
-
-
-
-
-
[JRASERVER-61439] Prompt user before clearing changed values when ESC key is pressed during inline edit
Looks like this is broken again or has never actually been fixed. I'm using JIRA Server 8.22.0 here and if I accidentally push Esc when editing my very long custom field in a transition dialog box, the dialog gets immediately closed without any prompt and I lose everything that I've typed so far into that custom field. Without any prompt whatsoever. That's frustrating to say the least, and all the issues describing that behavior are 'CLOSED' here as if they were fixed back in some 2018. It's five years later, but nothing is actually fixed. I've just lost 15 minutes of typing. Twice. I'm really mad now to say the least...
Hi everyone,
After careful consideration, we've decided to prioritize making ESC key behaviour consistent across description and comment edit operations on Jira Server roadmap. Your recent comments made it clear that our recent RTE improvements need a follow up regarding this element.
We hope to start development after our current projects are completed. Expect to hear an update on our progress within the next 6 months.
To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
Jira Server Product Management
I never used RichText editor.
Plain text editor is convenient, all got used to him.
+1 for
"if I bring up a right-click menu, I may instinctively press escape to close it out. Instead, I lose all my work."
This feels like a big issue and has nothing to do with proper behaviour of a software that wants to help users to be more efficient. Please fix.
This shouldn`t need to be discussed, it`s just a bothering behaviour that would be a bug in a non-web-environment.
Retyping my groomed story 
Matthew Nelson
added a comment - Ah! My Jira instance does have the rich text editor enabled, but I personally prefer the text editor. (I'm a frequent user of Markdown and GitHub issues, so I'm comfortable with text markup languages.)
Matthew Nelson
added a comment - Ah! My Jira instance does have the rich text editor enabled, but I personally prefer the text editor. (I'm a frequent user of Markdown and GitHub issues, so I'm comfortable with text markup languages.) Interesting - my company only uses the plain text editor. They might have gotten tired of the weird formatting in pasted text.
Perhaps edit the subject to append "(plain text editor only)", and put a few line feeds and an "Editor's note: The Visual Editor is not affected by this" at the end of the description? But I'd be disinclined to call it fixed as long as many people are still using the plain text editor.
Hi,
After reading the comment above I see the issue only reproduces when Rich Text Editor is not in use.
Regarding the inline issue edit on the Agile backlog in issue details pane, I can see that Esc would not discard the edit. Other actions would not discard the edit information either: clicking anywhere outside of the are would just save the edit (when visual editor is used).
So far I see that using the Visual Editor addresses the mentioned cases - as it prevents losing the text typed: the Esc button does not trigger editor to quit. As the feature is implemented since Jira 7.3.0 I am tempted to resolve the suggestion with the correspondent fix version.. Do you see any concerns with such resolution?
Cheers,
Ignat Alexeyenko
Jira Bugmaster.
- Jira 7.2.6
- during editing of description of issue.
We don't use Rich text editor becuse it not useful in some cases.
Matthew Nelson
added a comment - Ignat, I just reproduced this on Jira 7.5.1. I experience this issue primarily in the agile backlog detail pane and on the issue page itself. I presume both of these are examples of "inline edit."
Matthew Nelson
added a comment - Ignat, I just reproduced this on Jira 7.5.1. I experience this issue primarily in the agile backlog detail pane and on the issue page itself. I presume both of these are examples of "inline edit." 
I our JiraCloud version 1001.0.0-SNAPSHOT (using Safari), Esc key deletes your entire comment.