Skip to content
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

Updated task not appearing when it now matches filter after adding dependency #8281

Closed
emilschutte opened this issue Jan 16, 2024 · 0 comments
Assignees
Labels
bug Something isn't working resolved Fixed but not yet released (available in the nightly builds)
Milestone

Comments

@emilschutte
Copy link

emilschutte commented Jan 16, 2024

When you have a filter in effect on the receiving client that depends on endDate, and a remote client drags a connection to make a dependency from task X to task Y, thereby shifting task Y later in time, so that it should now match the filter where it did not before, then when the receiving client applies those changes (applyProjectChanges), task Y does get its date changed correctly but its row does not appear in view, even though it now matches the filter. This is due to the filter operating on the old date value.

@emilschutte emilschutte self-assigned this Jan 16, 2024
@isglass isglass added the bug Something isn't working label Jan 25, 2024
@isglass isglass added this to the 5.6.6 milestone Jan 25, 2024
@isglass isglass added the resolved Fixed but not yet released (available in the nightly builds) label Jan 25, 2024
@isglass isglass reopened this Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working resolved Fixed but not yet released (available in the nightly builds)
Projects
None yet
Development

No branches or pull requests

2 participants