121
API: get task Description as rich text or Markdown or HTML
Jake Spirek
Currently when you use the API to get a task, you lose all formatting of the Description field.
We need to have options for how to receive that text so it's not lost.
Log In
A
Akkaradech Sreesa-ngar
I Need this feature, too
Oliver
In our space we are using some custom automations for syncing and enhancing different types of tasks, but as of now a lot information is lost in that process and often needs manual rework.
I'd like to see a way to retrieve the fully marked-up task description as well as updating it back.
While standard Markdown might be a quite limited with regards to custom markup (MDX?), HTML on the other and could be too flexible and hard to validate.
For some of our projects we are using Slack's Block Kit API, maybe something similar could be a good fit here.
J
Joseph Ghafari
+1 for HTML for both read and write because Markdown barely supports a portion of the available formatting options.
Also, how is that not a thing already? It should have been baked in from the start. Please ClickUp, let us do actual productive things rather than give us useless features like changing the colour of a list...
F
Felix Schmidt
This is really odd! Need this feature, too
M
Maxime Carrière
Feels kinda weird to be able to update a task's markdown_description field but not read it. This makes updating a task's description via the api impossible without stripping all the formatting.
Aschkan Fardoose
Same issue here
R
Raphael Fritz
This really needs to be fixed, otherwise all the knowledge in Tasks descriptions (e.g. detailled features) is basically lost. Really wondering, why this is not already included. Shouldn't be too hard to just add a field to the api (like "description_formated") as the data is readily available.
Martin Widemann
yeah!
it's essential to pull data from the API as it is.
text is fine, but markdown is required.