# Feature SPAR-1 - Edit lag to follow-precedes-relations

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 15.2.0 |
| Votes | 42 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| SPAR-101 | Re-design Relations tab according to  Figma mockups (Primerise) | Feature | closed |  | 15.1.0 |  |

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/HrWVktq0SsGI2dqqIKQ11M/Scheduling---Lag-and-Modes?node-id=0-1 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Henriette Darge |
| Product manager |  |
| Developers |  |
| Designer | Parimal Satyal |
| 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** enter lag to follow/precedes relations   
**so that** this is included in the scheduling of work packages.

#### **Note**

Since we are changing the relations tab to include lag, we are also Primerising it without adding any additional functionality apart from the ability to add and edit lag.

#### **Acceptance criteria (high-level)**

  - The lag is shown in the relations tab for predecessor/sucessor relations.

  - The default is 0 days (unset).

  - Users with the permissions "Manage work package relations" can edit the lag.

  - The lag only considers working days in the current scope.

##### Viewing relations

When relations exist,

  - Predecessor/Successor relations include:
    
      - Lag (if it exists), expressed simply as "(Lag: 3 days)"
        
          - after the date (for predecessors)
        
          - before the date (for successors)

**Adding relations**

  - The creation dialog has an additional field:
    
      - Lag: input field (only for Predecessor and Successor relations)
        
          - Default: "0 days"
        
          - Caption: "The gap in number of working days in between the two work packages"
        
          - Validation: The field has to be an integer (whole numbers: negative, 0 or positive)
    
      - OPEN:
        
          - Should the unit be displayed as part of the label or as part of the input ??
        
          - When the value is empty, should we leave the field empty (as in figma) or display "0"?

**Editing relations**

  - Lag and description can be modified

#### **Visuals and Figma mockups**

The UX/UI is a work in progress. For the most up-to-date mockups, please refer to the Figma document:

 

#### **Anticipated UX issues**

  - A user, especially one who is not familiar with the concept of lag, might not understand the concept.
    
      - We've added a caption to explain what it is in the create/edit relations modal.

  - In a Gantt view, when a user moves a work package into the future, certain other work packages might be pushed. Based on the lag set for those relations, some might move by keeping a certain distance (3 days in between), some might move with no distance (the next day) and some might move with negative distance (-2 days). How should the user understand this inconsistent behaviour, especially if she cannot see that lag has been set inside the work packages?
    
      - How can we make lag more visible in the Gantt view itself? It would have to be in the lines connected the work packages, but we know that there are technical limitations to how much we can do here.

#### Reference

**MS Project:**

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/95368/content"></div><figcaption class="op-uc-figure--description">Example (MS Project):</figcaption></figure>

#### Out of scope

  - Making lag visible in the Gantt chart

  - Negative lag: <mention class="mention" data-id="58011" data-type="work_package" data-text="##58011">##58011</mention>

  - Displaying ghost relations, described separately: <mention class="mention" data-id="58427" data-type="work_package" data-text="##58427">##58427</mention>

  - The option to include non-working days in lag (option to select/deselect "Working days" next to Lag in the relation edit modal)

  - Scheduling modes, which will worked on after this feature: <mention class="mention" data-id="42388" data-type="work_package" data-text="##42388">##42388</mention>