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

Can NOT reorder fields on the screen designer in screen configurations

XMLWordPrintable

      Dragging a field within a tab on the screen editor, removes it from the view

      Steps to reproduce:
      1. Login as an admin and navigate to Configure Screen page of any of the screen.
      2. Drag a field within the tab.

      Notice that the dragged field disappears. A page refresh brings it back. This however renders the drag-drop functionality ineffective.

      There is NO way to reorder fields on a screen due to this bug

      See attached video

      Workaround
      Download add-on attached to this issue (jira-project-config-plugin-6.1.2-fix-for-JRA-35586.jar) and install it on your JIRA 6.1.2 instance to get this bug fixed.

        1. drag_field.swf
          388 kB
        2. jira-project-config-plugin-6.1.2-fix-for-JRA-35586.jar
          583 kB

            [JRASERVER-35586] Can NOT reorder fields on the screen designer in screen configurations

            aidanwojtas added a comment -

            Doesn't work on iPad running iOS 8.3 in Safari or Chrome

            aidanwojtas added a comment - Doesn't work on iPad running iOS 8.3 in Safari or Chrome

            Will added a comment -

            Awesome, thanks, Eric!

            Will added a comment - Awesome, thanks, Eric!

            Eric Dalgliesh added a comment -

            Hi will-gcm, This regressed in 6.2 and I've just fixed it today. Barring unforeseen circumstances, it should be available in JIRA 6.2.2, about 3 weeks from now. We have been tracking the 6.2 version of this at JRA-36964.

            Regards,
            Eric

            Eric Dalgliesh added a comment - Hi will-gcm , This regressed in 6.2 and I've just fixed it today. Barring unforeseen circumstances, it should be available in JIRA 6.2.2, about 3 weeks from now. We have been tracking the 6.2 version of this at JRA-36964 . Regards, Eric

            Will added a comment - - edited

            Ok, we have people in our office still having this issue with 6.2. I tried installing this fix, but it won't "take" in 6.2. When I try in both Chrome and Firefox, it works for me, but others using Chrome are having problems. Actually, I did get it to do this once a while back (might have been an outdated chrome), and this is what I saw in the console: 

            An exception has occurred in https://hidingourdomain.com/s/d41d8cd98f00b204e9800998ecf8427e/en_US-5s1zp2-1988229788/6252/54/8/_/download/superbatch/js/batch.js at 268 : Uncaught TypeError: Object #<Object> has no method 'dragStart' batch.js:2

            Will added a comment - - edited Ok, we have people in our office still having this issue with 6.2. I tried installing this fix, but it won't "take" in 6.2. When I try in both Chrome and Firefox, it works for me, but others using Chrome are having problems. Actually, I did get it to do this once a while back (might have been an outdated chrome), and this is what I saw in the console: An exception has occurred in https: //hidingourdomain.com/s/d41d8cd98f00b204e9800998ecf8427e/en_US-5s1zp2-1988229788/6252/54/8/_/download/superbatch/js/batch.js at 268 : Uncaught TypeError: Object #< Object > has no method 'dragStart' batch.js:2

            Dave C added a comment -

            will-gcm, yes this is fixed in 6.1.3 onwards which means it will be fixed in 6.2.

            Dave C added a comment - will-gcm , yes this is fixed in 6.1.3 onwards which means it will be fixed in 6.2.

            Will added a comment -

            so... 6.2 is out now... does this work with it?

            Will added a comment - so... 6.2 is out now... does this work with it?

            Leon Wright added a comment - - edited

            Upgraded our DEV/UAT instances to 6.1.3, all looks good now. Thanks.

            Leon Wright added a comment - - edited Upgraded our DEV/UAT instances to 6.1.3, all looks good now. Thanks.

            Wojciech Urbanski (Inactive) added a comment -

            Great question bmcdevit. You only need to upgrade and everything should be just fine.

            Wojciech Urbanski (Inactive) added a comment - Great question bmcdevit . You only need to upgrade and everything should be just fine.

            Brendan McDevitt added a comment -

            Josh,

            If we installed the work-around plugin, but would like to upgrade to 6.1.3, do we have to uninstall the plugin first?

            Thanks,
            Brendan

            Brendan McDevitt added a comment - Josh, If we installed the work-around plugin, but would like to upgrade to 6.1.3, do we have to uninstall the plugin first? Thanks, Brendan

            Josh Devenny added a comment -

            Hi Everyone - this has been fixed in JIRA 6.1.3, which is now available.

            https://www.atlassian.com/software/jira/download

            For those experiencing trouble with the plugin that we shipped as a workaround, please upgrade to 6.1.3.

            Josh

            Josh Devenny added a comment - Hi Everyone - this has been fixed in JIRA 6.1.3, which is now available. https://www.atlassian.com/software/jira/download For those experiencing trouble with the plugin that we shipped as a workaround, please upgrade to 6.1.3. Josh

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              kshekhar Kiran (Inactive)
              Affected customers:
              15 This affects my team
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: