# Feature DREAM-1057 - Possibility to decide whether to move children allong with a work package

Project: Stream Design System
Status: review failed
URL: https://community.openproject.org/work_packages/DREAM-1057

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.1.0 |
| Sprint |  |
| Backlog bucket |  |
| 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 | Frontend components and Primer design system, Modules and project features / Work packages |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan | Community (COM) |

## Details

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

## People

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

## Estimates and progress

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

## Description

**Acceptance criteria**

*   If the user tries to moves a parent work package with children show a dialog with these options:
    
    *   **Option 1: Move just this work package**
        
        *   Caption: Child work packages will remain in the current project but will still keep this as the parent
            
    *   **Option 2: Include all descendants**
        
        *   Caption: Child work packages will also be moved to the new project
            
    *   If option 2 is selected, show a banner (info): &quot;Only work packages that you have the permission to edit will be moved. Others will remain in the current project.&quot;
        
    *   When confirming the selection we get to the current `/move` page where we can select the project to move to
        
*   If there is a child, that is either not visible or not editable to the current user, this child does not get updated&nbsp;
    
*   Moving also affects grandchildren, even if there are elements in between in the hierarchy which the user cannot edit or see.
    
*   If the setting to allow cross-project hierarchy is turned off, we show the same dialog with Option 1 disabled. The banner (info) says: &quot;Cross-project work package relations are disabled, so all descendants will be moved along. The move will fail if you do not have permission to move all of them.&quot;
    

<br>
