# Epic SPPM-97 - Project life cycle with phases and gates - Step 2: work package assignments and journalization

Project: Stream Project Portfolio Management
Status: closed
URL: https://community.openproject.org/work_packages/SPPM-97

## Detailed specification

### Motivation and background information

### Acceptance criteria

*   General structure and basics
    
    *   Stages are renamed to &quot;Phases&quot;
        
    *   Gates are renamed to &quot;Phase gates&quot;
        
    *   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.

### Out of scope

*   Dedicated end point for start and finish date of a project
    
*   Project types
    
*   Duration
    
*   Inheritance/sharing
    
*   Timeline view/Gantt chart
    
*   Switching between manual and automatic scheduling (similar to scheduling of work packages)
    
*   Lag
    
*   Project types
    
*   Dashboards
    
*   Table view

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| List | cProject |
| Target versions |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| SPPM-89 | Feature | Phases as work package attribute | closed |  | 16.1.0 | Stream Project Portfolio Management | Medium |  |
| SPPM-98 | Feature | Journalize changes to phases and gates | closed |  | 16.1.0 | Stream Project Portfolio Management | Medium |  |
| SPPM-99 | Feature | Option to copy phase on copying a project | closed |  | 16.1.0 | Stream Project Portfolio Management | Medium |  |
| SPPM-100 | Feature | Automatic scheduling for phases and phase gates | closed |  | 16.1.0 | Stream Project Portfolio Management | Medium |  |
| SPPM-102 | Feature | Filters for phases and phase gates in project list | closed |  | 16.1.0 | Stream Project Portfolio Management | Medium |  |
| SPPM-103 | Feature | Order by phases and phase gates on project list | closed |  | 16.1.0 | Stream Project Portfolio Management | Medium |  |
| SPPM-148 | Feature | Date picker to edit phases and phase gates of a project life cycle | closed |  | 16.1.0 | Stream Project Portfolio Management | Medium |  |
| SPPM-150 | Feature | Turn gates into property of phase (rename life cycle elements to "Phase" and "Phase gates") | closed |  | 16.1.0 | Stream Project Portfolio Management | Medium |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| SPPM-178 | Task | Set enterprise level for custom project phases to premium | closed | Oliver Günther | 16.0.0 |  |
| SPPM-205 | Bug | Update working days settings warning messages to include phases | closed |  | 16.1.0 |  |
| SPPM-203 | Bug | Incorrect rescheduling after non working days are changed | closed |  | 16.1.0 |  |
| SPPM-197 | Bug | Clearing the start date of a following phase is not possible | closed |  | 16.1.0 |  |
| SPPM-192 | Bug | The following phase's finish date is inconsistent with the start date | closed |  | 16.1.0 |  |
| SPPM-190 | Code maintenance | refactor life cycle filters, add missing documentation | closed |  | 16.1.0 |  |
| SPPM-188 | Bug | The second phase's start date selection is not enabled | closed |  | 16.1.0 |  |
| SPPM-183 | Bug | Disabling an incomplete phase leads to inconsistencies | closed |  | 16.1.0 |  |
| SPPM-176 | Bug | Project level lifecycle phases are clickable for non Enterprise users | closed |  | 16.1.0 |  |
| SPPM-201 | Bug | PG::UndefinedColumn: ERROR:  column ancestor.project_phase_id does not exist | rejected | Jens Ulferts | 16.1.0 | Modules and project features / Project lifecyle - phases and gates, Modules and project features / Relations and scheduling |
| SPPM-199 | Bug | Wrong wording for project phases in system administration | closed |  | 16.1.1 | Modules and project features / Project lifecyle - phases and gates |
| SPPM-200 | Bug | Administration project life cycle page using wrong Primer components | closed |  | 16.2.0 | Modules and project features / Project lifecyle - phases and gates, Frontend components and Primer design system / Page header |
| SPPM-182 | Bug | Flickering Life Cycle Definition specs | closed |  | 16.2.0 |  |
| SPPM-116 | Code maintenance | Remove feature flag for project phases | closed |  | 16.2.0 |  |

## Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Project lifecyle - phases and gates, Modules and project features / Project list |
| Enterprise plan | Enterprise / Premium (PRE) |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Jens Ulferts |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers | OP Dev Polaris Team |
| Requested by | Stadt Köln |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 250d 0h · Σ 250d 0h |

## Description

### Story 1: Automatic scheduling

**As a** project portfolio manager

**I want to** automatically reschedule succeeding phases and gates.

**So that I** don't have to to this manually.

### Story 2: Work package assignments

**As a** project portfolio manager

**I want to** assign work packages to a phase (not to gates)

**So that I** can create work plans for each phase.

### Story 3: Journalization

**As a** project portfolio manager

**I want to** journalize the changes to the dates of phases/gates

**So that I** see the changes of the project schedule in the project activity.

### Story 4: Separate permissions

**As a** project portfolio manager

**I want to** have separate permissions to activate phases and gates and to change dates of phases and gates

**So that I** can avoid project managers to change the project lifecycle.
