Content
View differences
Updated by Attila Dombi over 1 year ago
> * 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.
>
> * 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.
>
>
>
>
>
>
>
>
> * 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.
>
> * 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.
>