Issue Collector: Can 'Name' and 'Email' be made required fields?

Hi all,

We use JIRA's Issue Collector as a support tool, where all of our customers can create/raise issues and/or feedback. We are using a single user license, which all customers go through via our single Issue Collector. We have found that some end-users are submitting issues without entering their name or email address, so we don't know which of our customers it came from. This is a problem, as it is embarrassing to call each customer, until you find the right one. :) Is it possible to make the 'Name' and 'Email' fields a requirement? the 'Summary' field.

Thank you.

4 answers

1 accepted

This solution is not tested for JIRA On Demand. However, we successfully implemented this for JIRA Download.

We faced a similar situation where we wanted to make the Name and Email field mandatory. Our work around was to add custom fields for Name and Email and make those mandatory in Issue Collector.

Issue collector does not seem to let you remove the default Name and Email fields. We got around that by hacking the issue collector plugin jar to modify the velocity template lines that display those fields.

The highlighted lines we removed from the velocity template in templates/collector/contactform.vm to get rid of the default Name and Email fields:

After modifying the issue collector jar we reuploaded it from the install new plugin page in JIRA administration.


Based on this information we have attempted to do the same thing but the Name and Email fields are still displayed (when previewed in the Issue Collector admin). Would you expect them to disappear from here too?


I too have attempted to use this workaround and have the same experience as mother-goose in that the fields are still displaying in the issue collector forms. How are you repackaging the jar file after editing the contact form?

I have JIRA On Demand, we really need to be able to make these fields required. I tried a custom field but with On Demand we have no access to the code and thus can not do the solution above. Is there an alternative?

1)-There is no need to remove the default email and name fields which have useful functionality attached to them within the system. Instead, hack the collector by simply adding the HTML required attribute to both tags. It's the simplest solution.

2)-To unpack and repack jars you need to install the jar utility.

jar -xvf file.jar

jar -cfv newjarfilename.jar <directory, path or file(s) to repack>

See the full answer here:


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,755 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot