Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I found this thread but it's already closed: 

The issue is that the description shows like a tree. This form is not allowing me to attach an image, but the Jira description field looks along the lines of:

  • type: orderedList
  • content:
    • 1
      • type: listItem
      • content:
        • 1
          • type: paragraph
          • content:
            • 1
              • type: text
              • content: this is the actual first item of the list

Zapier proceeds to join all these contents by comma “,” which loses purpose. It'd be ideal if Zapier supported passing the full object so that it could be rendered using code, or better yet if such a field was properly rendered as markdown.

Instead, based on that post, I ended up doing something similar. I url encode the description field in Jira automations into a single-line text field:

%23+this+is+the+actual+first+item+of+the+list

This can be then decoded using Zapier text transformation that are free. The only issue with this is that Jira automations trigger two updates in Zapier! (One by the user update, one by the Jira automation) Since the updates reach Zapier in the right order, it doesn't affect the end result, but I end up using twice as many actions just to extract the description.

I guess the alternative is to create an action to pull via webhook the full record in python/nodejs and render it manually there, but it kinda defeats the purpose of the trigger content. 

Hi ​@andras,

 

Welcome to the Community.

 

Zapier combines Jira description fields as a single string separated by commas, which may not suit all needs. Encoding the description into a single-line field and decoding it in Zapier is a clever workaround; it doubles updates and increases action consumption. Though Zapier lacks built-in markdown rendering, feedback on adding this feature has been shared with the product team. As an alternative, pulling complete records via a webhook and rendering them in Python or Node.js is suggested, though it may be more complex. User feedback remains vital to improving the platform. 

 

You may contact Zapier support to request that this feature be added in the future.

Hi Jammer,

Thanks for reading through my post.

I'm not sure which requirements are met with the current behaviour of comma joining an html tree 😉. The description field is not really useable.

Webhook would work, but then again it is an additional task, although it would avoid the double update from Jira.

Thanks again for pushing this to the product team. I'm not sure how often this comes up with other service providers, but two options are:

* Fixing this for Jira with proper rendering

* Provide a serialised version of the trigger object as input. A code step could deserialized this, manipulate it and do other meaningful things as well. Sadly still costing a task at least.

cheers,

Andras

Hi ​@andras,

 

Thank you for your feedback! We're continuously working to enhance our integrations, and your input is invaluable. We'll share your concerns about the HTML tree being joined by commas and the webhook workaround with our development team. Suggestions like improving Jira rendering and providing a serialized trigger object are noted and will be forwarded to the product team for consideration. We appreciate your patience as we strive to improve and welcome any further questions or ideas.

 

 

 

 

Reply


Terms & Conditions