Feature #40690
closed
Story #82206: list module enhancements/bugfixes
List-view: Mass-setting a value
0%
Description
Situation:
List-view, only one specific record-type selected.
In front of the column-title there is already an edit-icon to mass-edit all records. That however loads a list of all records with the possibility to change each one separately.
Proposal:
Have an easy way to set one new value for all of them.
One way to do it would be to simply use JavaScript on the client and a new icon near the new value for the first record like "copy to all other records". This would then also allow to choose a new value there, copy that to all other records but before saving still modify individual rows again.
Please note that this JavaScript-solution would need to take into account the field-type (select, text, ...).
Updated by Mathias Schreiber almost 10 years ago
- Priority changed from Should have to Could have
- Target version set to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 8 LTS
Updated by Riccardo De Contardi over 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Riccardo De Contardi over 4 years ago
- Related to Feature #26139: un-/hide multiple records with one click added
Updated by Simon Schaufelberger over 3 years ago
- Related to Feature #94906: Introduce multi record selection to filelist added
Updated by Christian Kuhn over 2 years ago
- Status changed from New to Closed
Hey.
I hope it's ok to close here for now. Apart from the fact that nothing happened in the issue for quite a few years, mass editing on single fields is already possible using the list module, and the approach does work, even though it's a rather seldom use case.
I think a "set a single field of multiple rows to one specific value" would require a more drastic change of the editing interfaces and can only happen with a broader refactoring.
This issue here won't help us a such with this task and should be instead encapsulated in a series of issues in case a broader list module refactoring and/or change of strategies takes place.