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.

Question

Why does the Jira 'add attachment to issue' force a garbage filename?

T

I’ve just spent hours beating my head against the fact that attachments sent to Jira tickets via the published Zapier action were showing up as strings of random characters with no file extension - meaning no preview, no file recognition, and customers in our Service Management implementation can’t see the attachments I thought I was dutifully providing them as part of a Docusign-related automation.

I was ready to blame Atlassian and their API, but it looks like submitting a filename should absolutely be supported - and when I went back and parsed through the ‘Data Out’, it looks like it’s Zapier sending out a random string of garbage as the filename, as opposed to maintaining the file name/extension of what it’s handed (let alone letting you customize!)

 

Can it… not be this way? Please?

Did this topic help you find an answer to your question?

3 replies

P
Forum|alt.badge.img+5

From what I’ve researched, Zapier sometimes generates temporary file identifiers or hashes when it processes files from triggers (like DocuSign in your case). If the action doesn’t explicitly map the original filename—or if the source app provides a file URL without a clear name—it defaults to this random string.

One approach is to grab the file from DocuSign, store it temporarily with a known filename, and then pass it to Jira. Another is to retain the original filenames when attaching files to Jira issues, you can bypass the standard Zapier action and utilize a webhook to interact directly with Jira's API.

T
  • tbennett
  • Author
  • New
  • 1 reply
  • February 26, 2025

I’ve tried inserting (unecessary) Google Drive steps in between, to very deliberately rename the file - Zapier insists on continuing to send a garbage string as the filename even in that instance.

I’ve had to go back to the 3 year old manual Webhook POST method, which does not overwrite the temp identifier, and actually leaves the filename/extension in place, for the moment.

I guess my concern is - why build an ‘official’ action if it does not act as intended and results in a worse experience than the manual method?

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • 7472 replies
  • February 27, 2025

Hi and welcome to the Community, ​@tbennett! 🎉 

I’m so sorry to hear of the troubles in sending files over to Jira. I can only imagine how frustrating this must be, especially after spending so much time trying to find a solution!

I did some testing on my end, and you’re absolutely right—the original filename and extension don’t seem to be preserved when uploading the attachment to Jira. As you’re able to use Webhooks to send the file over and keep the original file name and extension in place this makes me think it’s likely a bug. I’d recommend reaching out to our Support team to confirm that. If it is a bug, they’ll open up a bug report which will flag it to our engineers to be fixed.

Really appreciate you sharing your workaround of using the Webhooks POST action. For anyone that might be running into the same issue, I wanted to mention that the Jira Software Cloud app has Custom Actions and API Request actions available that you could use instead of a Webhooks action—they would automatically handle the authentication for the request which Webhooks doesn’t. 

Keep us posted on what the Support team find and let me know if there’s anything else I can help with in the meantime!

Reply


Terms & Conditions