We are setting up automatic bug report creation in Jira directly from Intercom using the official Jira for Tickets app with custom automation (Workflows). We would like to achieve this using only Intercom’s built-in tools, without relying on third-party integration services (like Zapier/Make) or a custom backend.
Everything works great, except for one thing: screenshots and files attached to the Intercom ticket are not being transferred to the newly created Jira issue.
Questions:
Is the ability to transfer attachments on the roadmap for the Jira for Tickets app, and is there an estimated timeline for this?
Is there currently any workaround using built-in tools (Workflows / Data Connectors) that we might have missed?
Thank you!
Best answer by Nathan Sudds
@NikolaiUtorg We are currently answering your question on the Fin Community Office Hours you can find out more by watching the replay -- but there’s two things that came up, one is that if the attachments are in a Private Note that’s a known issue.
You may also want to check if the types of attachments are whitelisted in your Intercom setup, what type of file types were they?
Also this may be something you could solve as you mentioned in #2 -- making a dataconnector but I’d recommend doing this with a procedure, and then use a data connector to accomplish this and create the ticket.
Claude is your friend in this case as well with the Intercom MCP to investigate things and make a data connector.
Hope this helps -- normally we would recommend using a 3rd party tool but you specifically said you didn’t want that.
Join to hear more about the options from me @Roy and @Aleksei O
@NikolaiUtorg We are currently answering your question on the Fin Community Office Hours you can find out more by watching the replay -- but there’s two things that came up, one is that if the attachments are in a Private Note that’s a known issue.
You may also want to check if the types of attachments are whitelisted in your Intercom setup, what type of file types were they?
Also this may be something you could solve as you mentioned in #2 -- making a dataconnector but I’d recommend doing this with a procedure, and then use a data connector to accomplish this and create the ticket.
Claude is your friend in this case as well with the Intercom MCP to investigate things and make a data connector.
Hope this helps -- normally we would recommend using a 3rd party tool but you specifically said you didn’t want that.
Join to hear more about the options from me @Roy and @Aleksei O
Did Nathan’s private-note and file-type checks explain the missing attachments in your setup? To narrow this down without adding another integration service, I’d test the same harmless sample file in a public reply and a private note on a test ticket, then compare what reaches Jira. That would help distinguish a source-location limitation from a file-type problem.
I’d also check that the engineering user can open the evidence, rather than just checking that a link appears. If neither route works, an explicit missing-evidence flag would at least prevent the escalation from looking complete while the native limitation is investigated.