# Feature DREAM-763 - Automatically upload PDF artefacts to project folder in Nextcloud or as work package attachment

Project: Stream Design System
Status: closed
URL: https://community.openproject.org/work_packages/DREAM-763

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.7.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List | PM² PMflex, RM PPM |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| DREAM-768 | Bug | Spacings and font size for new PDF settings are a little bit off | closed |  | 17.7.0 |  | Frontend components and Primer design system, Modules and project features / Export / PDF Export |
| DREAM-799 | Bug | Instructions for admins are missing to avoid user error | confirmed |  |  |  | Modules and project features / File storages, Modules and project features / Export / PDF Export |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / File storages, Modules and project features / Export / PDF Export |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Andrej Sandorf |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a project manager  
**I want to** automatically upload the PM²/PMflex artefacts to the project folder  
**so that** I can easily create an audit trail.

**Acceptance criteria**

*   We generalize the upload implementation for PIAs.  
    The generation/upload configuration is added to the PDF export settings in the global type config:  
    Options: 
    
    *   **Off** (default for all types)
        
    *   **Attach to work package**
        
    *   **Upload to project folder** - Nextcloud only (similar to PIA)
        
*   After each status change, the export is triggered (similar to PIA).
    
*   We use the existing file naming scheme from the PIA implementation. Files are not replaced but accumulate.
    
*   **Attach to work package:**   
    The generated PDF is added as a file attachment to the work package that changed status.  
    A file link to the uploaded PDF is added to the work package.
    
*   **Upload to project folder:**  
    The **type name** is used for the folder name inside the project folder.  
    The upload targets the work package's own project. If that project has no automatically-managed Nextcloud storage, the export is skipped for that work package (and logged)  
    A file link to the uploaded PDF is added to the work package.
    

**Permissions and visibility considerations**

*   Similar to PIA. Configuration is limited to administrators. The artefact is generated with full visibility of the work package's attributes (as in PIA), independent of any individual viewer's permissions.
    

**Out of scope**

*   Providers other than Nextcloud (OneDrive/SharePoint uploads).
    
*   Triggering on events other than status change (e.g. creation, arbitrary attribute changes).
    
*   Per-status configuration (any status change triggers the export).