We need this option available asap. It is not a suggestion, it is a gap in product functionality at a base level. How much effort is it to create a method to "Submit as guest? with an optional email field - if they want to follow the ticket or receive notifications.
The purpose of the "email confirmation to" field is for establishing communication with the customer....so when I disable ALL customer notifications (logically thinking through this) the email field is still required...makes no sense.
Submit as Guest, submit anonymously, etc. this all works through email requests, so why can the same function not apply to portal requests?
Or allow us to edit the description of the field so we can have a generic email there for the reporter to paste in IF they do not wish to create an account.
Having no options around this is crazy. Having this open for almost 5 years with no single shred of resolution or workaround, is crazier.
Can we vote for Atlassian to stop creating siloed features and apps, baking everything behind premium access, and focus on making the Core products we actually purchased (and what drove us to JSM in the first place) better?
We need this option available asap. It is not a suggestion, it is a gap in product functionality at a base level. How much effort is it to create a method to "Submit as guest? with an optional email field - if they want to follow the ticket or receive notifications.
The purpose of the "email confirmation to" field is for establishing communication with the customer....so when I disable ALL customer notifications (logically thinking through this) the email field is still required...makes no sense.
Submit as Guest, submit anonymously, etc. this all works through email requests, so why can the same function not apply to portal requests?
Or allow us to edit the description of the field so we can have a generic email there for the reporter to paste in IF they do not wish to create an account.
Having no options around this is crazy. Having this open for almost 5 years with no single shred of resolution or workaround, is crazier.
Can we vote for Atlassian to stop creating siloed features and apps, baking everything behind premium access, and focus on making the Core products we actually purchased (and what drove us to JSM in the first place) better?