Collapse or remove quoted email history in Email in ClickUp threaded replies | Voters

Collapse or remove quoted email history in Email in ClickUp threaded replies

Nicky Salido

We use Email in ClickUp to respond to customer emails directly from tasks. When replying using the threaded Reply option (replying to an existing email in the task activity), ClickUp includes the full previous email content in the reply body, and there is no option to remove or collapse the quoted history before sending.
This creates a poor experience for recipients in Gmail because the outgoing email becomes very cluttered with repeated prior messages, and Gmail does not consistently minimize/collapse the old content the way it typically does with native Gmail replies.
Current behavior:
Replying from a task via the threaded “Reply” action automatically includes the full prior email chain in the email body.
The composer does not provide a way to trim/remove the quoted text, or to send only the new reply content.
Expected behavior / requested enhancement:
Please add one or more of the following options for threaded email replies:
A toggle to hide/collapse quoted text in the reply composer (and send only the new content).
An option to remove quoted history from the reply body (similar to standard email clients).
A setting at the Workspace or user level such as “Include quoted text in replies: On/Off.”
(Optional) A “Show quoted history” expandable section in the composer UI so it’s available for reference but not sent as clutter by default.
Impact:
Makes external communication harder to read (especially for Gmail users).
Adds noise and can look unprofessional, particularly over long threads.
3 . Forces us to avoid threaded replies, which reduces the value of keeping email conversations neatly threaded in ClickUp.

April 15, 2026

Alexis Fabrigoule

Seconding this. We reproduced it on a fresh thread (3 messages) and compared the raw emails, which points to a root cause: emails sent from ClickUp don't quote the previous messages, they rebuild the whole conversation, and the rebuilt version differs from the originals. Gmail only collapses quoted history behind its expand button when the quote matches what Gmail already has in the thread; ClickUp's rebuild never matches, so recipients get the full unfolded tail.

Concrete differences we verified between the quoted block ClickUp sends and the original messages:

The "On ... wrote:" line is rewritten in a custom format (Gmail's "On Sun, Aug 9, 2026 at 2:40 AM ... wrote:" becomes "On August 9th 2026, 2:41:22 am ... wrote:").
The subject line ("Re: ...") is injected as body text inside the quote.
Original signatures/footers are dropped or replaced (embedded images become broken "http://null" links).
The same message can appear twice in one email, nested copies in different order.
The HTML is malformed (nested <p> inside <p>).

A reply to the same email composed in Gmail collapses correctly because it quotes the original verbatim; the ClickUp reply to it renders fully expanded. This happens on the first reply of a brand-new thread, so thread length isn't the trigger.

Suggested leads for a fix:

Quote the original message body verbatim (exact received HTML) using standard quoted-reply markup, so email clients can collapse it.
Add an option to reply without including the thread history, since the full conversation is already available in the task.
When building replies, don't rewrite the quoted content (headers, subjects, footers), and emit valid HTML.

Context: Gmail integration with "post replies to emails as threaded replies instead of new comments" enabled. The same discrepancy is visible inside ClickUp: received emails render cleanly, with the discussion tail only appearing when we expand "View email", while every email we send shows the entire history pasted directly in the thread panel, which makes the thread cumbersome to read. In other words, ClickUp interprets received emails correctly but not the ones it sends, and recipients also get the full unfolded history. We're on the Unlimited plan (considering Business for custom signatures) but can't commit to it until this is fixed.

Photo Viewer