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

Outdent records changed nodes in the reversed order #5980

Closed
bmblb opened this issue Jan 18, 2023 · 2 comments
Closed

Outdent records changed nodes in the reversed order #5980

bmblb opened this issue Jan 18, 2023 · 2 comments
Assignees
Labels
bug Something isn't working resolved Fixed but not yet released (available in the nightly builds)
Milestone

Comments

@bmblb
Copy link

bmblb commented Jan 18, 2023

To reproduce outdent several sublings at once and see project.changes array. You will notice tasks in the updated array are in the reverse order. Problem occurs when another project is applying this list of changes, it will add nodes in the reversed order and can calculate different WBS (unless we sync orderedParentIndex field)

@bmblb bmblb self-assigned this Jan 18, 2023
@emilschutte emilschutte assigned emilschutte and unassigned bmblb Jun 15, 2023
@emilschutte emilschutte added this to the 5.4.2 milestone Jul 14, 2023
@emilschutte
Copy link

Important note: the fix merged above requires that you configure forceWbsOrderForChanges : true on your TaskStore.

@emilschutte
Copy link

See also #7135.

@SergeyMaltsev SergeyMaltsev added resolved Fixed but not yet released (available in the nightly builds) bug Something isn't working and removed feature request labels Jul 26, 2023
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

3 participants