Clayton Tidwell
When a ClickUp Doc contains task mentions (the
<a type="task" mention-name="...">
format), they render correctly inside the app, showing the task name dynamically. However, when that same Doc is exported to PDF or HTML, every task mention displays as
"Private"
followed by the raw URL instead of the task name.
Expected behavior:
Exported task mentions should display the task name, either by using the
mention-name
attribute as fallback text or by requiring/auto-populating visible inner text at mention creation time.
Current behavior:
The export engine encounters an empty anchor tag, has no visible text to render, and falls back to "Private" + the raw task URL. This makes exported sprint retrospectives, status reports, and any doc referencing tasks unreadable without manually cross-referencing every URL.
Impact:
Any team exporting Docs for stakeholders, clients, or offline review (PDF, HTML) loses all task name context. This is especially painful for sprint reports, project updates, and retrospectives that reference dozens of tasks.
Workaround:
Manually duplicating the task name as visible text inside every mention link. This works but defeats the purpose of dynamic task mentions and is tedious at scale.
Suggested fix:
The export renderer should use
mention-name
(or a live API lookup of the task name) as the display text when the anchor's inner content is empty.