Content
Updated by Andrej Sandorf 8 days ago
  **As** a user   
**I want to** include long rich text custom fields in my work package description   
**so that** can export the information
**Acceptance criteria**
* Non-nested custom long rich text fields referenced by a macro in a description are included in the export.  via macro. 
    
**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 rich 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 rich text field macros
  
        **I want to** include long
**so that** can export the information
**Acceptance criteria**
* Non-nested custom long
**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
* 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