Content
View differences
Updated by Andrej Sandorf 3 days ago
**As** a project manager
**I want to** include wiki pages in the artefact
**so that** I can centralize the “fine prints” inning place.
**Acceptance criteria**
* In the PDF configuration I can select one or more wiki pages to be included
* I can change the order of the selected wiki pages
* Add a warning in the config that the included wiki pages are visible for the exporting user, regardless if they have access to it.
Note to QA: Different to the mockups on Figma, the select wiki dialog is NOT multiselect and does NOT load/show the selection on reopening. In the future there will be a full content tree (equal to the form configuration) where users can define which parts should be exported and in which order, replacing the whole form. So the amount of implementation needed was not warranted.
Note to Maya: Docs are already updated.
**Permissions and visibility considerations**
* Only admins and project admins for type variants can change the default configuration
* Treat admin inclusion of a wiki page as permission that the wiki page in question will be visible to everyone with access to the artifacts
**Technical considerations**
Currently, the PMflex PDF export is not in a background job. Depending on the amount and length of the included wiki pages, this may be necessary.
**Out of scope**
* Relative wiki pages in the individual project
* XWiki and any other non-internal providers
* Selecting a whole wiki, or implicitly including a page's sub-pages
* Wiki-specific macros like TOC, etc.
* <mention class="mention" data-id="82696" data-type="work_package" data-text="###XWI-180" data-display-id="XWI-180">###XWI-180</mention>
**I want to** include wiki pages in the artefact
**so that** I can centralize the “fine prints” inning place.
**Acceptance criteria**
* In the PDF configuration I can select one or more wiki pages to be included
* I can change the order of the selected wiki pages
* Add a warning in the config that the included wiki pages are visible for the exporting user, regardless if they have access to it.
Note to QA: Different to the mockups on Figma, the select wiki dialog is NOT multiselect and does NOT load/show the selection on reopening. In the future there will be a full content tree (equal to the form configuration) where users can define which parts should be exported and in which order, replacing the whole form. So the amount of implementation needed was not warranted.
Note to Maya: Docs are already updated.
**Permissions and visibility considerations**
* Only admins and project admins for type variants can change the default configuration
* Treat admin inclusion of a wiki page as permission that the wiki page in question will be visible to everyone with access to the artifacts
**Technical considerations**
Currently, the PMflex PDF export is not in a background job. Depending on the amount and length of the included wiki pages, this may be necessary.
**Out of scope**
* Relative wiki pages in the individual project
* XWiki and any other non-internal providers
* Selecting a whole wiki, or implicitly including a page's sub-pages
* Wiki-specific macros like TOC, etc.
* <mention class="mention" data-id="82696" data-type="work_package" data-text="###XWI-180" data-display-id="XWI-180">###XWI-180</mention>