# Feature OP-17878 - PDF Meeting Export: Have the same styling applied to the PDF as on the web

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-17878

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Export / PDF Export, Modules and project features / Meetings |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | OP Dev Sirius Team |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a user  
**I want to f**eature parity for the styling options on the web and the PDF  
**so that I** have the expected results

*Copied user feedback from* <https://community.openproject.org/projects/openproject/work\_packages/67365/activity#comment-1444152>

> I've attached a test PDF export. As a user I assume that I would see the same, or very similar styling when I export my styled memo, but that is not the case.  
> The line under Heading 1, visible in the Meeting memo in OpenProject, a good visual aid to segment a memo, is not present in the PDF export. I also don't really see a differences between Heading 1 & 2. and the table borders work pretty mysteriously for me.  
> So, for example if I want to achieve the visual of the Heading 1, I have to use a Section, which by the way is exported in a way so that only a line is visible under the Section header. Which is fine, if I know that that is what I will be seeing in the exported memo. Right now I had to go and do a lot of tests to see and know how my memo would look like when exported.  
> Now I have my styling rules based on those tests, but this not ideal.

**Acceptance criteria**

  - **F**eature parity

<br>
