Content
View differences
Updated by Niels Lindenthal 4 months ago
**As a** project manager ### Steps to reproduce
**I want to** create 1. Create a pdf PDF report for a work package list including related tables work packages with a relationship
2. Select all "relationship columns" to be included in the table:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/741426/content">
### What is the buggy behavior?
**So that I** can better document m:n-entities. None of the relationship information is added to the table in the report, even though they have been selected.
<br> <img class="image_resized op-uc-image op-uc-image_inline" style="width:599px;" src="/api/v3/attachments/741427/content">
**Acceptance criteria** ### What is the expected behavior?
* Work packages from related tables are added to the export.
* The position selected relationship information is defined by included in the postion table view and includes the ID and title of the card.
* We show linked work package
In addition, I would kind of expect the following attributes:
* ID
* Type
* Subject
* Status
* Date custom tables within the work packages to be exported as well, see: <mention class="mention" data-id="65999" data-type="work_package" data-text="#65999">#65999</mention>
**I want to** create
2. Select all "relationship columns" to be included in the table:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/741426/content">
### What is the buggy behavior?
**So that I** can better document m:n-entities.
<br>
**Acceptance criteria**
* Work packages from related tables are added to the export.
* The position
* We show
In addition, I would kind of expect
* ID
* Type
* Subject
* Status
* Date