# Epic FND-40 - Configurable work package relationship types per project

Project: Stream workspace foundations
Status: new
URL: https://community.openproject.org/work_packages/FND-40

## Detailed specification

### Motivation and background information

OpenProject supports various relationship types between work packages, such as relates to, duplicates, blocks, requires, and others. Currently, all relationship types are globally available across every project without any possibility to restrict or configure which types are shown or usable within a specific project context.

Different projects have different workflows and methodologies. For some projects, certain relationship types are irrelevant, confusing, or even counterproductive. There is currently no way to hide unused relationship types from the UI within a specific project.

### Acceptance criteria

##   

Main goals:

*   Allow instance administrators and project administrators to configure which relationship types are enabled per project.
    
*   Allow instance administrators to create their own relationship types.
    
*   Hide disabled relationship types from the work package detail view, relation tab, and any other UI locations where relationships are managed.
    
*   Include it in the project templates.
    
*   Include it in the workflow schemas.
    
*   Locking configuration at instance level
    
    *   Each relationship type can be marked as locked at the instance level
        
    *   Locked relationship types cannot be toggled by project administrators
        
    *   The project settings UI clearly indicates which types are locked

### Out of scope

*   Creating entirely custom relationship types.
    
*   Restricting relationship visibility on a per-role or per-user basis within a project.
    
*   Deleting existing relationships when a type is disabled.

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q2 |
| Date |  |
| Votes |  |
| List | RM Jira exit, TIB 2026 |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance | Medium — Useful Mid-Term |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Rosanna Sibora |
| Product manager | Sonita Soth |
| Designer | Parimal Satyal |
| Developers | OP Dev Comms Team |
| Requested by |  |
| Interest by | Black (37919), Bowling (40324), Home (224196000003952096) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 25d 0h |

## Description

As a project administrator, I want to be able to enable or disable specific work package relationship types for certain project, so that the team only sees the relationship types relevant to our workflow.

Additionally I also want to create my own relationships if needed.