Hello,
We would like to have the option to create a specific form condition for End Users that requires an attachment when a specific field option is selected. I've seen a community post with a coding work around, but we want to avoid this and think it would make more send to have this available as a Condition on a form. Thoughts?
Agreed! I use the workaround but the workaround is quite complicated and if you have many forms that need requirements, it gets messy and confusing in the code as well. I would love to see this supported via the UI, especially given how common a use-case it is for forms.
+1 if we can make this as simple as that then the better.
+1 I have multiple customers who would like to utilise such a feature. Using custom-coded workarounds is tiresome and this should be built-in functionality.
Use case: There are various reasons why an attachment needs to be mandatory for form submission. I've noted a few below as examples from my customers:
-
+1 - definitely a great feature to have. Having the ability to require an attachment based on a field or form selected would be fantastic.
As Amie mentions above, there are a bunch of use cases where documents are required and needing to write custom code to handle this is frustrating.
+1 on this - still no native support for making attachments required on the Submit a Request form as of April 2026.
Running a Help Centre on the Copenhagen Theme with the latest Guide Templating API, this remains a gap. The old jQuery workaround is no longer viable since jQuery was removed in v2 themes, and downgrading isn't an option.
Worth noting that Service Catalog already supports required attachments as of March 2026, so the logic clearly exists within the platform. Extending this to standard ticket forms and form conditions feels like a natural next step.
Would love to see this on the roadmap!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.
Thank you again for your feedback and for being a valuable customer with Zendesk.