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

[59539] Migrate scheduling mode and lags #17235

Draft
wants to merge 9 commits into
base: dev
Choose a base branch
from

Conversation

cbliard
Copy link
Member

@cbliard cbliard commented Nov 20, 2024

Ticket

https://community.openproject.org/wp/59539

(Part of https://community.openproject.org/wp/42388)

What are you trying to accomplish?

Implement new automatic scheduling mode

Migration:

  • All non-successor work packages are switched to manual scheduling mode
  • All successor work packages are switched to automatic scheduling mode
  • All parent are switched to which mode???
  • Closest follows relations have lag adjusted to keep the same dates for successors

Feature implementation:

  • TBD

Screenshots

TBD

What approach did you choose and why?

TBD

Merge checklist

  • Added/updated tests
  • Added/updated documentation in Lookbook (patterns, previews, etc)
  • Tested major browsers (Chrome, Firefox, Edge, ...)

@cbliard cbliard marked this pull request as draft November 20, 2024 11:43
@cbliard cbliard force-pushed the feature/42388-new-automatic-scheduling-mode branch from 3b388c0 to ccbaae4 Compare November 20, 2024 13:41
https://community.openproject.org/wp/42388

Scheduling mode is now manual by default. Only successors will be in
automatic mode.

WIP
@cbliard cbliard force-pushed the feature/42388-new-automatic-scheduling-mode branch from ccbaae4 to 30d07e7 Compare November 22, 2024 09:30
To preserve dates, a lag is set for follows relations when both the
predecessor and the follower have dates.
`lag` is the number of _working_ days between predecessor and successor
dates.
The rule is: it never switches from manual to automatic scheduling mode.
It only switches from automatic to manual, and only if keeping automatic
is not possible because it would mean losing the dates.

The code and specs have been updated to reflect this.

A materialized view is used to reuse the data in multiple different
queries.
@cbliard cbliard force-pushed the feature/42388-new-automatic-scheduling-mode branch from 46a22d1 to 391d65b Compare November 27, 2024 11:18
@cbliard cbliard changed the title [42388] Migrate scheduling mode and lags [59539] Migrate scheduling mode and lags Nov 27, 2024
The column is also non-nullable now.
The tests have to be adapted to explicitly set scheduling mode to
automatic for followers (which used to be the default).

Also, add a new column type for days counting in the table helpers. It
controls the `ignore_non_working_days` attribute
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

1 participant