Content
View differences
Updated by Niels Lindenthal almost 2 years ago
**As an** OpenProject employee
**I want to** trigger the pdf creation from markdown files directly inside OpenProject
**so that** I don't have to install all the mechanism on my local machine.
**Acceptance criteria**
* No local installation of Ruby and the export gem required.
* The .md-content is taken from description.
* Text macros are rendered in the pdf export, e.g.:
* `workPackageValue:45896:updateAt` -> workPackageValue:45896:updatedAt
* `workPackageValue:45896:author` -> workPackageValue:45896:author
* `workPackageValue:45896:status`\-> workPackageValue:45896:status
* The pdf export is triggered from the export modal.
* For each styling we have a separate icon in the export modal (styling definition and selection will be enhanced later).
* contract
* Feature flag so we can test it on community earlier before we have the modal
**Open**
* How to manage the YAML.files?
* Can we develop this without the export modal?
**I want to** trigger the pdf creation from markdown files directly inside OpenProject
**so that** I don't have to install all the mechanism on my local machine.
**Acceptance criteria**
* No local installation of Ruby and the export gem required.
* The .md-content is taken from description.
* Text macros are rendered in the pdf export, e.g.:
* `workPackageValue:45896:updateAt` -> workPackageValue:45896:updatedAt
* `workPackageValue:45896:author` -> workPackageValue:45896:author
* `workPackageValue:45896:status`\-> workPackageValue:45896:status
* The pdf export is triggered from the export modal.
* For each styling we have a separate icon in the export modal (styling definition and selection will be enhanced later).
* contract
* Feature flag so we can test it on community earlier before we have the modal
**Open**
* How to manage the YAML.files?
* Can we develop this without the export modal?