Details

      Description

      I work on a mac and my browser supports emacs key bindings for editing in a browser's text box, but JIRA overrides these with keyboard shortcuts. For example I pree Ctrl-a to go to the beginning of the line in a text box and JIRA takes me to a new page to add an attachment to the issue.

      This is very annoying. I do not use JIRA keyboard shortcuts and I have no interest in using them, and yet they cripple my standard text editing style.

        Issue Links

          Activity

          Hide
          Kai B. added a comment -

          I add my vote.

          But it should be possible to select which shortcut should be turned off. We have problems here with the backspace. If you are to fill out the fields to create an issue, the focus is not in a text field and you press by mistake the backspace - then everything is gone and you have to enter everthing again....

          Cheers,
          Irene

          Show
          Kai B. added a comment - I add my vote. But it should be possible to select which shortcut should be turned off. We have problems here with the backspace. If you are to fill out the fields to create an issue, the focus is not in a text field and you press by mistake the backspace - then everything is gone and you have to enter everthing again.... Cheers, Irene
          Hide
          Neal Applebaum added a comment -

          Kai,

          I've been bitten by that awful backspace functionality too. But I don't see how JIRA can help -that's a browser thing.

          Show
          Neal Applebaum added a comment - Kai, I've been bitten by that awful backspace functionality too. But I don't see how JIRA can help -that's a browser thing.
          Hide
          Simon added a comment -

          I have lost a lot of work because of the access key activation functionality.

          The biggest issue is that if you have entered work into form fields for an issue, there is potentially important information in the form fields. The current shortcut key functionality ignores data entered into the form fields and vectors to the access key page. So if you had any data on the previous page, it is lost.

          The simplest suggestion would be to have the shortcut key activation function check to see if any of the fields have been modified before moving off to the shortcut link. This way if there is volatile data that is about to be thrown away, the user could be warned before this occurs.

          It would be nice to be able to disable the shortcuts, but just not having the data evaporate would be a great improvement.

          Also, the emacs key bindings come from the readline library and they are generally supported across all Mac Os X apps due to the fact that it is essentially a unix platform.

          Show
          Simon added a comment - I have lost a lot of work because of the access key activation functionality. The biggest issue is that if you have entered work into form fields for an issue, there is potentially important information in the form fields. The current shortcut key functionality ignores data entered into the form fields and vectors to the access key page. So if you had any data on the previous page, it is lost. The simplest suggestion would be to have the shortcut key activation function check to see if any of the fields have been modified before moving off to the shortcut link. This way if there is volatile data that is about to be thrown away, the user could be warned before this occurs. It would be nice to be able to disable the shortcuts, but just not having the data evaporate would be a great improvement. Also, the emacs key bindings come from the readline library and they are generally supported across all Mac Os X apps due to the fact that it is essentially a unix platform.
          Hide
          Simon added a comment -

          If you use Firefox, there is a config setting in the "about:config" called accesskeycauseactivation where you can apparently disable access key activation. However, due to a bug in Firefox (see: https://bugzilla.mozilla.org/show_bug.cgi?id=319929) this setting needs to be reset on every Firefox restart.

          You can get the same functionality (or disabling of functionality) by installing the greasemonkey plugin (https://addons.mozilla.org/en-US/firefox/addon/748) and creating an override for the accessKey property on all the page elements. This seems to do the trick and has the added benefit that greasemonkey lets you select the pages that this applies to.

          Show
          Simon added a comment - If you use Firefox, there is a config setting in the "about:config" called accesskeycauseactivation where you can apparently disable access key activation. However, due to a bug in Firefox (see: https://bugzilla.mozilla.org/show_bug.cgi?id=319929 ) this setting needs to be reset on every Firefox restart. You can get the same functionality (or disabling of functionality) by installing the greasemonkey plugin ( https://addons.mozilla.org/en-US/firefox/addon/748 ) and creating an override for the accessKey property on all the page elements. This seems to do the trick and has the added benefit that greasemonkey lets you select the pages that this applies to.
          Hide
          Simon added a comment -

          Adding a greasemonkey user script for disabling access key properties for a page.

          Show
          Simon added a comment - Adding a greasemonkey user script for disabling access key properties for a page.
          Hide
          Simon added a comment -

          To use the greasemonkey user script do the following:
          1. Install the greasemonkey plugin.
          2. Click on the above accesskey_disable.user.js link. (Greasemonkey will ask if you want to install it. Click install)
          3. Open: Tools->Greasemonkey->Manage User Scripts.
          4. Add to the included pages specification to cover the sites you want it to be excuted on.

          You should find that the access key activation is now disabled for the sites matching the spec, and the default emacs/readline bindings will work.

          Hope this helps.
          [n.b These instructions are for firefox 2.0.0.8, greasemonkey 0.7.20070607.0 on MacOsX 10.4.10]

          Show
          Simon added a comment - To use the greasemonkey user script do the following: 1. Install the greasemonkey plugin. 2. Click on the above accesskey_disable.user.js link. (Greasemonkey will ask if you want to install it. Click install) 3. Open: Tools->Greasemonkey->Manage User Scripts. 4. Add to the included pages specification to cover the sites you want it to be excuted on. You should find that the access key activation is now disabled for the sites matching the spec, and the default emacs/readline bindings will work. Hope this helps. [n.b These instructions are for firefox 2.0.0.8, greasemonkey 0.7.20070607.0 on MacOsX 10.4.10]
          Hide
          ray hixson added a comment -

          That works - thank you very much!

          Show
          ray hixson added a comment - That works - thank you very much!
          Hide
          Jeff Turner added a comment -

          I think we need a better grasp of the extent of the problem. Which browsers and operating systems are involved? Does this affect Firefox 2 (where shortcuts on linux now require shift+alt+key)?

          Show
          Jeff Turner added a comment - I think we need a better grasp of the extent of the problem. Which browsers and operating systems are involved? Does this affect Firefox 2 (where shortcuts on linux now require shift+alt+key)?
          Hide
          Andrew Wagner added a comment -

          I have this problem on os x 10.4.11, Safari version 3.0.4 (523.12.2) and Firefox/2.0.0.14.

          The workaround of installing the greasemonkey Firefox plugin and the above script worked for me, and I'm happy to use FireFox until a better solution is found.

          1. Install the greasemonkey Firefox plugin:
          https://addons.mozilla.org/en-US/firefox/addon/748

          2. Install the accesskey_disable.user.js script by opening the link below:
          http://jira.atlassian.com/secure/attachment/22576/accesskey_disable.user.js

          3. If desired, edit which sites this applies to in Tools->Greasemonkey->Manage User Scripts.

          Thanks!
          Drew

          Show
          Andrew Wagner added a comment - I have this problem on os x 10.4.11, Safari version 3.0.4 (523.12.2) and Firefox/2.0.0.14. The workaround of installing the greasemonkey Firefox plugin and the above script worked for me, and I'm happy to use FireFox until a better solution is found. 1. Install the greasemonkey Firefox plugin: https://addons.mozilla.org/en-US/firefox/addon/748 2. Install the accesskey_disable.user.js script by opening the link below: http://jira.atlassian.com/secure/attachment/22576/accesskey_disable.user.js 3. If desired, edit which sites this applies to in Tools->Greasemonkey->Manage User Scripts. Thanks! Drew
          Hide
          Andrew Wagner added a comment -

          Also, I would encourage you to move this from "Minor New Feature" to something more pressing; it is a design flaw that causes unexpected data loss any time a mac user tries to use standard line editing key shortcuts while editing text. Thanks again! Drew

          Show
          Andrew Wagner added a comment - Also, I would encourage you to move this from "Minor New Feature" to something more pressing; it is a design flaw that causes unexpected data loss any time a mac user tries to use standard line editing key shortcuts while editing text. Thanks again! Drew
          Hide
          Vick Khera added a comment -

          This is clearly a major UI flaw that needs to be addressed. Of the many UI issues that annoy in Jira, this one is right at the very top of my list.

          Show
          Vick Khera added a comment - This is clearly a major UI flaw that needs to be addressed. Of the many UI issues that annoy in Jira, this one is right at the very top of my list.
          Hide
          David Findlay added a comment -

          I too find this extremely irritating. I will be in the middle of entering a big long comment and I'll press CTRL-E to go to the end of the line, and instead Jira will go and edit the issue instead.

          Show
          David Findlay added a comment - I too find this extremely irritating. I will be in the middle of entering a big long comment and I'll press CTRL-E to go to the end of the line, and instead Jira will go and edit the issue instead.
          Hide
          Peter Oberauer added a comment -

          JIRA's keyboard shortcuts cause my comments to be lost during editing, or accidentally/prematurely submitted, on Firefox 3.0.4 on Mac OS X 10.5.5 !

          I would simply like all of these keyboard shortcuts turned off, as a per-user or per-site preference - I don't mind as long as they are off.

          The following keyboard shortcuts for editing text, predate JIRA by a very very long way, and at least the ones below should be considered sacred:
          http://www.gnu.org/software/bash/manual/bashref.html#Commands-For-Moving

          They work perfectly well in textareas and input fields in Firefox on any normal website, and are familiar shortcuts in bash, Emacs. They all function in TextEdit and other standard-respecting Mac apps too.
          C-a beginning of line
          C-e end of line
          C-f forward char
          C-b backward char
          C-d delete char
          C-k kill the text from point to the end of the line.

          JIRA disrespects many of these. Inconsistently, Ctrl+S submits any form in JIRA, while on the docs page below, you have, more logically and less destructively, the accesskey="s" for the search form.
          http://www.atlassian.com/software/jira/docs/v3.13/shortcuts.html

          accesskeys like 's' to change the focus to another form field on the page are nice, "shortcuts" that take you to other pages and lose your edits, while pressing formerly functional keys like Ctrl-a, are really not!

          Thanks everyone for the greasemonkey workarounds, but I really want a fix where JIRA doesn't disrespect well established, standard, functional keyboard shortcuts.

          This is a Major PITA, not a Minor one as prioritised. Thanks.

          Show
          Peter Oberauer added a comment - JIRA's keyboard shortcuts cause my comments to be lost during editing, or accidentally/prematurely submitted, on Firefox 3.0.4 on Mac OS X 10.5.5 ! I would simply like all of these keyboard shortcuts turned off, as a per-user or per-site preference - I don't mind as long as they are off. The following keyboard shortcuts for editing text, predate JIRA by a very very long way, and at least the ones below should be considered sacred: http://www.gnu.org/software/bash/manual/bashref.html#Commands-For-Moving They work perfectly well in textareas and input fields in Firefox on any normal website, and are familiar shortcuts in bash, Emacs. They all function in TextEdit and other standard-respecting Mac apps too. C-a beginning of line C-e end of line C-f forward char C-b backward char C-d delete char C-k kill the text from point to the end of the line. JIRA disrespects many of these. Inconsistently, Ctrl+S submits any form in JIRA, while on the docs page below, you have, more logically and less destructively, the accesskey="s" for the search form. http://www.atlassian.com/software/jira/docs/v3.13/shortcuts.html accesskeys like 's' to change the focus to another form field on the page are nice, "shortcuts" that take you to other pages and lose your edits, while pressing formerly functional keys like Ctrl-a, are really not! Thanks everyone for the greasemonkey workarounds, but I really want a fix where JIRA doesn't disrespect well established, standard, functional keyboard shortcuts. This is a Major PITA, not a Minor one as prioritised. Thanks.
          Hide
          ray hixson added a comment -

          I agree with the commenter below that it's a major - I was recently trying out a new browser that didn't have greasemonkey capability and it bit me in the ass again - losing my edits...

          Show
          ray hixson added a comment - I agree with the commenter below that it's a major - I was recently trying out a new browser that didn't have greasemonkey capability and it bit me in the ass again - losing my edits...
          Hide
          sensui added a comment -

          We got problems in Windows & IE, since the default keyboard shortcut of switch japanese imput method is just Alt + `, Many guys lost their edits by use it for in jira, it means "CANCEL".

          Show
          sensui added a comment - We got problems in Windows & IE, since the default keyboard shortcut of switch japanese imput method is just Alt + `, Many guys lost their edits by use it for in jira, it means "CANCEL".
          Hide
          Howard Look added a comment -

          Adding my vote to please, please, please fix this. It is killing me. 20+ years of Emacs muscle memory is killing me within Jira, especially when every other text editor and type-in on a Mac supports it. Please at least provide a way to disable the keyboard shortcuts for us Safari users who can't use the Firefox workaround. Thanks!

          Show
          Howard Look added a comment - Adding my vote to please, please, please fix this. It is killing me. 20+ years of Emacs muscle memory is killing me within Jira, especially when every other text editor and type-in on a Mac supports it. Please at least provide a way to disable the keyboard shortcuts for us Safari users who can't use the Firefox workaround. Thanks!
          Hide
          Rick Schultz added a comment -

          The description says it all: the effects of this bug are crippling. How can this bug have been open for so long? Are all the Atlassian developers running Greasemonkey?

          Show
          Rick Schultz added a comment - The description says it all: the effects of this bug are crippling. How can this bug have been open for so long? Are all the Atlassian developers running Greasemonkey?
          Hide
          Chris Gibbs added a comment - - edited

          I'd just like to throw another vote in on this. The keystrokes that JIRA is overriding are practically a "standard" on any *nix system (including os x and solaris).

          As Simon mentioned, they come from the GNU readline library: http://en.wikipedia.org/wiki/GNU_readline

          JIRA is great, don't get me wrong - I love it. But not being able to disable this is a serious bug.

          Show
          Chris Gibbs added a comment - - edited I'd just like to throw another vote in on this. The keystrokes that JIRA is overriding are practically a "standard" on any *nix system (including os x and solaris). As Simon mentioned, they come from the GNU readline library: http://en.wikipedia.org/wiki/GNU_readline JIRA is great, don't get me wrong - I love it. But not being able to disable this is a serious bug.
          Hide
          Robert Sfeir added a comment - - edited

          This keyboard shortcut stuff really gets in the way. I'm on OS X 10.6.3 using Chrome (dev build) and pressing a simple command + C to copy text off a page triggers the create issue link. This also happens in Safari on the same platform, so it's not like I'm using an unusual browser.

          You're interfering with standard shortcuts on an OS... this is just a bad idea... and clearly not tested well.

          Show
          Robert Sfeir added a comment - - edited This keyboard shortcut stuff really gets in the way. I'm on OS X 10.6.3 using Chrome (dev build) and pressing a simple command + C to copy text off a page triggers the create issue link. This also happens in Safari on the same platform, so it's not like I'm using an unusual browser. You're interfering with standard shortcuts on an OS... this is just a bad idea... and clearly not tested well.
          Hide
          Brett Ryan added a comment -

          I'm on OSX and not seen any problem, CMD+C works fine for copy, pressing `c' alone opens create issue.

          I think however it might be wise to disable shortcuts once anyone has a form open (comment, already creating new issue, etc...).

          Show
          Brett Ryan added a comment - I'm on OSX and not seen any problem, CMD+C works fine for copy, pressing `c' alone opens create issue. I think however it might be wise to disable shortcuts once anyone has a form open (comment, already creating new issue, etc...).
          Hide
          Mike Nowak added a comment -

          I see it happening in Mac OS X with Safari 4. Is there no way to turn off keyboard short cuts?

          Show
          Mike Nowak added a comment - I see it happening in Mac OS X with Safari 4. Is there no way to turn off keyboard short cuts?
          Hide
          Dave Flogeras added a comment -

          This is also particularly annoying for vim users. My fingers randomly press the escape key without my consent, and I found out today that I can easily lose all of my comment text this way. At least a "confirm" box would be helpful.

          Show
          Dave Flogeras added a comment - This is also particularly annoying for vim users. My fingers randomly press the escape key without my consent, and I found out today that I can easily lose all of my comment text this way. At least a "confirm" box would be helpful.
          Hide
          Roman Revyakin added a comment -

          I also vote to have at least a user control to turn those shortcuts off. Using Opera 10 here with the vimopera shortcuts. It is very annoying

          Show
          Roman Revyakin added a comment - I also vote to have at least a user control to turn those shortcuts off. Using Opera 10 here with the vimopera shortcuts. It is very annoying
          Hide
          Aaron Carlson added a comment -

          These keyboard shortcuts are non-standard and cause unexpected behavior most commonly of which is losing work and time. Since the likely reason for adding these shortcuts was to save time it should be obvious that there is a disconnect. I think the shortcuts need to be disable-able and moreover should be re-thought altogether.

          Show
          Aaron Carlson added a comment - These keyboard shortcuts are non-standard and cause unexpected behavior most commonly of which is losing work and time . Since the likely reason for adding these shortcuts was to save time it should be obvious that there is a disconnect. I think the shortcuts need to be disable-able and moreover should be re-thought altogether.
          Hide
          Chris Mountford [Atlassian] added a comment -

          This is fixed in a version of JIRA that will be shipped as 4.2. Please note the workaround attached to this issue.

          Show
          Chris Mountford [Atlassian] added a comment - This is fixed in a version of JIRA that will be shipped as 4.2. Please note the workaround attached to this issue.
          Hide
          Bernd Schatz added a comment -

          Where can i disable / modifiy this short-cuts ?
          When will this be fixed in confluence ?
          (We currently use 3.2.1_01 and <ctrl><k> still opens a windows for adding a link.

          Show
          Bernd Schatz added a comment - Where can i disable / modifiy this short-cuts ? When will this be fixed in confluence ? (We currently use 3.2.1_01 and <ctrl><k> still opens a windows for adding a link.

          Hi Bernd,

          When will this be fixed in confluence ?

          You've commented in the JIRA project, are you after CONF-21908 or CONF-7256?

          Cheers,
          Peter

          Show
          Peter Leschev [Atlassian] - Recovering JIRA Bugmaster added a comment - Hi Bernd, When will this be fixed in confluence ? You've commented in the JIRA project, are you after CONF-21908 or CONF-7256 ? Cheers, Peter
          Hide
          Trey Howard added a comment -

          As mentioned earlier, I find these annoying. I have no interest in using the shortcuts and often find that I have accidentally performed some operation because I started typing when I wasn't focused in an input field (or equivalent). Being able to turn them off would be fantastic. Thanks!

          Show
          Trey Howard added a comment - As mentioned earlier, I find these annoying. I have no interest in using the shortcuts and often find that I have accidentally performed some operation because I started typing when I wasn't focused in an input field (or equivalent). Being able to turn them off would be fantastic. Thanks!

            People

            • Assignee:
              Unassigned
              Reporter:
              ray hixson
            • Votes:
              18 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: