Jira to Azure DevOps Description formatting script nt working

General Questions
, , , ,
1

Originally asked by John Muff on 20 April 2021 (original question)

I’m linking Jira Helpdesk Cloud to Azure DevOps.

The link works ok until I add some script to format the Description field from Jira - so it doesn’t look like a single string of text in DevOps.

I’ve added the following lines to my script (I’ve tried a few variations too!):-

Jira.issue.description = nodeHelper.getHtmlField(issue, “description”)
Jira.issue.comments = nodeHelper.getHtmlComments(issue)

When the above is added and I attempt to ‘exalate’ an issue from Jira to DevOps, I just see a message in Jira saying “Waiting for remote”. It never progresses.

What am I doing wrong.

2

Answer by Francis Martens (Exalate) on 21 April 2021

  • When seeing ‘Waiting for remote’ you (or the ADO admin) has to check what is going on on the ADO side. Probably there is some error there.
  • What is the description field renderer on the Jira side - check the field configuration.
    the getHtmlField will only work if the field configuration sets the description field to markdown renderer

Comments:

John Muff commented on 21 April 2021

There is an error on the ADO side and I’ve generated a zip of it. It doesn’t elp me solve my issue though.

The error.csv in the zip contains:-

act_type,connect_remote_issue_urn,creation_date,entity_type,error_entity_type,error_reaction,failed_to_exalate_issues,field_values,id,instance_id,issue_id,issue_id_str,issue_urn,key,relation_id,remote_entity_type,remote_issue_id,remote_issue_id_str,remote_issue_urn,root_cause_detail_text,root_cause_error_type_name,stack_trace,sync_event_id,sync_request_id,trigger_id,users_dismissed

I can send more of the zipped files if required but I note some contain sensitive info.

  • What is the description field renderer on the Jira side - check the field configuration.
    the getHtmlField will only work if the field configuration sets the description field to markdown renderer

I am using this code based on your support documentation here: Converting data between HTML and Markdown in Jira Cloud - Exalate Documentation - Exalate Documentation (idalko.com)

Francis Martens (Exalate) commented on 21 April 2021

That article assumes that the description field renderer is set to markdown.
Is this the case?

Ariel Aguilar commented on 22 April 2021

Hi John,

Let’s say you have Jira = A and Azure = B through a visual connection, you will need to add an extra script with the following to use stripHml on description:

A.issue.description = nodeHelper.stripHtml(B.issue.description)

Let me know if this works for you,

We are still reviewing what should be used for comments and will get you a proper answer.

Kind regards,

Ariel

Francis Martens (Exalate) commented on 22 April 2021

Ariel Aguilar- the question is to format the Jira description such that it presents nicely on the ADO side. The stripHtml will remove any html formatting from the ado description.

John Muff- what is the renderer used on the description field in Jira

John Muff commented on 22 April 2021

Hi,

Thanks for your reply.

I’ve done exactly as you done above and my link still doesn’t work.

I created a new Jira Helpdesk ticket and ‘exalated’ it with the below line in my script:

Jira.issue.description = nodeHelper.stripHtml(DevOps.issue.description)

In the Rules tab of my connection, the Scripts has a red exclamation mark.

The problem with the above though is that Jira uses Markup so I would have though I need to convert the Markup TO HTML rather than strip the html?