Is anyone monitoring this?  This is a big deal.

We are looking forward to it as well.

Any progress being made on this?

We need this for validation of an "email" field, please.

Ideally, we could enter a regular expression that needs to be match/not match before the input is accepted. 

Very surprised this doesn't have more upvotes, we require this for email, phone number, and address.

Same here we need validations on fields too, such as email

+1 in voting

We have an email filed. We want to add format verification to make sure that user entered a valid format to make it works from UI and REST API both

It's very important. For example:

• I want to have two request types: Report a Problem and Report a Bug Found during Testing. When someone raises a Problem I do not always know all the details in the first place so I need this form to be well developed. But when someone is testing my application I exactly know which version and settings he has, so I can prepare a very short form (without version number, settings etc.). But I have to prevent all the customers to raise bugs by this second option. Then I will have a validator like put your test number and then you can raise the ticket
• You cannot decide that the people from your organization can view more request types in the Portal then normal customers. But I would like to have some special ones. Because I want customers to raise tickets for bugs in my SD, but not in JIRA Software. Then I can set a validator that if a customer is in my organization or has a JIRA software access, can raise a ticket for JIRA also

Hi,
Today we are using JIRA Service Desk at my company and are in need of this specific function. We have a specific list to verify if a user is allowed to submit specific requests. I would like to have a custom field in the Service Desk Portal when users submit issues and improvements. This field should be mandatory and compare the input to a specific list. Example:
1. User has a problem with our SW and goes to the support portal
2. He/she selects to report a bug in the system and is taken to the fields needed to be filled out when submitting this bug (description, priority etc.) On this screen there is also a "Licence number" field.
3. The user needs to fill in their licence number for that specific product.
4. Number is compared to an internal list (not visible to customer) and if valid the issue can be created, if not it should not be possible to continue submitting issue.

We need this because there could be many customers and licences, some might not have been renewed and therefore they are not entitled to support. This is a requirement for us to have, else the support will not be correct and we might need to change support system. In other words, it is crucial we have this functionality.

You have a SEN field, seems like this is what we need.