Content
View differences
Updated by Marc Alcobé over 1 year ago
_**Note:** This is planned for the OpenProject Web App release 15.1 (11.12.24) as part of the features ##22360 and ##58011._
### Acceptance criteria:
* The lag is shown in the relations tab for follow-precedess 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.
* Add these "new" type of relations:
* Allow work package relation type **Child** in the Relations tab: Makes the related a work package a sub-item of the current (parent) work package.
* Rename current relation named _Precedes_ to **Predecessor (before):** The related work package necessarily needs to finish before this one can start.
* Rename current relation named _Follows_ to **Successor (after):** The related work package necessarily needs to start after this one finishes.
* Reorganise all the possible relations under the relation type dropdown in this order:
1. **Related to**
2. **Predecessor (before)**
3. **Successor (after)**
4. **Child**
5. **Duplicates**
6. **Duplicated by**
7. **Blocks**
8. **Blocked by**
9. **Includes**
10. **Part of**
11. **Requires**
12. **Required by**
* When adding a **Predecessor (before)** or a **Successor (after)** relation to a work package users will be able to introduce a lag of _X_ working days between both work packages.
* Users can also add a negative lag as specified in _<mention class="mention" data-id="58011" data-type="work_package" data-text="#58011">#58011</mention>._
* Lag already exists as an API element but has never been used in the frontend so far. Use the current API.
* When a relation of **Predecessor (before)** or a **Successor (after)** with lag is created display the lag added in the relation in the relations list in the tab.
**Figma and visuals**
https://www.figma.com/design/arGHBRVi6WLJDLTv0YoOoo/Mobile-App---Spike?node-id=2029-4982 (11.12.24)._
### Acceptance criteria:
* The lag is shown in the relations tab for follow-precedess 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.
* Add these "new" type of relations:
* Allow work package relation type **Child** in the Relations tab: Makes the related a work package a sub-item of the current (parent) work package.
* Rename current relation named _Precedes_ to **Predecessor (before):** The related work package necessarily needs to finish before this one can start.
* Rename current relation named _Follows_ to **Successor (after):** The related work package necessarily needs to start after this one finishes.
* Reorganise all the possible relations under the relation type dropdown in this order:
1. **Related to**
2. **Predecessor (before)**
3. **Successor (after)**
4. **Child**
5. **Duplicates**
6. **Duplicated by**
7. **Blocks**
8. **Blocked by**
9. **Includes**
10. **Part of**
11. **Requires**
12. **Required by**
* When adding a **Predecessor (before)** or a **Successor (after)** relation to a work package users will be able to introduce a lag of _X_ working days between both work packages.
* Users can also add a negative lag as specified in _<mention class="mention" data-id="58011" data-type="work_package" data-text="#58011">#58011</mention>._
* Lag already exists as an API element but has never been used in the frontend so far. Use the current API.
* When a relation of **Predecessor (before)** or a **Successor (after)** with lag is created display the lag added in the relation in the relations list in the tab.
**Figma and visuals**
https://www.figma.com/design/arGHBRVi6WLJDLTv0YoOoo/Mobile-App---Spike?node-id=2029-4982