makeplane / makeplane/plane

[bug]: Markdown ignored - rendered as plain-text in work items

Open
#8,781 3 comments 0 reactions 3 assignees View on GitHub

@Saurabhkmr98 is already working on this.

Since Mar 24, 2026.

🐛bug plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current behavior

When issues/PRs sync from GitHub to Plane, markdown formatting in the description is rendered as literal text.
The same underlying issue affects manual paste.

It appears that when both text/html and text/plain are present, it consumes text/html first and the tiptap-markdown extension's transformPastedText path is never reached.

Expected: GitHub issue descriptions render with proper markdown formatting in Plane.
Actual: Raw markdown syntax is displayed as plain text.

The topic of broken markdown formatting has been raised since 2023, but I have not found other issues for the impact it has related to the github integration specifically so maybe this is new -- but it makes the github integration unusable.

Steps to reproduce

For GitHub integration:

  1. Connect to github
  2. Sync github Issues / PRs as Work Items
  3. Create Issue / PR in github with markdown formatting
  4. See error

For manual paste:

  1. Copy markdown-formatted text from Github issue
  2. Create a Work Item in Plane
  3. Edit the Work Item description
  4. Paste from your clipboard
  5. See error
Environment

Production

Browser

Google Chrome

Variant

Cloud

Version

v1.2.3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.