# Feature SPAR-159 - Show indirect relations (successors/predecessors) in relations tab

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Votes |  |
| 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 | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/HrWVktq0SsGI2dqqIKQ11M/Scheduling---Modes%2C-Lag%2C-Single-date?node-id=1792-7664 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Parimal Satyal |
| Accountable |  |
| Product manager |  |
| 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** know when a time-sensitive relation is an indirect one (via a parent)  
**so that** I can better understand how these indirect relations might affect the scheduling of my work package

**Acceptance criteria**

  - In the Relations tab in the work package split screen and on the 'Predecessor' and 'Sucessor' tabs in the date picker:
    
      - When a work package has a predecessor or successor relationship via its parent (and thus not a direct relationship) that affects its scheduling,
        
          - Mark these relations with an "Indirect" label similar to "Closest"
    
      - It's possible for a relationship to be both closest and indirect
    
      - Because this can add additional length to the line with dates and lag:
        
          - Reduce font size from `Body/Medium` to `Body/Small`
    
      - These relations also do not have a More icon, since editing or removing them is not possible (these have to be done via the parent)

  - If an indirect relationship In the datepicker, when a user clicks on 'Show relations' button:
    
      - Also show indirect relationships that affect scheduling of the current work

**Technical notes**

  - *\[open\] Are there other ways a relationship can be indirect apart from through a parent?*

**Open points**

  - *\[open\] What about indirect ancestors (eg. grand-parents) or descendents (eg. grand-children)? In other words, should we display n+1 level hierarchies in the Children section with the indirect label? But whouldn't we need to then display the hierarchy since a flat display is not really helpful.*

**Permissions and visibility considerations**

  - We follow existing rules on visiblity; if a user does not have the necessary permissions to view details of a related work package, we will display a 'ghost' relation as described in <mention class="mention" data-id="58427" data-type="work_package" data-text="##58427">##58427</mention>

**Out of scope**

  - Indirect relations shown in a separate block; this would add additional visual complexity and we do not see the need for this at the moment

**Example**

Example of "wp" having "predecessor of ancestor" as an indirect predecessor:

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