Public case submission seems like it's been marooned by the robustness of the email functionality. The usual life cycle for someone using this is:

1. Start using it.
2. Start getting spam.
3. Stop using it.

Maybe there's a 2.5 step in there where they contact Fog Creek and ask why they're getting spam. Worse yet, there's not a great understanding that selecting "Yes" from the allow public submissions dropdown will allow outside parties to create cases in their FogBugz installation. (I know, it's documented, but users don't read.)

Here's a list of what I think could be done to make this feature something people use on purpose:

• Customizable email response templates
• Show or do not show "Your Cases" section according to global setting
• Shut down public case view after 100 incorrect ticket values, to prevent brute-force attacks
• One-click hide for email addresses to address privacy concerns
• True integration with and potential to limit the form to community users
  • Ability to set permissions such that community users from a given group/client/company can see case status for all cases from their group/client/company
• CAPTCHAs to prevent spamming the form
• Clearer notation that a given case has been submitted via the public web form (rather than Bug posted to website)

Case FC1859902

Edit: I'm making this status-fixed because we have gone a long way to improving this feature with the recently released (7.3.2) community user features. Here's some highlights:

• A few small security features on the form that should drastically reduce bot traffic.
• Ability to restrict the submissions to community users.
• Ability for community users to see their own cases.
• Customizable email response templates.

Public case submission seems like it's been marooned by the robustness of the email functionality. The usual life cycle for someone using this is:

1. Start using it.
2. Start getting spam.
3. Stop using it.

Maybe there's a 2.5 step in there where they contact Fog Creek and ask why they're getting spam. Worse yet, there's not a great understanding that selecting "Yes" from the allow public submissions dropdown will allow outside parties to create cases in their FogBugz installation. (I know, it's documented, but users don't read.)

Here's a list of what I think could be done to make this feature something people use on purpose:

• Customizable email response templates
• Show or do not show "Your Cases" section according to global setting
• Shut down public case view after 100 incorrect ticket values, to prevent brute-force attacks
• One-click hide for email addresses to address privacy concerns
• True integration with and potential to limit the form to community users
  • Ability to set permissions such that community users from a given group/client/company can see case status for all cases from their group/client/company
• CAPTCHAs to prevent spamming the form
• Clearer notation that a given case has been submitted via the public web form (rather than Bug posted to website)

Case FC1859902

Public case submission seems like it's been marooned by the robustness of the email functionality. The usual life cycle for someone using this is:

1. Start using it.
2. Start getting spam.
3. Stop using it.

Maybe there's a 2.5 step in there where they contact Fog Creek and ask why they're getting spam. Worse yet, there's not a great understanding that selecting "Yes" from the allow public submissions dropdown will allow outside parties to create cases in their FogBugz installation. (I know, it's documented, but users don't read.)

Here's a list of what I think could be done to make this feature something people use on purpose:

• Customizable email response templates
• Show or do not show "Your Cases" section according to global setting
• Shut down public case view after 100 incorrect ticket values, to prevent brute-force attacks
• One-click hide for email addresses to address privacy concerns
• True integration with and potential to limit the form to community users
• CAPTCHAs to prevent spamming the form
• Access to the public case submission form while logged in as an admin. Ability to add and remove projects from that interface, or, better yet, the ability to limit public case submission to community users only.
• Disallow signed-in users from using it so there's no confusion with the New Case feature.
• Clearer notation that a given case has been submitted via the public web form (rather than Bug posted to website)

Case FC1859902

Public case submission seems like it's been marooned by the robustness of the email functionality. The usual life cycle for someone using this is:

1. Start using it.
2. Start getting spam.
3. Stop using it.

Maybe there's a 2.5 step in there where they contact Fog Creek and ask why they're getting spam. Worse yet, there's not a great understanding that selecting "Yes" from the allow public submissions dropdown will allow outside parties to create cases in their FogBugz installation. (I know, it's documented, but users don't read.)

Here's a list of what I think could be done to make this feature something people use on purpose:

