Hi ​@AlexCL 

For us to have more info, clarify which Zap action you are trying to use for Jira by posting screenshots as well as screenshots of the configured field you are trying to use.

TIP: Click field labels to see tooltips with more info.

Hi ​@Troy Tessalone :) 

Zap action is Jira Software Cloud > Create issue, the issue I have is when reaching the Configure > Description step, I can’t put [] markdown in the field and get an action element out of it in the ticket created (it’s not translated and stays in text).
 

This should work according to Jira’s markdown documentation https://support.atlassian.com/jira-software-cloud/docs/markdown-and-keyboard-shortcuts/.

Here is some more info about action items in Jira: https://community.atlassian.com/forums/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018

But it’s like some of these don’t work (the same goes for emojis from Jira), which leads me to believe this integration relies on Confluence markup integration instead: https://confluence.atlassian.com/doc/confluence-wiki-markup-251003035.html

Cheers,

​@AlexCL 

The Description field may only accept plain text as part of the Jira Zap app integration for that action.

You may have to explore using the Jira API: https://developer.atlassian.com/cloud/jira/software/rest/intro/#introduction

Make sure the Jira API supports the desired Description formatting.

Zap action: Jira - API Request

Hi ​@Troy Tessalone ,

Description field accepts plain text indeed, but when markdown is used, it works sometimes and sometimes it doesn’t. For instance when creating tables in the same field if I type ||header|cell1| it will create a formatted table. I just don’t get why action items do not work in that same logic while the Jira markdown documentation claims it should.

​@AlexCL 

You can try submitting a ticket with Zapier Support for further troubleshooting and clarification: https://zapier.com/app/get-help