Content
View differences
Updated by Niels Lindenthal about 1 year ago
* General structure and basics
* Stages are renamed to "Phases"
* Gates are renamed to "Phase gates"
* Two gates always require a phase in between. A gate can not precedes another gate. There is no gate without a corresponding phase.
* Automatic scheduling
* Changing the finish date of a phase/gate triggers the rescheduling of succeeding phases/gates.
* In case finish dates of phases/gates are empty (no duration) they are not set by changing the dates of predecessors. Dates can be deleted from phases/ gates.
* Active phases/gates are sequential. The sequence is defined by the order of the phases/gates in the administration.
* In case a phase/gate is inactive in a project, the next active phase/gate is considered to be the successor. Multiple inactive phases/gates can be ignored that way.
* Phases/gates not active in the project are not scheduled. In case a phase/gate is inactivated, it keeps its dates.
* Activating and deactivating a stage/gate does not trigger a rescheduling.
* Only working days can be selected. Non-working days are excluding from rescheduling. Finish days can not be non-working days.
* Date picker
* Clicking on a phase/gate opens a date picker. There is an icon next to the date to indicate if a phase/gate can be edited.
* Phase that follow another phase/gates are read only.
* Activity
* The activity page includes the changes to phases/gates
* Work package
* A work package can be optionally assigned to a phase/gate (single-select).
* The work package type form configuration also includes the attributes (phase/gate).
* The assignment of work packages to a phase/gate does not impact scheduling.
* Work packages can be filtered for their phases/gates.
* Permissions
* There is a separate project permission to activate and deactivate project phases/gates.
* There is a separate project permission to edit phases/gates.
* Stages are renamed to "Phases"
* Gates are renamed to "Phase gates"
* Two gates always require a phase in between. A gate can not precedes another gate. There is no gate without a corresponding phase.
* Automatic scheduling
* Changing the finish date of a phase/gate triggers the rescheduling of succeeding phases/gates.
* In case finish dates of phases/gates are empty (no duration) they are not set by changing the dates of predecessors. Dates can be deleted from phases/ gates.
* Active phases/gates are sequential. The sequence is defined by the order of the phases/gates in the administration.
* In case a phase/gate is inactive in a project, the next active phase/gate is considered to be the successor. Multiple inactive phases/gates can be ignored that way.
* Phases/gates not active in the project are not scheduled. In case a phase/gate is inactivated, it keeps its dates.
* Activating and deactivating a stage/gate does not trigger a rescheduling.
* Only working days can be selected. Non-working days are excluding from rescheduling. Finish days can not be non-working days.
* Date picker
* Clicking on a phase/gate opens a date picker. There is an icon next to the date to indicate if a phase/gate can be edited.
* Phase that follow another phase/gates are read only.
* Activity
* The activity page includes the changes to phases/gates
* Work package
* A work package can be optionally assigned to a phase/gate (single-select).
* The work package type form configuration also includes the attributes (phase/gate).
* The assignment of work packages to a phase/gate does not impact scheduling.
* Work packages can be filtered for their phases/gates.
* Permissions
* There is a separate project permission to activate and deactivate project phases/gates.
* There is a separate project permission to edit phases/gates.