Links not being parsed with Jira tickets raised by Zapier with new UI

[Dave Tibbs]

We use Zapier to programmatically raise Jira tickets, and in one type of them we're including a URL to our ELK stack, which contains parentheses in it.

Jira's automatic URL parsing wouldn't include the final closing parentheses (which is a common issue) so we got around this by explicitly declaring the link with markdown, which worked fine.

However it appears with the new UI that the markdown links in these tickets created are no longer being parsed and the markdown is being displayed as-is in the ticket description.

Anyone else experienced this and found a solution?

Thanks in advance for any help!

[Shantanu Parashar]

For those still wondering, try 

[{{context.results_link}}]

instead of 

{{{context.results_link}}}

Elasticsearch needs to update its documentation :P 

[Nick_Hebert]

Also struggling to get this to work as well. Would be interested to see a solution to this problem from JIRA. Something so trivial is becoming quite a problem for many.