Content
View differences
Updated by Marc Alcobé 12 months ago
**As** a mobile user
**I want to** see the parent of the work package I'm checking
**so that** I don't need to go to the web app to check it
**Acceptance criteria**
* The add relations action triggers a FAB list and not a bottom sheet list.
* If the work package has a parent work package, add a new box for the parents' relation.
* Include a new flow to set a parent relation between the work package you are looking at, and another work package.
* This relation can not have description or lag.
* Make sure that this relation creates the relation also in the web app.
* The work packages displayed in the bottom sheet to select the parent is limited by the API `available_relation_candidates`.
* Check that the order of the relations matches the one implemented in the web app.
* It is only possible to have 1 parent. If the work package already has a parent, remove the option from the FAB menu.
* The more menu allows you to remove the relations.
* By adding a parent, the child's dates are not changed; if the parent has automatic scheduling activated, its dates will come from the children.
* If the parent previously had predecessors, those dates will be overwritten by those of the new children (Children get priority to predecessors)
* If the (new) parent was previously auto-scheduled, the dialogue 'This is automatically scheduled' should come up, up since it's an attempt to move an auto-scheduled work package ([see mockups here](https://www.figma.com/design/xiZOMN9Vdgm5RiZotIRa7p/Mobile-App---Work-packages?node-id=1130-8672&t=RmLZAaGmy0hDIIFN-4))
**Technical notes**
* <br>
**Permissions and visibility considerations**
* <br>
**Translation considerations**
* <br>
**Out of scope**
* Display higher hierarchies like grandparents or grandchildren
**I want to** see the parent of the work package I'm checking
**so that** I don't need to go to the web app to check it
**Acceptance criteria**
* The add relations action triggers a FAB list and not a bottom sheet list.
* If the work package has a parent work package, add a new box for the parents' relation.
* Include a new flow to set a parent relation between the work package you are looking at, and another work package.
* This relation can not have description or lag.
* Make sure that this relation creates the relation also in the web app.
* The work packages displayed in the bottom sheet to select the parent is limited by the API `available_relation_candidates`.
* It is only possible to have 1 parent. If the work package already has a parent, remove the option from the FAB menu.
* The more menu allows you to remove the relations.
* By adding a parent, the child's dates are not changed; if the parent has automatic scheduling activated, its dates will come from the children.
* If the parent previously had predecessors, those dates will be overwritten by those of the new children (Children get priority to predecessors)
* If the (new) parent was previously auto-scheduled, the dialogue 'This is automatically scheduled' should come up,
**Technical notes**
* <br>
**Permissions and visibility considerations**
* <br>
**Translation considerations**
* <br>
**Out of scope**
* Display higher hierarchies like grandparents or grandchildren