# Feature SPAR-237 - Always display relations in the relations tab in a fixed order

Project: Stream Planning and Reporting
Status: closed
URL: https://community.openproject.org/work_packages/SPAR-237

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 15.5.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_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 |  |
| Build Number |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

**Context**

We previously specified the order in which to display relations within a single section: <mention class="mention" data-id="61885" data-type="work_package" data-text="##61885">##61885</mention>

However, this does not specify in which order the sections themselves (relation types) should be displayed. Currently, there is no fixed order and it seemed to depend rather arbitrarily on what the database returns. This work package seeks to define a fixed order for these sections.

**Acceptance criteria**

  - In the work package Relations tab, always show groups of relations in this order:
    
      - Related to
    
      - Predecessor (before)
    
      - Successor (after)
    
      - Duplicates
    
      - Duplicated by
    
      - Blocks
    
      - Blocked by
    
      - Includes
    
      - Part of
    
      - Requires
    
      - Required by
    
      - Children

  - Continue to only show sections for relations that exist. For example, a work package only has relations of types Children, Predecessors and Related to exist, it would be in this order:
    
      - Related to
    
      - Predecessor
    
      - Children

**Technical notes**

  - 
    <br>

**Permissions and visibility considerations**

  - No change, users who don't have the permission to see certain permissions will see ghost relations in their respective sections

**Translation considerations**

  - No change

**Out of scope**

  - A separate section for Parents is described separately: <mention class="mention" data-id="38030" data-type="work_package" data-text="##38030">##38030</mention>
