Content
Updated by Andrej Sandorf 8 days ago
**As** a user
**I want to** include long text custom fields in my work package description
**so that** can export the information
Current:
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><figure class="image image_resized op-uc-figure" style="width:368px;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/798612/content"></div><figcaption class="op-uc-figure--description">Input</figcaption></figure></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><figure class="image image_resized op-uc-figure" style="width:586px;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/798613/content"></div><figcaption class="op-uc-figure--description">PDF</figcaption></figure></td></tr></tbody></table></figure>
**Acceptance criteria**
* Non-nested custom long text fields referenced by a macro in a description are included in the export.
**Technical notes**
* "Non-nested" refers to macros like `workPackageValue:richtextfield` or `projectValue:richtextfield` are not inserted into another formatting, like tables, quotes, lists, etc.
As long text fields can contain all of those formattings themselves and even contain other rich text macros.
* We can look into supporting nested ones as well if they don't contain any of these.
**Permissions and visibility considerations**
* _No changes required for permissions, handled as with other custom fields_
**Out of scope**
* Nested long text field macros
**I want to** include long text custom fields in my work package description
**so that** can export the information
Current:
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><figure class="image image_resized op-uc-figure" style="width:368px;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/798612/content"></div><figcaption class="op-uc-figure--description">Input</figcaption></figure></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><figure class="image image_resized op-uc-figure" style="width:586px;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/798613/content"></div><figcaption class="op-uc-figure--description">PDF</figcaption></figure></td></tr></tbody></table></figure>
**Acceptance criteria**
* Non-nested custom long text fields referenced by a macro in a description are included in the export.
**Technical notes**
* "Non-nested" refers to macros like `workPackageValue:richtextfield` or `projectValue:richtextfield` are not inserted into another formatting, like tables, quotes, lists, etc.
As long text fields can contain all of those formattings themselves and even contain other rich text macros.
* We can look into supporting nested ones as well if they don't contain any of these.
**Permissions and visibility considerations**
* _No changes required for permissions, handled as with other custom fields_
**Out of scope**
* Nested long text field macros