# Feature SPAR-30 - Specify relation type in journalised activity entries for dates changes caused by relations

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

## 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 | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

### Note

These specs were split (de-scoped) from the following feature:

<mention class="mention" data-id="46481" data-type="work_package" data-text="###46481">###46481</mention>

### **Acceptance criteria**

  - Extend the current generic message ("Dates changed by changes to related {type} \#{id}: {subject}" so that it is more specific:
    
      - Use one of these strings, depending on the change:
        
          - For date changes caused by relations:
            
              - "**Dates changed** as a result of changes to predecessor {type} \#{id}: {subject}"
        
          - For date changes caused by children:
            
              - "**Dates changed** as a result of changes to child {type} \#{id}: {subject}"
        
          - If the immediate relationship cannot be established:
            
              - "**Dates changed** as a result of changes to {type} \#{id}: {subject}
                
                  - **\[open\]** does this ever happen?
        
          - If the related work package is not visible by the current user (ghost relations)
            
              - "**Dates changed** as a result of changes to a related work package"

  - When aggregating, only name the responsible work package for the last update