Skip to content

Unexpected behaviour when deleting option A and naming option B with option A's value #12345

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

Open
ijreilly opened this issue May 28, 2025 · 2 comments
Assignees

Comments

@ijreilly
Copy link
Collaborator

Bug Description

options_issue.mov

spotted while reviewing this PR, comes from the way we filter options based on their values and not their ids while deciding on which options to remove.

@ijreilly
Copy link
Collaborator Author

@prastoin i think this is independent from what you mentionned about storing option ids instead of values in views, since it is unrelated to views. It's just the way we decided to do the filtering which can be updated now because in the place we do it we have access to both option id and value.

@prastoin
Copy link
Contributor

Yes indeed ! was thinking that you were iterating over a filtered view and not on an atomic kanban view

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🔖 Planned
Development

No branches or pull requests

2 participants