Preventing new tickets by email, but allowing responses to notifications

[Angie Thompson]

Good afternoon.

My question is, is it possible to prevent Jira users from raising new tickets by email, while allowing users to respond by email to a ticket notification? 

What we're looking to achieve is a portal-only ticket creation channel, while still allowing users the ability to respond to notifications they are sent on existing tickets by email and have those responses create comments on the ticket. 

Can you have one without the other? 

I can see that this question has been raised previously, link below, but the solution mentioned does not work. 

https://community.atlassian.com/t5/Jira-Service-Management/Email-Requests-Prevent-New-Tickets-Via-Email-BUT-Allow-Responses/qaq-p/2058919?utm_source=dm&utm_medium=unpaid-social&utm_campaign=P:online*O:community*I:social_share*

Thank you 

[Chad Jackson]

Looking to do something similar, where only certain System accounts are allowed to create new e-mail Issues. In theory it should limit all e-mail generated issue unless the e-mail comes from Email1,2,3 or 4. Leaving the rest of the system open for issue updates etc.

Curious what others have to say on this subject, we are a few months out from  being able to lock down e-mail issues.

[Soto_ Jose]

Hi Chad, 

Have you found a workaround for this? I was able to achieve this via an automation, but I can't make exceptions. In other words, I want to allow certain services to email in tickets such as monitoring services that would alert us about workstations running out of hard drive space etc, but block it for all users so they would be forced to login to the Jira Portal to submit tickets and include all the necessary details.