# Bug OP-6692 - Work package relation labels inconsistent between form configuration and relations tab

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 10.4.0 |
| Observed in versions | 10.5.0 |
| Sprint | 10.4.0 |
| Backlog bucket |  |
| Bug found in version (deprecated) | 10.5.x |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

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

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

## **Steps to reproduce:**

1.  Add a table of related work packages group to a work package type.
2.  In the table of related work packages display work packages which are "required by".
3.  Go to a work package of that type, click to add a new entry and create a work package.

### **Actual Behavior**

Work package has relation type "Required" instead of "Required by", meaning the created work package is not displayed in the table (see gif).

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

### **Expected Behavior**

Work package is correctly added with relationship "required by".