-
Suggestion
-
Resolution: Unresolved
-
5,410
-
471
-
Issue Summary
When email addresses are added to the suppression list, it is needed to contact Atlassian support to provide the list and clear current occurrences.
Workaround
More information on this topic, here: Jira Cloud email notification suppression list and why users don't receive email notification
There are now two self-serve features for removing a user's email address from the suppression list in certain cases without needing to contact Support:
- For new users (who have not yet logged in for the first time) clicking the Resend invite link will remove the email from the suppression list.
- If the user has a verified account (i.e. they have logged into your Jira instance before) and the suppressed email notifications are being generated by a Jira Software or Jira Work Management project, project admins now have the ability to remove the email address from the suppression list using the Project email audit
If the self-serve options are not available to you we recommend creating a Support Ticket with us. For a quick resolution, please include the affected user's email address in your message.
- derived from
-
JRACLOUD-67264 Provide a log for Jira outbound email
- Closed
- incorporates
-
ID-8735 Provide admins with a way to unsuppress email addresses that are not receiving Reset Password email
- Gathering Interest
-
ID-8745 Provide admins with a way to unsuppress email addresses that are not receiving OTP 6-digit verification code email
- Gathering Interest
- is related to
-
JRACLOUD-67264 Provide a log for Jira outbound email
- Closed
-
ID-7791 Allow receiving notifications for when a user has emails blocked.
- Gathering Interest
-
JRACLOUD-84053 Ability to bulk re-send the invitation emails
- Gathering Interest
-
JSDCLOUD-11634 request for resending emails these are blocked by atlassian
- Gathering Interest
- relates to
-
JRACLOUD-75062 To have a log within the cloud site, to give information on emails that get bounced
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...