Filter Bucket Configuration migration issues #651

Closed
opened 2025-11-01 21:01:10 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @Mattiam2 on GitHub (Oct 1, 2025).

Description

After migrating from v0.24.6 to v1.0.0-rc2 the projects don't load if at least one projects has a kanban view with bucket configuration set to "Filter".

Image

Debugging I discovered that in v0.24.6 the bucket_configuration column in project_views table was in this form:
[{"title":"Done","filter":"done = True"}]
While in v1.0.0 it's now in this form:
[{"title":"Done","filter":{"s":"","sort_by":null,"order_by":null,"filter":"done = true","filter_include_nulls":false}}]

The migration 20250323212553 needs to update also the bucket_configuration column in the same way it does with the filter.

If I have time I'll do a pull request.

Vikunja Version

v1.0.0-rc2

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @Mattiam2 on GitHub (Oct 1, 2025). ### Description After migrating from v0.24.6 to v1.0.0-rc2 the projects don't load if at least one projects has a kanban view with bucket configuration set to "Filter". <img width="761" height="189" alt="Image" src="https://github.com/user-attachments/assets/4ec0966c-b9e0-4028-bc4d-06a6b9749ca3" /> Debugging I discovered that in v0.24.6 the _bucket_configuration_ column in _project_views_ table was in this form: `[{"title":"Done","filter":"done = True"}]` While in v1.0.0 it's now in this form: `[{"title":"Done","filter":{"s":"","sort_by":null,"order_by":null,"filter":"done = true","filter_include_nulls":false}}]` The migration 20250323212553 needs to update also the bucket_configuration column in the same way it does with the filter. If I have time I'll do a pull request. ### Vikunja Version v1.0.0-rc2 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
Author
Owner

@Mattiam2 commented on GitHub (Oct 1, 2025):

Update, in migration 20241119115012 this conversion was done but only if bucket_configuration_mode = 2.
If someone in the past put a filter and then decided to revert back to "Manual bucket configuration", the "bucket_configuration" field would stay filled. That's why the issue occures.

@Mattiam2 commented on GitHub (Oct 1, 2025): Update, in migration 20241119115012 this conversion was done but only if bucket_configuration_mode = 2. If someone in the past put a filter and then decided to revert back to "Manual bucket configuration", the "bucket_configuration" field would stay filled. That's why the issue occures.
Author
Owner

@kolaente commented on GitHub (Oct 1, 2025):

Fixed in 67ebd876d3, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Oct 1, 2025): Fixed in https://github.com/go-vikunja/vikunja/commit/67ebd876d3630555917943e23c39dc93939b54ca, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#651