Loading
Because changing forty tasks one at a time is unbearable, so people export to a spreadsheet, edit there, and re-import — losing anything the export did not carry.
The table view is a grid of tasks and their fields, built for editing many rows at once.
Columns are fields and cells are editable, with multi-select and fill-down. Every change goes through the same rules as a single edit, so dependencies still move and history is still recorded.
A phase slips a fortnight. Selecting its tasks and shifting dates in one action moves them together, with dependent work following, rather than forty edits and a missed one.
It will not let you bypass validation. A bulk edit that would create a circular dependency or an impossible date fails on those rows and says which.
It edits the same fields as anywhere else — owner, status, dates, estimates, labels — and bulk changes are recorded as such.
Into matching columns, yes, with a preview before it applies.
The change is recorded as one action and can be undone as one.
Yes, and saved as a view.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.