**As** a project admin
**I want to** organize the project into dedicated stages
**so that** it is easier to communicate about the stage 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 stages_

**Acceptance criteria**

* Create a feature flag for the feature hiding all traces of it.

* Seed a fixed set of stage and gate types (for both existing and new instances of OpenProject)

* Those stage and gate types are similar to work package types. They define which stages/gates exist in a project. Each project will then receive instances of those types (see below)

* Begin of the insertionSeeded stages: Initiating: #F7983A (24 days), Planning: #F05823 (48 days), Executing: #EC038A (96 days), Closing: #B1D13A (24 days)End of the insertion Begin of the deletion \[open\] Which stages/gates are seeded? What color are they seeded with? Which order are they to be in.End of the deletion

* \[open\] Are they internationalized?

* The project overview page has an area which displays the dates configured for each stage/gate in the current project.

* Viewing the stages/gates requires a project permission.

* Begin of the insertionName: View project stages and gatesEnd of the insertion Begin of the deletion \[open\] What is the name of this permission?End of the deletion

* Begin of the insertionPre-seeding: All projectEnd of the insertion Begin of the deletion \[open\] Which of the preseededEnd of the deletion roles Begin of the insertionget this permissionEnd of the insertion Begin of the deletion receive the permission? Assumption - Project admin.End of the deletion

* Begin of the insertionMigrationsEnd of the insertion Begin of the deletion \[open\] Which of the existing roles receive the permissionEnd of the deletion on existing Begin of the insertioninstallations:End of the insertion Begin of the deletion instances? Assumption -End of the deletion All Begin of the insertionprojectEnd of the insertion roles Begin of the insertiongetEnd of the insertion Begin of the deletion having the 'edit project' permission.

* \[open\] Visualization ofEnd of the deletion this Begin of the insertionpermission (since they are empty no data is leaked)End of the insertion Begin of the deletion area. Assumption - The colors should also be displayed here.End of the deletion

* The area showing the stages/gates in the current project the dates of the stages can be modified.

* Modifying the dates of the stages/gates requires a project permission different from the view permission.

* Begin of the insertionName: Edit project stages and gates (includesEnd of the insertion Begin of the deletion \[Assumption\] Receiving the edit permission requires to also have theEnd of the deletion view Begin of the insertionpermission)End of the insertion Begin of the deletion permission.End of the deletion

* Begin of the insertionPre-seeding: The role project admin gets this permissionsEnd of the insertion Begin of the deletion \[open\] Which of the preseeded roles receive the permission? Assumption - Project admin.End of the deletion

* Begin of the insertionMigrationsEnd of the insertion Begin of the deletion \[open\] Which of the existing roles receive the permissionEnd of the deletion on existing Begin of the insertioninstallations:End of the insertion Begin of the deletion instances? Assumption -End of the deletion All Begin of the insertionprojectEnd of the insertion roles Begin of the insertionthat get this permission that haveEnd of the insertion Begin of the deletion havingEnd of the deletion the Begin of the insertionpermission "edit project".End of the insertion Begin of the deletion 'edit project' permission.End of the deletion

* Stages have two input fields for dates (start/end) while stages have one field.

* \[open\] It might Begin of the insertionbe helpful to define a duration similar to work packages. This facilitates planning and rescheduling

* \[open\] It mightEnd of the insertion also be that both have one field and that for stages, a range is defined.

* The user is supported when modifying the dates by the OpenProject date picker. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * The start date of a stage has to be before the end date. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionTheEnd of the insertion Begin of the deletion \[Assumption\] There is no requiredEnd of the deletion minimum length for a Begin of the deletion stage. AEnd of the deletion stage Begin of the insertionis one day: This means a stageEnd of the insertion can start and end on the same date. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the deletion \[Assumption\]End of the deletion There is no maximum length for a stage. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the deletion \[Assumption\]End of the deletion Stages cannot have overlapping dates. Gates can overlap the start/end date of a gate. But only exactly the start/end date. The date of a gate cannot be between a stage's dates. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * \[open\] Can a stage's date be the same as another stage's date. Assumption - No, this is not possible. Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertion\[open\] We might need something like "lag" in the future.

* End of the insertion Include stages/gate instances in the two seeded projects.

* \[open\] Begin of the insertionTheEnd of the insertion Begin of the deletion WhichEnd of the deletion dates Begin of the deletion should beEnd of the deletion set Begin of the deletion for the gatesEnd of the deletion in Begin of the insertionthe demo project are relative to the seeding date. The seeding date is seven days after the seeding date.End of the insertion Begin of the deletion those projects?End of the deletion

* \[open\] Could be done in a separate feature.

* Begin of the deletion \[Assumption\]End of the deletion If a project is copied, the dates for stages/gates are copied as well. There is a setting added when copying to disable this Begin of the insertionbehaviorEnd of the insertion Begin of the deletion behaviourEnd of the deletion similar to the other copy options.

* Begin of the insertionChangesEnd of the insertion Begin of the deletion \[open\] Should changesEnd of the deletion to the gates Begin of the insertionare journalized.End of the insertion Begin of the deletion be journalized?End of the deletion