Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-18515

After renaming a version, users cannot drag & drop issues

      Issue Summary

      After a user renames a version in the board's backlog, dragging and dropping issues no longer works. Instead, text is selected

      Environment

      Jira Software Cloud, a (classic) Scrum project with some versions.

      Steps to Reproduce

      1. Navigate to the backlogs section of a board. Open the Versions panel
      2. On one of the versions, click the down-arrow and then click Edit name. Rename the version.
      3. Attempt to drag&drop an issue either to a version or just to rank it higher

      Expected Results

      The user can drag&drop issues from the backlog

      Actual Results

      When attempting to drag&drop, the cursor selects text from the page

      Workaround

      After renaming the version, refreshing the browser page fixes the issue

            [JSWCLOUD-18515] After renaming a version, users cannot drag & drop issues

            Dylan made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Long Term Backlog [ 12073 ] New: Closed [ 6 ]
            Dylan made changes -
            Labels Original: front-end stale-bulk-close202010 New: front-end stale-bulk-close202010 stale-bulk-close202204

            Dylan added a comment -

            Hi all,

            Thank you for raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.

            To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Dylan added a comment - Hi all, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
            Bugfix Automation Bot made changes -
            Support reference count Original: 1 New: 2
            Suraj Goel made changes -
            Status Original: Needs Triage [ 10030 ] New: Long Term Backlog [ 12073 ]
            Russ Gould [Atlassian] (Inactive) made changes -
            Resolution Original: Timed out [ 10 ]
            Status Original: Closed [ 6 ] New: Needs Triage [ 10030 ]
            Dylan made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Long Term Backlog [ 12073 ] New: Closed [ 6 ]
            Dylan made changes -
            Labels Original: front-end New: front-end stale-bulk-close202010

            Dylan added a comment -

            Hi all,

            Thank you for raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.

            To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Dylan added a comment - Hi all, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
            Pedro Tacla Yamada made changes -
            Status Original: Gathering Impact [ 12072 ] New: Long Term Backlog [ 12073 ]

              Unassigned Unassigned
              clionte Claudiu Lionte (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: