# Feature OP-19251 - Copy agenda items including outcomes to subsequent meetings

Project: OpenProject
Status: in test
URL: https://community.openproject.org/work_packages/OP-19251

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0, Passion time |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 | Modules and project features / Meetings |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan | Community (COM) |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee | Cécile Guiot |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Alfonso Mancilla |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

### **User story**

As a user managing recurring meetings  
I want to copy or move agenda items including their outcomes to a subsequent meeting  
so that ongoing topics retain their context and do not require manual duplication of results

### Acceptance criteria

*   When copying an agenda item to another meeting, users are given an option to include outcomes
    
*   A checkbox or selection dialog is available: “Include outcomes”
    
*   If selected, all outcomes (e.g. notes, decisions) linked to the agenda item are copied to the new meeting
    
*   If not selected, current behavior remains unchanged (only agenda item is copied)
    
*   Copied outcomes are clearly associated with the new agenda item
    
*   The system maintains data integrity (no unintended linkage between original and copied outcomes)
    

### Technical notes

*   Outcomes are currently stored as separate entities linked to agenda items
    
*   Copy logic needs to be extended to optionally duplicate associated outcome records
    
*   Ensure copied outcomes are newly created objects (no shared references)
    
*   Consider extensibility for future related entities (e.g. attachments, comments)
    
*   UI changes required in copy/move interaction (checkbox or modal)
    

### Permissions and visibility considerations

**To whom is this feature visible?**

*   Users with permission to view and edit meetings and agenda items
    

**When is it not visible?**

*   Users without sufficient permissions to view or edit agenda items
    
*   In contexts where copying/moving agenda items is not allowed
    

### Translation considerations

**Key terms and phrases in the key languages**

*   English:
    
    *   “Include outcomes”
        
    *   “Copy agenda item”
        
    *   “Outcomes”
        
*   German:
    
    *   „Ergebnisse einschließen“
        
    *   „Tagesordnungspunkt kopieren“
        
    *   „Ergebnisse“
        

### Out of scope

*   Automatic synchronization between original and copied outcomes
    
*   Selective partial editing of outcomes during copy (beyond basic selection)
    
*   Changes to outcome data model or structure
    
*   Copying unrelated entities (e.g. work packages not explicitly linked)
    

###   

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
