# Feature PIR-120 - Include work package attributes in PIR PDF export

Project: Project Inititation Requests
Status: new
URL: https://community.openproject.org/work_packages/PIR-120

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| List | PM² PMflex |
| 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 / Export / PDF Export |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Signed off by |  |
| Interest by | Dom (224196000001898262) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Labor costs |  |

## Description

**As** an administrator  
**I want to** include the configured attributes of the PIR work package in the PIR PDF  
**so that** the generated PDF reflects both project-level information and information added to the work package during the subsequent review and approval process.

**Acceptance criteria**

*   The PIR PDF can include **work package attributes** in addition to the existing project attributes.
    
*   Work package attributes are included according to the **form configuration of the PIR work package type**.
    
*   When additional work package attributes are populated after the initial PIR creation, these values are included when the PIR PDF is regenerated.
    
*   When the PIR PDF is automatically regenerated, e.g. following a configured status change, the latest values of the relevant project and work package attributes are included.
    
*   The existing PIR creation and PDF generation workflow continues to work without requiring a separate PMflex artifact export.
    

**Technical notes**

*   The existing **PMflex artifact export** already supports exporting work package attributes according to the work package form configuration and could serve as a reference for the expected behavior.
    
*   The feature should extend the existing **PIR PDF generation**, rather than introduce an additional PDF generation mechanism.
    

**Permissions and visibility considerations**

*   The functionality should be available to administrators who can configure the PIR / Project Creation Wizard.
    
*   The generated PDF should only include attributes the PIR configuration is intended to expose.
    
*   Existing permissions for accessing the PIR work package and generated artifacts should remain unchanged.
    

**Translation considerations**

*   Project Initiation Request (PIR)
    
*   Project attributes
    
*   Work package attributes
    
*   PDF / artifact
    
*   Form configuration
    

**Out of scope**

*   Introducing additional PDF or artifact types.
    
*   Selecting between PIR and PMflex templates during a status change.
    
*   Changes to the generic PMflex artifact export.
    
*   Changes to Nextcloud storage locations or folder configuration.
    

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