• Customizable email response templates
• Show or do not show "Your Cases" section according to global setting
• Shut down public case view after 100 incorrect ticket values, to prevent brute-force attacks
• One-click hide for email addresses to address privacy concerns
• True integration with and potential to limit the form to community users
• CAPTCHAs to prevent spamming the form
• Access to the public case submission form while logged in as an admin. Ability to add and remove projects from that interface, or, better yet, the ability to limit public case submission to community users only.
• Disallow signed-in users from using it so there's no confusion with the New Case feature.
• Clearer notation that a given case has been submitted via the public web form (rather than Bug posted to website)

Case FC1859902

Public case submission seems like it's been marooned by the robustness of the email functionality. The usual life cycle for someone using this is:

1. Start using it.
2. Start getting spam.
3. Stop using it.

Maybe there's a 2.5 step in there where they contact Fog Creek and ask why they're getting spam. Worse yet, there's not a great understanding that selecting "Yes" from the allow public submissions dropdown will allow outside parties to create cases in their FogBugz installation. (I know, it's documented, but users don't read.)

Here's a list of what I think could be done to make this feature something people use on purpose:

• Customizable email response templates
• Show or do not show "Your Cases" section according to global setting
• Shut down public case view after 100 incorrect ticket values, to prevent brute-force attacks
• One-click hide for email addresses to address privacy concerns
• True integration with and potential to limit the form to community users
• CAPTCHAs to prevent spamming the form
• Disallow signed-in users from using it so there's no confusion with the New Case feature.
• Clearer notation that a given case has been submitted via the public web form (rather than Bug posted to website)

Case FC1859902

Public case submission seems like it's been marooned by the robustness of the email functionality. The usual life cycle for someone using this is:

1. Start using it.
2. Start getting spam.
3. Stop using it.

Maybe there's a 2.5 step in there where they contact Fog Creek and ask why their they're getting spam. Worse yet, there's not a great understanding that selecting "Yes" from the allow public submissions dropdown will allow outside parties to create cases in their FogBugz installation. (I know, it's documented, but users don't read.)

Here's a list of what I think could be done to make this feature something people use on purpose:

• Customizable email response templates
• Show or do not show "Your Cases" section according to global setting
• Shut down public case view after 100 incorrect ticket values, to prevent brute-force attacks
• One-click hide for email addresses to address privacy concerns
• True integration with and potential to limit the form to community users
• CAPTCHAs to prevent spamming the form
• Clearer notation that a given case has been submitted via the public web form (rather than Bug posted to website)

Case FC1859902

Public case submission seems like it's been marooned by the robustness of the email functionality. The usual life cycle for someone using this is:

1. Start using it.
2. Start getting spam.
3. Stop using it.

Maybe there's a 2.5 step in there where they contact Fog Creek and ask why their getting spam. Worse yet, there's not a great understanding that selecting "Yes" from the allow public submissions dropdown will allow outside parties to create cases in their FogBugz installation. (I know, it's documented, but users don't read.)

Here's a list of what I think could be done to make this feature something people use on purpose:

• Customizable email response templates
• Show or do not show "Your Cases" section according to global setting
• Shut down public case view after 100 incorrect ticket values, to prevent brute-force attacks
• One-click hide for email addresses to address privacy concerns
• True integration with and potential to limit the form to community users
• CAPTCHAs to prevent spamming the form
• Clearer notation that a given case has been submitted via the public web form (rather than Bug posted to website)

Case FC1859902

Public case submission seems like it's been marooned by the robustness of the email functionality. The usual life cycle for someone using this is:

1. Start using it.
2. Start getting spam.
3. Stop using it.

Maybe there's a 2.5 step in there where they contact Fog Creek and ask why their getting spam. Worse yet, there's not a great understanding that selecting "Yes" from the allow public submissions dropdown will allow outside parties to create cases in their FogBugz installation. (I know, it's documented, but users don't read.)

Here's a list of what I think could be done to make this feature something people use on purpose:

• Customizable email response templates
• Show or do not show "Your Cases" section according to global setting
• Shut down public case view after 100 incorrect ticket values, to prevent brute-force attacks
• One-click hide for email addresses to address privacy concerns
• True integration with and potential to limit the form to community users
• CAPTCHAs to prevent spamming the form
• Clearer notation that a given case has been submitted via the public web form (rather than Bug posted to website)