Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

When copying card text from JSON and inserting into Card, newlines are not converted

Svend Koustrup
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 12, 2023

When user "A" has a previously edited but unsaved card description, and in the meantime user "B" updated the card description, then when "A" clicks the Save button, "B"'s edit is overwritten.

When this happens, my colleagues come to me and I have to dig into the JSON for the previous edit description.

I can take this markdown'ed description and paste directly into the Trello card which works great for the markdown formatting, but newlines, formatted as "\n" in the JSON text, is not imported as newlines but rather literally as "\n".

So I have to insert the JSON text into a text editor and replace "\n" with actual newlines, and then copy this text into the Trello card description field.

2 wishes from me:

  1. If I have an unsaved description field in a card, when the user hits the Save button, please check if anyone else have made any updates. Maybe even provide a diff viewer for the user, so it's visible what the user have changed since the version this user had when he made the edit, but also what edits (an)other user(s) have made. But at least warn the user that someone else have made changes as well, if you really want to overwrite this.
  2. When entering (pasting) text into the Trello Card description field, please translate "\n" to newlines.

Best regards,


1 answer

0 votes
Cody C.
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 14, 2023

Hi Svend - sorry for the trouble, and thank you. I can see where there could be some improvements with the description history in Trello and I'm glad to pass a vote for that along on your behalf, as well as the observation about newline characters.

While I can't necessarily promise movement on those, I can definitely mention those to the product team on your behalf.

For now, it sounds like you're on the right track with your workaround, that's the best option I was able to come up with as well.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events