Why does a deleted user email fail to be received in a Jira service desk project that has 'Anyone on the web' customer permissions to it?
We have a few people that were not supposed to have Jira users, and have since had them removed. They are to send in tickets/requests by email. However, if they send the email (like other team members do with no issues) their email does not get delivered to the inbox/queue. Even though the email request permissions are set to allow anyone on the web. Also other people within our organization that do not have Jira users are able to submit tickets/request via email. As long as they did not have a Jira user.
Redacted screenshot below.
This is an expected behavior in Jira.
provided the user has a registered jira user account and jira finds the said account, it will reject their tickets because the said user is disabled irrespective of if the ticket is coming to a project that allow any users to create tickets.
The email order is as followed:
As you can see the second step guarantees the user cannot create a ticket.
So to solve the following:
The above makes sure the user the user cannot access JIRA proper due to the lack of a license but the user is still active so (s)he can still create tickets.
But we don't want them to be users because then we have to pay and keep track of them. We have actually removed their user(s) entirely. Shouldn't Jira treat them as any other incoming email in that case or does the email need to be manually scrubbed from Jira's database to fully remove the email so it is not blocked?
This is rather interesting because if tge users have been removed from your user group(confirm that they weren’t just deactivated), then they should be able to create tickets. You can read up on how to delete a user deletion here: https://support.atlassian.com/jira-cloud-administration/docs/deactivate-or-delete-managed-accounts/
On the topic of membership, a user who doesn’t belong in a group that grants access to an Atlassian application would normally not lead to you being billed.
If the issue persists, please raise a direct ticket with Atlassian since they will be the ones in the best position to help with user access related topics due to it user management being hosted by them directly.
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events