### Begin of the insertion\\StepsEnd of the insertion Begin of the deletion StepsEnd of the deletion to reproduce

**Common steps:**

1. Be a non admin user

2. Have two projects

1. "Project read only": The user is member in here but does not have the "Manage work package relations" permission

2. "Project writable": The user is member with the permission "Manage work package relations" permission

3. Have two work packages one in each project

1. "Work package read only"

2. "Work package writable"

4. Go to the writable ticket "Work package writable"


**Create case:**

1. Go to the relations tab and open the modal to create a new "Blocks" permission (Also possible for other relations)

2. Insert "Work package read only"

3. Click "Add"


**Update case (If there already is an existing relation):**

1. Go to the relations tab and click on the three dots menu for the relation to the read only WP

2. Click "Edit relation"

3. Update the description

4. Click "Save"


**Delete case (If there already is an existing relation):**

1. Go to the relations tab and click on the three dots menu for the relation to the read only WP

2. Click "Delete relation"


### What is the buggy behavior?

**Create case:**

* The relation is created.


**Update case (If there already is an existing relation):**

* The relation is updated.


**Delete case (If there already is an existing relation):**

* The relation is deleted.


### What is the expected behavior?

**Common:**

* We enforce symmetry; the user needs write permission on both work packages in order to be able to create the relation.


Begin of the insertion**Add case (in-line error):**End of the insertion Begin of the deletion **Create case:**End of the deletion

* Relations with read-only permissions are still visible in the results. However, selecting one Begin of the insertionin the create realtion dialog formEnd of the insertion throws an in-line error below the field with text:

* "The selected work package Begin of the deletion is read-only andEnd of the deletion cannot be added Begin of the insertionbecause you do not have edit permissions for the selected work package."End of the insertion Begin of the deletion as a relation."End of the deletion


**Update case Begin of the insertion(flash error)**End of the insertion Begin of the deletion (If there already is an existing relation):**End of the deletion

* Begin of the insertionShow error after click on "Edit relations" in the more menu (before displaying the dialog) a relation already exists

* End of the insertion "This relation cannot be Begin of the insertioneditedEnd of the insertion Begin of the deletion updatedEnd of the deletion because Begin of the insertionyou do not have edit permissions forEnd of the insertion the Begin of the insertionselectedEnd of the insertion Begin of the deletion relatedEnd of the deletion work Begin of the insertionpackage."


End of the insertion Begin of the deletion package is read-only."


End of the deletion **Delete case Begin of the insertion(flash error):**End of the insertion Begin of the deletion (If there already is an existing relation):**End of the deletion

* Begin of the insertionShow error after click on "Delete relations" in the More menu:

* End of the insertion "This relation cannot be deleted because Begin of the insertionyou do not have edit permissions forEnd of the insertion the Begin of the insertionselectedEnd of the insertion Begin of the deletion relatedEnd of the deletion work Begin of the insertionpackage."


End of the insertion Begin of the deletion package is read-only."

End of the deletion <br>


### Screenshots and other files

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/314824/content">

### Technical notes

This is possible because the `relations/base_contract.rb` only checks the `model.from` work package for the permission.