# Feature SPAR-27 - Follows / Precedes relationship adds unneccesary days to work packages

Project: Stream Planning and Reporting
Status: new
URL: https://community.openproject.org/work_packages/SPAR-27

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Votes | 9 |
| 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 |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

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

## Estimates and progress

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

## Description

### Steps to reproduce

create arbitrary workpackages and milestones with follow/precede-relationships.

### What is the buggy behavior?

OP sets the start date for the following milestone to one day after the end date of the preceding work package.

Example:

WP 1: End date: 31.01.2023 - precedes Milestone 1

MS 1: Start date 1.2.2023 - follows WP 1

(same goes for any type of work package, actually)

This issue cannot be solved with manual planning, because then the relationship does not work anymore, as manual planning "overrides" the relation.

### What is the expected behavior?

The relationship should allow the following work package to start on the same day as the preceding work package.

Reasoning: Let's say you finish work package "software testing" on a Friday. In the afternoon you sign of this stage of the project and hit the milestone "testing successful". That is all on the same day. Also, if you had to cut of one day for the actual work package, so that it would end on a Thursday in order to get the milestone to hit the Friday, it would undermine the intention of planning the number of required working days in the first place.

### Important notes

I am convinced that this should be changed, because whether a following work package should start the day after or on the same day with respect to its predecessor is a decision made by the project manager. 

If this was changed, however, the change would have to bear in mind, that it may severly affect existing project plans.

###