Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-5617

Manage Rapid Boards throws Cannot bind new shortcut Exception

XMLWordPrintable

      When having GreenHopper 5.10.6 and Atlassian Developer Toolbox 1.2 enabled in JIRA, you get the following error when trying to Manage Rapid Boards:

      An exception occurred

      Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.
      Details

      Exception: Error: Cannot bind new shortcut "dt" due to conflict with existing shortcut "d"
      Resource: http://ttsupportvm.local:8511/jira511/s/en_USbj8ss5/772/3/1/_/download/superbatch/js/batch.js
      Line: 519

        1. exception.png
          exception.png
          45 kB

          Form Name

            [JSWSERVER-5617] Manage Rapid Boards throws Cannot bind new shortcut Exception

            Sorin Sbarnea added a comment -

            Where is the fix for Jira 5? We cannot upgrade to 6 until we do enough testing and Jira 5 is still supported.

            Sorin Sbarnea added a comment - Where is the fix for Jira 5? We cannot upgrade to 6 until we do enough testing and Jira 5 is still supported.

            jhinch (Atlassian) added a comment - - edited

            The fix for this issue didn't make it into 6.0.1 but did make it into 6.0.2. Sorry for the confusion

            jhinch (Atlassian) added a comment - - edited The fix for this issue didn't make it into 6.0.1 but did make it into 6.0.2 . Sorry for the confusion

            Theodore Tzidamis (Inactive) added a comment -

            I am sorry Dag,

            I was confused also. I reproduced locally and, indeed, I am getting the same error.

            I am reopening this for our Development Team to check.
            Thank you for your amazing dedication here.

            Theodore Tzidamis (Inactive) added a comment - I am sorry Dag, I was confused also. I reproduced locally and, indeed, I am getting the same error. I am reopening this for our Development Team to check. Thank you for your amazing dedication here.

            Dag Christensen added a comment - - edited

            Sorry, I still don't understand I just upgraded to Greenhopper 6.0.1, which is stated as fix version for this bug, and the first thing I saw when accessing greenhopper was the error message described above. Wasn't the bug supposed to be fixed in 6.0.1, the version I have installed now?

            Dag Christensen added a comment - - edited Sorry, I still don't understand I just upgraded to Greenhopper 6.0.1, which is stated as fix version for this bug, and the first thing I saw when accessing greenhopper was the error message described above. Wasn't the bug supposed to be fixed in 6.0.1, the version I have installed now?

            Theodore Tzidamis (Inactive) added a comment -

            Hi Dan,

            The purpose was to combine forces between this Bug and that KB that already existed. I apologize, the intention was not to give that impression but to help as many users as possible by letting them know that the bug fix is included in GreenHopper 6.0.1.

            Good job finding the workaround.

            Theodore Tzidamis (Inactive) added a comment - Hi Dan, The purpose was to combine forces between this Bug and that KB that already existed. I apologize, the intention was not to give that impression but to help as many users as possible by letting them know that the bug fix is included in GreenHopper 6.0.1. Good job finding the workaround.

            Dag Christensen added a comment -

            So the fix was to add a KB article with a workaround? I found the workaround before commenting here, but you give the impression the bug was fixed in 6.0.1.

            Dag Christensen added a comment - So the fix was to add a KB article with a workaround? I found the workaround before commenting here, but you give the impression the bug was fixed in 6.0.1.

            Theodore Tzidamis (Inactive) added a comment -

            There is this relevant KB for more info.

            Theodore Tzidamis (Inactive) added a comment - There is this relevant KB for more info.

            Dag Christensen added a comment - - edited

            I got this error in Jira 5.1.2 with Greenhopper 6.0.1. Disabling Atlassian Developer Toolbox fixed the issue.

            Dag Christensen added a comment - - edited I got this error in Jira 5.1.2 with Greenhopper 6.0.1. Disabling Atlassian Developer Toolbox fixed the issue.

            Shaun Clowes (Inactive) added a comment -

            This has already been spotted and fixed in 6.0.1 which will be released shortly.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - This has already been spotted and fixed in 6.0.1 which will be released shortly. Thanks, Shaun

              jhinch jhinch (Atlassian)
              ttzidamis Theodore Tzidamis (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: