# Feature OP-19102 - Visual Alert for Work Package/Project Phase Date Conflicts

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-19102

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 2 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Project lifecyle - phases and gates, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a project manager  
**I want to** be visibly notified if the start- and/or end-date of a work package does collide with the start- and/or end-date of its associated project life cylce phase  
**so that** I know that a work package needs to be re-scheduled

**Acceptance criteria**

  - User sees a visible hint that a set date does not fit to the planned scheduled derived from the project life cycle phase selected for a work package

<br>

**Current situation**

User can select arbitrary dates for work packages. However, the project phase should define in which time frame a work package shall be closed. At the moment, these two scheduling options are not linked to each other in any way.  
There should at least a hint that the schedule of a work package does not align with the schedule of its assinged project phase.

**Technical notes**

  - 
    <br>

**Permissions and visibility considerations**

  - All users with edit permissions for work packages and access to project life cycle features

**Translation considerations**

  - *Key terms and phrases in the key languages* 

**Out of scope**

  - Workflows for:
    
      - Change of associated phase after a date was set
    
      - General update of phase's scheduled dates

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*
