Format description text (REST API)
Hi
I'm using the Rest API to create ticket issue.
I was wondering how can I do to format the desciption text accross the Rest API.
I just need the carriage return to structure the description otherwise it's unreadable (<br/>).
The system does not accept HTML.
Cheers
Alain
I'm using the Rest API to create ticket issue.
I was wondering how can I do to format the desciption text accross the Rest API.
I just need the carriage return to structure the description otherwise it's unreadable (<br/>).
The system does not accept HTML.
Cheers
Alain
Please sign in to leave a comment.
Do you know if this list of Wiki markup is full ?
Have tried "\n\r", I pretty sure you can't transfer carriage return or any none alphanumeric character.
I can send only printable characters.
Same here. You can't sent newline in GET request. We could do it with POST most probably.
Besides I think that GET request limits the length of query string.
Notice that POST will return a bit different response then PUT.
I am sorry to resurrect this old issue, but I was not able to find the information I seek otherwise (and link to this issue came up quite high in my Google search).
I am looking for a way of formatting the issue description using the current Markdown support in YouTrack. AFAIK there are two flavours of markdown, one that was used at the time of writing the original post here, the other that is used now (and that is consistent with Common Mark). However, using REST API, I can still only use the old markup format. Is there a way to change this behaviour?
Hi!
I'm Sergey from the YouTrack team.
There are Markdown and Wiki. This thread is about Wiki syntax. We deprecated Wiki syntax a couple of years ago. Yet, we continued to render Wiki for old content for a while, and it was available in the REST API. In the recent 2022.2 update, all the Wiki parts were removed from the codebase completely.
So please upgrade to the last build of 2022.2 version, and you will only have the Markdown option by default.
Many thanks Sergey for your quick answer.