Content
View differences
Updated by Parimal Satyal over 1 year ago
**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,
* Each type of existing relation is contained in a box section
* Predecessor/Successor relations include:
* The words "(before)" for Predecssors and "(after)" for Successors after the section titles for additional clarity
* Start and end date of the related work package (if it exists)
* Indication of manual scheduling (pin icon) if that's the case
* Lag (if it exists), expressed simply as "(Lag: 3 days)" after the date
**Adding relations**
* Click on the button will trigger a flat Action menu to select relation types. Each relation has a title and a short caption that describes the relation type
* Selecting a relation type will display a dialog:
* Title: "Add {relation type}"
* Body:
* Work package search input
* Description: input 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)
**Editing relations**
* Relations can also be edited
* The More (⋯) action on relations displays a drop-down with two options:
* Edit relation
* Delete relation
* The "Edit relation" modal displays the Edit modal
* This is a variation of the add relation modal
* The work package field is inactive (it is not possible to modify this)
* Lag and description can be modified
* Child relations only have the "Delete" relation option; they cannot be edited (because they can have neither lag nor description)
#### **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:
workPackageValue:"Figma wireframes"
<br>
**Add successor dialog**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:515px;" src="/api/v3/attachments/238431/content">
**Multiple relations visible:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:450px;" src="/api/v3/attachments/234377/content">
**Edit relation modal:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:508px;" src="/api/v3/attachments/238432/content">
#### **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: ##58011
* Displaying ghost relations, described separately: ##58427
* 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: ##42388
**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,
* Each type of existing relation is contained in a box section
* Predecessor/Successor relations include:
* The words "(before)" for Predecssors and "(after)" for Successors after the section titles for additional clarity
* Start and end date of the related work package (if it exists)
* Indication of manual scheduling (pin icon) if that's the case
* Lag (if it exists), expressed simply as "(Lag: 3 days)" after the date
**Adding relations**
* Click on the button will trigger a flat Action menu to select relation types. Each relation has a title and a short caption that describes the relation type
* Selecting a relation type will display a dialog:
* Title: "Add {relation type}"
* Body:
* Work package search input
* Description: input 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)
**Editing relations**
* Relations can also be edited
* The More (⋯) action on relations displays a drop-down with two options:
* Edit relation
* Delete relation
* The "Edit relation" modal displays the Edit modal
* This is a variation of the add relation modal
* The work package field is inactive (it is not possible to modify this)
* Lag and description can be modified
* Child relations only have the "Delete" relation option; they cannot be edited (because they can have neither lag nor description)
#### **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:
workPackageValue:"Figma wireframes"
**Add successor dialog**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:515px;" src="/api/v3/attachments/238431/content">
**Multiple relations visible:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:450px;" src="/api/v3/attachments/234377/content">
**Edit relation modal:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:508px;" src="/api/v3/attachments/238432/content">
* 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: ##58011
* Displaying ghost relations, described separately: ##58427
* 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: ##42388