Repository navigation
[Bug]: Edit Tasks in Bulk does not work #5812
Description
Bug Summary
Edit tasks in bulk does not produce the expected result.
Description
The bulk edit functionality for tasks does not work when using Kanboard via the official Docker image. After selecting multiple tasks and attempting to edit them, no changes are applied.
Steps to Reproduce
Go to a project board
Go to list view
Select multiple tasks using checkboxes
Click on "Edit selected tasks" (bulk edit option)
Modify one or more fields (e.g., color)
Save changes
Expected Behavior
Selected tasks should be updated with the new values.
Actual Behavior
No changes are applied to the selected tasks after saving. No error message is displayed.
Version
v1.2.52
Database
tested with sqlite and postgres
PHP Version
8.4.19
Browser
Mozilla/5.0 (X11; Linux x86_64; rv:150.0) Gecko/20100101 Firefox/150.0
Operating System
Linux 7.0.0-15-generic
Relevant Logs or Error Output
Additional Context
Issue occurs consistently
Tested with multiple browsers
Unsure if this is specific to Docker setup or affects other installations
No plugins in use
Checklist
- I have searched existing issues to ensure this bug hasn't been reported before.
- I verified that the problem is not caused by a plugin. Please report the issue to the plugin author if applicable.
Activity
wilidgasoft commentedon Jun 14, 2026
Hi, I'd like to work on this bug as part of an open source contribution program with CODEPATH.
I'm planning to reproduce the issue locally, trace the regression between v1.2.48 and v1.2.52, and submit a fix. I'll comment here once I have a clear root cause before opening a PR.
Please let me know if there's anything specific to keep in mind or if this is already being looked at.
wilidgasoft commentedon Jun 14, 2026
Hi @rwc0888, I was able to reproduce the steps described. After investigation, the bulk edit form requires explicitly checking the checkbox next to each field (e.g., Color) to apply changes to that property. If no checkboxes are selected, no changes are applied — this appears to be intentional behavior, not a bug. Could the maintainer confirm if this is by design? If so, the form might benefit from clearer labeling so users understand they need to opt-in per field.