308556b7edb5 You can use that particular keyword and use as not to send email or auto delete in Automation. In my organization, after lot of struggle our Jira Admins created a different flow in that so that whenever user clicks that button it shows an error.

I would have attached image for better understanding but unfortunately, I am not able to attach image anymore.

I would have helped you better for get going. Sorry.

This causing users to select the incorrect request type within my organizations. Because of this, automations are sending tickets to the wrong queue and causing a giant headache.

forms functionality is not working

For us the biggest reason we do not want users to submit issues directly in a service project is that by bypassing the portal UI the user is not presented the relevant KB articles which might deflect the ticket.

@Jim Bren,

I am not sure if it helps or useful because it uses one complete workflow.

--> Create a Request type as "Task" or whatever is avalaible.

--> Click on Project Settings in the Service Desk Admin

--> Click on Project Automation

--> Create a Rule (as below)

You can also set Transition the issue as Delete. So it will never creates an issue.

I work for a company, so I cannot provide more information but certainly will help if I have that software.

I hope it helps.

@Manu Mitra, would you mind sharing a screenshot of the automation? Sounds like a decent work around.

@Jim Bren I know right?

I have created automation and made that create button useless and an email is sent to them stating "No one is gonna work on this request."

I imagine since this request has languished since 2017, it is pretty unlikely to get done. It'd be nice if you would say no instead of pointing us to a dead feature request. 

When I press the Create button, the screen created by the form's functionality does not load.

Required fields set in the form are not displayed as input fields, resulting in inappropriate requests being submitted.

Yeah we are getting a lot of problems because when JSD agents create issues they usually forgot to set a lot of our custom fields used for our workflows and KPI's