# Feature OP-16759 - Auto-linking Work Packages via Hashtag Reference

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-16759

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

**As a** project member  
**I want to** automatically establish a relationship between work packages when referencing a work package number with `#` in the description  
**so that** related tasks are quickly and efficiently linked without manual intervention.

**Acceptance criteria**

*   When a user includes `#<WorkPackageID>` in a work package description, a relationship is automatically created if no existing relationship exists.
    
*   The relationship type is set to **&quot;relates to&quot;** by default.
    
*   If the referenced work package does not exist, no relationship is created.
    
*   If the referenced work package already has a relationship, no duplicate relationship is added.
    

**Technical notes**

*   If a valid ID is found and no relationship exists, create a **&quot;relates to&quot;** relationship automatically.
    
*   Log the auto-linking action for traceability.
    

**Permissions and visibility considerations**

*   _Project members with permission to edit work packages._
    
*   Users without permission to edit work packages will not trigger the auto-linking.
    
*   If a referenced work package is in a restricted or private project, the link is not created unless the user has access.
