# Code Insight report newline

**URL:** <https://community.developer.atlassian.com/t/code-insight-report-newline/37730>\
**Category:** Bitbucket Server\
**Tags:** code-insights\
**Created:** [April 27, 2020, 3:37pm UTC](https://community.developer.atlassian.com/t/code-insight-report-newline/37730 "2020-04-27T15:37:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahsberg](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ahsberg/32/39762_2.png) [@ahsberg](https://community.developer.atlassian.com/u/ahsberg)\
**Post date:** [April 27, 2020, 3:37pm UTC](https://community.developer.atlassian.com/t/code-insight-report-newline/37730/1 "2020-04-27T15:37:01Z")

</div>

We have an issue when we are creating a Code Insights report for our pull requests.

According to the API documentation only raw strings are allowed in the description fields, with the addition of new lines.

> This string may contain escaped newlines and if it does it will display the content accordingly.

However, there is lacking documentation on what this escaped newline is since neither `\n`, `\\n`, `<br>` or html escaped newlines variants are working.

All our attempts will only render a single line with content regardless of what escape character we are using. Please can you give some advice here?

See: [REST Resources Provided By: Bitbucket Server - Code Insights](https://docs.atlassian.com/bitbucket-server/rest/7.1.1/bitbucket-code-insights-rest.html#idp9)  
We are using Bitbucket Server 7.1.1

---

<div class="post-metadata">

**Author:** ![ChristopherKochovski](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@ChristopherKochovski](https://community.developer.atlassian.com/u/ChristopherKochovski)\
**Post date:** [October 19, 2020, 5:34am UTC](https://community.developer.atlassian.com/t/code-insight-report-newline/37730/3 "2020-10-19T05:34:55Z")

</div>

Hi @ahsberg,

I am a developer on Bitbucket Server and upon consulting with another developer on the team there appears to be a bug unfortunately.

You can follow the ticket at [BSERV-12633](https://jira.atlassian.com/browse/BSERV-12633) to track the progress.

Kind regards,  
Christopher Tom Kochovski