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

Available slot for startDate calculates wrong when non-working periods defined #7038

Closed
chuckn0rris opened this issue Jun 20, 2023 · 1 comment
Assignees
Labels
bug Something isn't working forum Issues from forum OEM OEM customer resolved Fixed but not yet released (available in the nightly builds)
Milestone

Comments

@chuckn0rris
Copy link

Forum post

Here
https://www.bryntum.com/products/schedulerpro/examples/resource-non-working-time/
If change day to next with forward arrow of dateField, new date will go to far forward and jump next available slot.
If click back arrow and forward arrow again, it will jump to another slot. If repeat back-forward, date will change again.

Screen.Recording.2023-06-20.at.13.33.46.mov
@chuckn0rris chuckn0rris added bug Something isn't working forum Issues from forum OEM OEM customer labels Jun 20, 2023
@canonic-epicure canonic-epicure self-assigned this Aug 1, 2023
@canonic-epicure
Copy link

So this happens because the StartDateField increments its value by "working" time. Also in that example hoursPerDay config of the project is set to 24. So it shifts the events over several days.

This seems to be unexpected for the user, should be changed to some other behavior may be?

@matsbryntse matsbryntse changed the title Available slot for startDate calculates srong when non-working periods defined Available slot for startDate calculates wrong when non-working periods defined Aug 9, 2023
@canonic-epicure canonic-epicure added ready for review Issue is fixed, the pull request is being reviewed in progress and removed in progress ready for review Issue is fixed, the pull request is being reviewed labels Aug 21, 2023
@isglass isglass added this to the 5.5.2 milestone Aug 23, 2023
@isglass isglass added resolved Fixed but not yet released (available in the nightly builds) and removed ready for review Issue is fixed, the pull request is being reviewed labels Aug 23, 2023
@canonic-epicure canonic-epicure modified the milestones: 5.5.2, 5.6.0-alpha-2 Aug 24, 2023
@SergeyMaltsev SergeyMaltsev modified the milestones: 5.6.0-alpha-2, 5.6.0 Oct 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 forum Issues from forum OEM OEM customer resolved Fixed but not yet released (available in the nightly builds)
Projects
None yet
Development

No branches or pull requests

4 participants