I have created an integration between Jira and Monday.com that is intended to send information mostly into Jira. According to the documentation, File columns are supported. Indeed, I’m able to pull up the syncing recipe and see my File column in the Monday.com fields. But there are no Jira fields to map it into. I would’ve assumed it would just go to Jira attachments, but that doesn’t show up in the Jira side of the mapping. It just says “No Options.”
My first instinct is that there is some field type in Jira it’s mapped to that we don’t have enabled, but the documentation doesn’t say what it maps to and nothing stands out to me as accepting files.
You’re right in assuming the File column should ideally map to Jira attachments, but in native integrations or middleware platforms, Jira’s attachment field often doesn’t show up directly in field mappings because it’s not treated as a standard field—it’s usually handled via a separate API call
Instead of trying to map the file in the regular field mapping UI, use a custom webhook or automation step to upload the file as an attachment to the Jira issue after it’s created.
If you’re using Make.com, Zapier, or n8n for this flow, you can use a Get File action from Monday, then pipe that into Jira’s Add Attachment API endpoint.
Most likely, your current setup is only syncing standard issue fields—attachments in Jira need to be explicitly pushed via their REST API and won’t show up in visual mapping tools.
Let me know what integration tool you’re using—happy to sketch out the exact steps or drop a quick Loom if needed!
Hey! Thanks for the quick response. I’m using the native integration provided by Monday.com along with the syncing recipe that comes with that. It says it supports syncing the File type to Jira. If that doesn’t sync to attachments, that’s fine, but where does it support syncing to?
If it supports the File type out of the box, I’d rather not do a custom job. The documentation says it’s supported. The column shows up in the mapping dropdown for Monday. I just need to know what valid field to map it to in Jira.
Monday.com native integration actually handles the “File” column when synced to Jira, since their docs can sometimes be a bit vague. Most often, native integrations don’t push files directly to Jira attachments but instead map them to Jira’s URL or text fields—basically creating a link back to the file stored in Monday.com.
So in practice, you’d want to try mapping the File column to a Jira “Text Field (multi-line)” or a custom field that supports URLs and see how it behaves.
native sync with a lightweight Make.com automation that checks when files are added, grabs the file, and pushes it as a proper Jira attachment. It’s non-invasive, keeps your native setup intact, and gives you exactly what you need if the native integration falls short.