Content
View differences
Updated by Niels Lindenthal over 1 year ago
**As** a Project Portfolio Manager
lifecycle manager
**I want to** create plan lifecycle steps based on duration
**so that** I can plan independently from the dates, e.g.
* for project templates where project stages and gates already that get instantiated.
This feature only partially fulfils the user story since the duration is not yet an independent field. This will be done within ###59180.
**Acceptance criteria**
* Stages receive a duration.
* It is a separate field in the database.
* The duration will be calculated for now (`end_date - start_date + 1`)
* Gates don't have a duration.
* Another way of seeing it: The duration is always 0
* The duration is displayed as a column in the project life cycle administration table.
* For now the duration is read only. It will become editable via ###59180
**Permissions and visibility considerations**
**so that** I * Users having the "View project stages and gates" permission can add see the specific dates later once it duration.
**Out of scope**
* Duration columns in the project list
* Duration filters in the project list
* Duration is decided when not displayed in the project starts. overview page
**so that** I can plan independently from the dates, e.g.
* for
This feature only partially fulfils the user story since the duration is not yet an independent field. This will be done within ###59180.
**Acceptance criteria**
* Stages receive a duration.
* It is a separate field in the database.
* The duration will be calculated for now (`end_date - start_date + 1`)
* Gates don't
* Another way of seeing it: The
* The duration is displayed as a column in the project life cycle administration table.
* For now the duration is read only. It will become editable via ###59180
**Permissions and visibility considerations**
**so that** I
**Out of scope**
* Duration columns in the project list
* Duration filters in the project list
* Duration