Content
View differences
Updated by Andrej Sandorf 7 days ago
**As** an OpenProject admin
**I want to** customize the PDF exports (Work package export)
**so that** my project teams do not need to do those settings with every export.
**Acceptance criteria**
* In Administration -> Work packages -> Types -> Type A -> PDF export there is a setting for each PDF
* Clicking on the edit mode opens a fullscreen configuration screen in a new page (one route for each template).
* Each PDF export can have different settings
* PMflex artefact: (just an example, will be implemented with <mention class="mention" data-id="78561" data-type="work_package" data-text="#PIR-118" data-display-id="PIR-118">#PIR-118</mention>) artifact:
* Include project budget
* Include project lifecycle
* ...
* Business letter (just an example, will be implemented with <mention class="mention" data-id="60437" data-type="work_package" data-text="#OP-16397" data-display-id="OP-16397">#OP-16397</mention>)
* Text placeholder footer left
* Text placeholder footer middle
* Text placeholder footer right
* ...
* These settings are loaded into the Export dialog when exporting a work package
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Creating PDF templates from the user frontend
* Centrally managed placeholder text like imprint
* Settings for the file naming schema
* Order of attributes (for now hard-coded in the PDF export template)
* [OP-16397](https://community.openproject.org/work_packages/OP-16397)
* <mention class="mention" data-id="78561" data-type="work_package" data-text="#PIR-118" data-display-id="PIR-118">#PIR-118</mention>
**I want to** customize the PDF exports (Work package export)
**so that** my project teams do not need to do those settings with every export.
**Acceptance criteria**
* In Administration -> Work packages -> Types -> Type A -> PDF export there is a setting for each PDF
* Clicking on the edit mode opens a fullscreen configuration screen in a new page (one route for each template).
* Each PDF export can have different settings
* PMflex artefact: (just an example, will be implemented with <mention class="mention" data-id="78561" data-type="work_package" data-text="#PIR-118" data-display-id="PIR-118">#PIR-118</mention>)
* Include project budget
* Include project lifecycle
* ...
* Business letter (just an example, will be implemented with <mention class="mention" data-id="60437" data-type="work_package" data-text="#OP-16397" data-display-id="OP-16397">#OP-16397</mention>)
* Text placeholder footer left
* Text placeholder footer middle
* Text placeholder footer right
* ...
* These settings are loaded into the Export dialog when exporting a work package
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* Creating PDF templates from the user frontend
* Centrally managed placeholder text like imprint
* Settings for the file naming schema
* Order of attributes (for now hard-coded in the PDF export template)
* [OP-16397](https://community.openproject.org/work_packages/OP-16397)
* <mention class="mention" data-id="78561" data-type="work_package" data-text="#PIR-118" data-display-id="PIR-118">#PIR-118</mention>