Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Impossible to choose several fields at the same time to drag and drop it (design forms by drag-and-drop) #27705

Closed
qgib opened this issue Sep 18, 2018 · 5 comments
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Forms High Priority Regression Something which used to work, but doesn't anymore

Comments

@qgib
Copy link
Contributor

qgib commented Sep 18, 2018

Author Name: Alain FERRATON (@FERRATON)
Original Redmine Issue: 19881
Affected QGIS version: 3.3(master)
Redmine category:forms


In versions prior to 3.0, it was possible to choose several fields at the same time to drag and drop them into the designer.
It is no longer possible in the new design

(It also lacks the field assignment button and the up and down buttons).

@qgib
Copy link
Contributor Author

qgib commented Sep 18, 2018

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 1
  • crashes_corrupts_data was configured as 0
  • version was configured as 3.3(master)
  • priority_id was changed from Normal to High
  • tracker_id was changed from 2 to 1

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Forms Regression Something which used to work, but doesn't anymore labels May 25, 2019
@troopa81
Copy link
Contributor

troopa81 commented Jun 24, 2019

Proposed PR #30364 for 3.4
Proposed PR #30365 for 3.6
3.8 is already corrected

@troopa81
Copy link
Contributor

So 3.6 is EOL and 3.4 PR has been merged, so this issue should be closed.

@nyalldawson @DelazJ Should'nt this issue automatically closed when PR has been merged? I did something wrong?

@DelazJ
Copy link
Contributor

DelazJ commented Jun 25, 2019

@troopa81 Nothing wrong. It's closed when the merged PR is against the default branch (aka master) which is not the case here. This one needs to be closed manually.

@troopa81
Copy link
Contributor

@DelazJ Thanks for the explanation.

@troopa81 troopa81 self-assigned this Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Forms High Priority Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

3 participants