Content
View differences
Updated by Jens Ulferts over 1 year ago
**As** a project admin
**I want to** organize the project into dedicated stages and gates
**so that** it is easier to communicate about the step the project is in and what that means for the progress.
_Note: This is but the first in a number of features which will greatly increase the versatility of phases_
**Acceptance criteria**
* Create a feature flag for the feature hiding all traces of it.
* Seed a fixed set of phases and gate types (for both existing and new instances of OpenProject)
* Those phases and gate types are similar to work package types. They define which phases/gates exist in a project. Each project will then receive instances of those types (see below).
* Seeded phases:
* Initiating: #F7983A,
* Ready for Planning: #682D91,
* Planning: #F05823,
* Ready for Executing: #682D91,
* Executing: #EC038A,
* Ready for Closing: #682D91,
* Closing: #B1D13A
* The colors are newly created if they do not exist (in Administration -> Colors).
* The seeded phases and gates are internationalized (during seeding process, can not be changed later).
* Existing projects will not have the stages and gates enabled.
* New projects will not have the stages and gates enabled by default.
* The project overview page has an area called "Project lifecycle" in the sidepanel above the project attributes section which displays the dates configured for each stage/gate in the current project.
* Viewing the phases/gates requires a project permission.
* Name: View project phases and gates
* Pre-seeding: All project roles get this permission
* Migrations on existing installations: All project roles get this permission (since they are empty no data is leaked). This includes anonymous and non-members.
* In case all stages and gates are disabled in the project (##58163), the section is hidden.
* The area showing the phases/gates in the current project's overview page allows the user to modify the dates of each stage/gate.
* Modifying the dates of the phases/gates requires a project permission different from the view permission.
* Name: Edit project phases and gates (~~includes~~ requires view permission)
* Pre-seeding: The role project admin gets this permissions.
* Migrations on existing installations: All project roles that get this permission that have the permission "edit project".
* Phases and gates have an input field to modify their date (range).
* The user is supported when modifying the dates by the OpenProject date picker
* For gates, it is a single date date picker.
* For stages, it is the range date picker.
* A stage will either have no date set at all or both dates set. It cannot have only the start or the end date set.
* The start date of a stage has to be before the end date.
* The minimum length for a stage is one day: This means a stage can start and end on the same date.
* There is no maximum length for a stage.
* Having gaps between stages/gates is allowed.
* Stages cannot have overlapping dates. Gates can overlap the start/end date of a stage. But only exactly the start/end date. The date of a gate cannot be between a stage's dates.
* A gate's date can not be the same as another gate's date.
* The dates entered have to reflect the order configured for phases/gates in the administration.
* e.g. It is not possible to define the dates of the 'Initiating' phase to be after the dates of the 'Closing' phase. phase.
* Phases/gates of the child project limited are not limited by the dates in the parent project.
<br>
**Out of scope**
* Automatic scheduling for inserting the dates of stages and gates in the overview page.
* including maintaing a fixed lag
* Scheduling by insertion of a duration.
* Inheritance to sub projects
* Seeding of phases/gates for demo projects (##58303)
**Reference**
* The stages are [taken from PM2](https://www.pm2alliance.eu/wp-content/uploads/2024/02/pm%C2%B2-project-management-methodology-NO0523520ENN.pdf)
**Figma**
https://www.figma.com/design/4Z950sfYbceOqUN6sFV7Mr/Project-management%3A-Stages-and-Gates?node-id=1-10673&node-type=frame&t=cGwFE1QlfVr4tS33-0
**I want to** organize the project into dedicated stages and gates
**so that** it is easier to communicate about the step the project is in and what that means for the progress.
_Note: This is but the first in a number of features which will greatly increase the versatility of phases_
**Acceptance criteria**
* Create a feature flag for the feature hiding all traces of it.
* Seed a fixed set of phases and gate types (for both existing and new instances of OpenProject)
* Those phases and gate types are similar to work package types. They define which phases/gates exist in a project. Each project will then receive instances of those types (see below).
* Seeded phases:
* Initiating: #F7983A,
* Ready for Planning: #682D91,
* Planning: #F05823,
* Ready for Executing: #682D91,
* Executing: #EC038A,
* Ready for Closing: #682D91,
* Closing: #B1D13A
* The colors are newly created if they do not exist (in Administration -> Colors).
* The seeded phases and gates are internationalized (during seeding process, can not be changed later).
* Existing projects will not have the stages and gates enabled.
* New projects will not have the stages and gates enabled by default.
* The project overview page has an area called "Project lifecycle" in the sidepanel above the project attributes section which displays the dates configured for each stage/gate in the current project.
* Viewing the phases/gates requires a project permission.
* Name: View project phases and gates
* Pre-seeding: All project roles get this permission
* Migrations on existing installations: All project roles get this permission (since they are empty no data is leaked). This includes anonymous and non-members.
* In case all stages and gates are disabled in the project (##58163), the section is hidden.
* The area showing the phases/gates in the current project's overview page allows the user to modify the dates of each stage/gate.
* Modifying the dates of the phases/gates requires a project permission different from the view permission.
* Name: Edit project phases and gates (~~includes~~ requires view permission)
* Pre-seeding: The role project admin gets this permissions.
* Migrations on existing installations: All project roles that get this permission that have the permission "edit project".
* Phases and gates have an input field to modify their date (range).
* The user is supported when modifying the dates by the OpenProject date picker
* For gates, it is a single date date picker.
* For stages, it is the range date picker.
* A stage will either have no date set at all or both dates set. It cannot have only the start or the end date set.
* The start date of a stage has to be before the end date.
* The minimum length for a stage is one day: This means a stage can start and end on the same date.
* There is no maximum length for a stage.
* Having gaps between stages/gates is allowed.
* Stages cannot have overlapping dates. Gates can overlap the start/end date of a stage. But only exactly the start/end date. The date of a gate cannot be between a stage's dates.
* A gate's date can not be the same as another gate's date.
* The dates entered have to reflect the order configured for phases/gates in the administration.
* e.g. It is not possible to define the dates of the 'Initiating' phase to be after the dates of the 'Closing' phase.
* Phases/gates of the child project limited are not limited by the dates in the parent project.
<br>
**Out of scope**
* Automatic scheduling for inserting the dates of stages and gates in the overview page.
* including maintaing a fixed lag
* Scheduling by insertion of a duration.
* Inheritance to sub projects
* Seeding of phases/gates for demo projects (##58303)
**Reference**
* The stages are [taken from PM2](https://www.pm2alliance.eu/wp-content/uploads/2024/02/pm%C2%B2-project-management-methodology-NO0523520ENN.pdf)
**Figma**
https://www.figma.com/design/4Z950sfYbceOqUN6sFV7Mr/Project-management%3A-Stages-and-Gates?node-id=1-10673&node-type=frame&t=cGwFE1QlfVr4tS33-0