Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-39965

"Create Issue" should prompt before closing (on "Cancel" or Esc)

XMLWordPrintable

    • 0
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Some people on my team have commented recently that they've lost work, after spending time composing a long issue, in the dialog where I'm currently writing. (Seems like it's happened at least once to multiple people we know.) After it happened to me last week, I resolved to report this as a usability problem.

      You can reproduce this by imagining you've gathered a load of disparate information in the "Create Issue" Dialog (or actually do it) and accidentally click the "Cancel" link, or tap the Escape key. Bam! (dialog closes) Re-open. All your work's gone. Was there a prompt? Nope. (If there were a way to get it all back, that'd be great too!)

      Moreover, this behavior creates the need for the arcane "write-up your bug in and editor and then copy+paste" workflow, which is awfully painful. Please add a quick confirmation dialog! (or something equally small) Thanks!

            [JRASERVER-39965] "Create Issue" should prompt before closing (on "Cancel" or Esc)

            Eoin Payne added a comment -

            Eh, created in 2014.. still nothing?

            Eoin Payne added a comment - Eh, created in 2014.. still nothing?

            Flavio Lira added a comment -

            +1 please

            Flavio Lira added a comment - +1 please

            ambsw_technology added a comment - - edited

            +1 for Atlassian taking responsibility for the SERIOUS and NEGATIVE consequences of the decision to make Create Issue (and, with the right workflow, Edit Issue) modals. I'm in favor of suppressing Esc entirely, but this is also a valid option.

            • The root cause here is Atlassian's CHOICE to make the Create and Edit screens modals. If they're going to persist in this choice, they should also CHOOSE to make them as convenient as possible for users.
            • The number of people who accidentally click "Create" and are bummed by a non-functional Esc key will be... approximately zero. And for those that do, the inconvenience is trivial. The opposite is true for the clearly non-trivial number of people who have such a non-trivial problem with the current behavior that they spent the time to post the same issue on your forums.

            It may (though I disagree even on this point) make sense to maintain a consistent Esc behavior (even though they really haven't, https://jira.atlassian.com/browse/JRA-41814), but you need to FIX THE PRODUCT in some other way:

            • Create a "draft" ticket when content is included
            • Ask users to confirm the closure
            • Change the create button so it doesn't use a modal

            As far as I'm concerned, this is a big enough waste of employee time (let alone the annoyance factor!) that I'll be shopping for alternatives when I move on to my next startup. Jira may still prevail, but the last thing you want to do is give your existing customers a compelling reason to go shopping... and for such a stupid, trivial reason.

            ambsw_technology added a comment - - edited +1 for Atlassian taking responsibility for the SERIOUS and NEGATIVE consequences of the decision to make Create Issue (and, with the right workflow, Edit Issue) modals. I'm in favor of suppressing Esc entirely, but this is also a valid option. The root cause here is Atlassian's CHOICE to make the Create and Edit screens modals. If they're going to persist in this choice, they should also CHOOSE to make them as convenient as possible for users. The number of people who accidentally click "Create" and are bummed by a non-functional Esc key will be... approximately zero. And for those that do, the inconvenience is trivial. The opposite is true for the clearly non-trivial number of people who have such a non-trivial problem with the current behavior that they spent the time to post the same issue on your forums. It may (though I disagree even on this point) make sense to maintain a consistent Esc behavior (even though they really haven't, https://jira.atlassian.com/browse/JRA-41814 ), but you need to FIX THE PRODUCT in some other way: Create a "draft" ticket when content is included Ask users to confirm the closure Change the create button so it doesn't use a modal As far as I'm concerned, this is a big enough waste of employee time (let alone the annoyance factor!) that I'll be shopping for alternatives when I move on to my next startup. Jira may still prevail, but the last thing you want to do is give your existing customers a compelling reason to go shopping... and for such a stupid, trivial reason.

              Unassigned Unassigned
              804d0fe426cc Tor E Hagemann
              Votes:
              10 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: