Servicenow Description field is not getting mapped with Jira description field

[Vishwas Kulkarn]

Hi @Ankur Bawiskar ,

I have a integration with jira, I want to map Servicenow "description" field with Jira "description" field.

below is my ServiceNow "description" field.

The issue is, "description" filed is not geting mapped with Jira because I have multiple line text in servicenow and jira is not taking new line text in its "description" field. If I wrote above text in single line like below it works.

Please find my script include code below.

var createJiraStory = new sn_ws.RESTMessageV2('JiraIntegrationEndpoint', 'Create Issue');
createJiraStory.setStringParameterNoEscape('description', current.description);

Also I have tried with "current.description.toString()" but its not working.

could you please help me in this?

Thank you.

[Mathieu Lepoutr]

Hi Vishwas

I'm working as a pre-sales engineer with Exalate.

Exalate was designed with exactly these types of use-cases in mind, you could say that it is our "bread and butter".

One of Exalate's features, apart from syncing tickets bi-directionally, syncing description from SNOW to Jira.

The ticket with description will out-of-the-box be fully bi-directionally syncronized, which means, if a field gets updated on either side, it will automatically update on the other side, you can change this to make it uni-directional if you so please.

Exalate is easy and straightforward to set-up and you can control exactly which data you want to send and/or receive. 

Cheers

[Eric Smith]

Hi Vishwas. SNOW description is either normal text or in html format while the Jira one is markdown format. Markdown have different syntax for new lines. with some transformation, mapping is possible.

I must admit i've never had such an issue with the mapping. we pretty much skipped this by using a 3rd party tool to carry out the integration process. you can check the solution we used, just for reference. 

[Tim Borquez]

Do you know know how I would go about transforming the new lines?  Like replacing the html new line characters?

Cant use a new solution because everything is already built.  It's just the description field that wont go through 🙁

[svani]

Hi @Tim Borquez ,

I know its very late, are you able to resolve this, we are facing the same issue unable to map the description.

thanks in advance