Skip to content

OpenProject is the leading open source project management software for product, project and portfolio management. A powerful Jira alternative with agile planning, issue tracking, roadmaps, Gantt charts, time tracking, collaboration features, and more. Available on premises or in the cloud. ⭐ Star us on GitHub

[#65395] Work package relations menu changes https://community.openp… (#19424)

Maya Berdygylyjova1e953b613b8b
diff --git a/docs/user-guide/work-packages/work-package-relations-hierarchies/README.md b/docs/user-guide/work-packages/work-package-relations-hierarchies/README.md
index 9fb82490633..d1e888d983f 100644
--- a/docs/user-guide/work-packages/work-package-relations-hierarchies/README.md
+++ b/docs/user-guide/work-packages/work-package-relations-hierarchies/README.md
@@ -37,21 +37,8 @@ Work package relations indicate that work packages address a similar topic or cr
You can select one of the following relations:
-- **Create new child** - This option lets you create a new package and automatically adds it as a child to the current (parent) work package.
-
-- **Child** - This option allows you to add an existing work package as a child to the current (parent) work package.
-
- **Related to** - This option adds a link from the work package A to work package B, so that project members can immediately see the connection, even if the work packages are not members of the same hierarchy.
-- **Parent** - This option makes the related work package a parent of the current (child) work package.
-
-- **Duplicates / Duplicated by** - This option indicates that the work package B duplicates a work package A in one way or another, for example both address the same task. This can be useful if you have the same work package that needs to be a part of a closed and public projects at the same time. The connection in this case is only semantic, the changes you make in work package A will need to be adapted in work package B manually.
-
-> [!NOTE]
-> Some changes in statuses will be adjusted automatically for the duplicated work package. Specifically, if the status of a work package A is set to be "closed" (or set to any status that is defined to count as "closed" in the [system settings](../../../system-admin-guide/manage-work-packages/work-package-status/), for example "rejected" often counts as a "closed" status), the status of the work package B will change to "closed". Note that this is direction dependent. Only if the work package A is closed will the work package B be closed as well, not the other way around.
-
-- **Blocks / Blocked by** - This option defines status change restrictions between two work packages. If you set a work package A to be blocking work package B, the status of work package B cannot be set to closed or resolved until the work package A is closed.
-
- **Predecessor (before)/ Successor (after)** - Defines a chronological relation between two work packages. For example, if you set a work package A to precede a work package B, the start date of B has to be at least a day after the finish date of A.
Please note: If work package B is in [manual scheduling mode](../../gantt-chart/scheduling/#manual-scheduling), changing the finish date of work package A will have no effect on work package B.
@@ -71,6 +58,21 @@ You can always edit the *Description* and *Lag* fields at a later time.
![Add a successor work package in OpenProject](openproject_user_guide_relations_tab_edit_lag.png)
+- **Create new child** - This option lets you create a new package and automatically adds it as a child to the current (parent) work package.
+
+- **Child** - This option allows you to add an existing work package as a child to the current (parent) work package.
+
+- **Parent** - This option makes the related work package a parent of the current (child) work package.
+
+- **Other relations** - Clicking *other relations* opens second level navigation with additional relations options. They include:
+
+- **Duplicates / Duplicated by** - This option indicates that the work package B duplicates a work package A in one way or another, for example both address the same task. This can be useful if you have the same work package that needs to be a part of a closed and public projects at the same time. The connection in this case is only semantic, the changes you make in work package A will need to be adapted in work package B manually.
+
+> [!NOTE]
+> Some changes in statuses will be adjusted automatically for the duplicated work package. Specifically, if the status of a work package A is set to be "closed" (or set to any status that is defined to count as "closed" in the [system settings](../../../system-admin-guide/manage-work-packages/work-package-status/), for example "rejected" often counts as a "closed" status), the status of the work package B will change to "closed". Note that this is direction dependent. Only if the work package A is closed will the work package B be closed as well, not the other way around.
+
+- **Blocks / Blocked by** - This option defines status change restrictions between two work packages. If you set a work package A to be blocking work package B, the status of work package B cannot be set to closed or resolved until the work package A is closed.
+
- **Includes / Part of** - Defines if work package A includes or is part of work package B. This relation type can be used for example when you have a roll-out work package and work packages which should be shown as included without using hierarchical relationships. There is no additional effect.
- **Requires / Required by** - Defines if work package A requires or is required by work package B. There is no additional effect.
diff --git a/docs/user-guide/work-packages/work-package-relations-hierarchies/openproject_user_guide_wp_add_child.png b/docs/user-guide/work-packages/work-package-relations-hierarchies/openproject_user_guide_wp_add_child.png
index 6510900c5ae..1c02b126b8d 100644
Binary files a/docs/user-guide/work-packages/work-package-relations-hierarchies/openproject_user_guide_wp_add_child.png and b/docs/user-guide/work-packages/work-package-relations-hierarchies/openproject_user_guide_wp_add_child.png differ
diff --git a/docs/user-guide/work-packages/work-package-relations-hierarchies/openproject_user_guide_wp_add_relations_button.png b/docs/user-guide/work-packages/work-package-relations-hierarchies/openproject_user_guide_wp_add_relations_button.png
index f3e2cef10cf..e1ec443348c 100644
Binary files a/docs/user-guide/work-packages/work-package-relations-hierarchies/openproject_user_guide_wp_add_relations_button.png and b/docs/user-guide/work-packages/work-package-relations-hierarchies/openproject_user_guide_wp_add_relations_button.png differ