# Feature OP-6700 - Change wording of relation queries

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-6700

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 10.4.0 |
| Sprint | 10.4.0 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

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

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

## The labels are inconsistent and misleading:

<table><tbody><tr><td><strong>Relations tab</strong></td><td><strong>Form configuration</strong></td><td>&nbsp;</td></tr><tr><td>Requires</td><td>&nbsp;</td><td>a work package created in the embedded table ends up swapped in the counterpart (PR 8023)</td></tr><tr><td>Required by</td><td>&nbsp;</td><td>a work package created in the embedded table ends up swapped in the counterpart (PR 8023)</td></tr><tr><td>Part of</td><td>Including</td><td>&nbsp;</td></tr><tr><td>Includes</td><td>Beeing part of</td><td>&nbsp;</td></tr><tr><td>Blocks</td><td>Blocked by</td><td>&nbsp;</td></tr><tr><td>Blocked by</td><td>Blocking</td><td>&nbsp;</td></tr><tr><td>Duplicated by</td><td>Duplicating</td><td>&nbsp;</td></tr><tr><td>Related to</td><td>Relating to</td><td>&nbsp;</td></tr><tr><td>Precedes</td><td>Following</td><td>&nbsp;</td></tr><tr><td>Follows</td><td>Preceding</td><td>&nbsp;</td></tr><tr><td>Children</td><td>Being child of</td><td>&nbsp;</td></tr></tbody></table>

I suggest to use the same wording in both select fields:

The label above the relations table configuration would be like this:

Header: Add table of related work packages (existing translation string from create button)

Filtered work package relations  (new translation string)

![](/api/v3/attachments/17094/content)

###