Content
View differences
Updated by Parimal Satyal 12 months ago
**As** a project member
**When I** link to another work package from within the rich text fields, description, comment, etc.
**I want to** automatically create a relationship between the current and the linked work package
**so that** it a lot quicker to establish a bidirectional link that helps me later to find related work packages coming from the other direction.
**Acceptance criteria**
* When
* pasting a work package url
* or using the hash(es) notation to add a work package to the description field or comment box
* a little pop-over asks for the relation type, having "Related" as the default.
* that modal has an "Add relation" and a "skip" button
* If the user moves the cursor away from the actual link, the pop-over automatically disappears avec 2 seconds
* If there is already was a relationship (like a relationship, like parent-child, "related to" or any other relation), do not show the pop-over. There don't for adding another as there can only be one relationship between two work packages.
**When I** link to another work package from within the rich text fields, description, comment, etc.
**I want to** automatically create a relationship between the current and the linked work package
**so that** it a lot quicker to establish a bidirectional link that helps me later to find related work packages coming from the other direction.
**Acceptance criteria**
* When
* pasting a work package url
* or using the hash(es) notation to add a work package to the description field or comment box
* a little pop-over asks for the relation type, having "Related" as the default.
* that modal has an "Add relation" and a "skip" button
* If the user moves the cursor away from the actual link, the pop-over automatically disappears avec 2 seconds
* If there is already