Open issuesSwitch filter

In our migration there were some issues with groups and number of licenses so our around 1100 users all got around 7 e-mails from "an unknown asking them to join a SAAS service" - this is exactly what our Security department is requesting people to not accept and to report (i.e. external mails with links asking you to "join" something)...  

I estimate about 5 hours of unnecessary communication for this. I guess if you multiply that with number of migrations it would make a great business case for your customers?  

When we do a User Clean Up, admins receive COUNTLESS notification mails! Please prioritize this

CES-49538 - User is a site admin and I have been receiving emails from Atlassian intended for system administrators. Need a feature to disable the notifications for the single user with admin access 

Sign me up as soon as this becomes available.

Hi everyone, I'm sharing this post that was previously added on the related ticket JRACLOUD-1369 – Reduce JIRA email chatiness as it may be of interest to watchers of this ticket:

We are excited to be launching an Early Access Program (EAP) for some new changes we plan to introduce to help tackle the Jira email chattiness issue, and would like to invite all Jira Cloud admins to join our EAP. By participating, you'll have the opportunity to test out the new changes firsthand and provide us with valuable feedback to help shape the final version of this feature.

For more details and to sign up for the EAP, please refer to our community article.

THIS IS HUGE! This is an HR issue, Project Administrators are GETTING THESE notifications WHY!? Someone completely irrelevant to a project is removed and all the Project Admins get notified....this makes no SENSE! This is a violation of confidentiality from an HR perspective why is this not addressed?

Myself and our other org admins should at least be able to unsubscribe from these alerts. The emails are so SO annoying, and just fill my inbox. Hell, even in Jira you'll get 1 email if multiple changes are made within a short period. Can you really not do the same with Atlassian?? 1 Email with a summary of changes made within a short period?

It is definitely important to have the option of being able to delete managed accounts in bulk and not have to use the API, as well as the option to disable users of deleted accounts from being notified by email.

It is false that when the account is deleted via API, no mail arrives. I executed a process to delete several accounts and they all received the deactivation email and the 14 days.

We did a cleanup (deletion) of leftover 30.000 users in our ORG, and we have 50 ORG admin, this resulted in 1.5 Mio emails in a short time, so the sending email domain am.atlassian.com was blocked by our mail servers, unnotices by us. After we got the server unblocked, a few days later Atlassian sent reminders to users and ORG admins, so server was blocked again. And in 3 days users are finally removed, so this will happen again, and again, and again ...

Same domain is used to send verification emails to users on login, so that users were not able to login for a few days (weeks).

If the flooding of email blocks the domain, our ORG admin do not get all those information emails - but really, who reads 30.000 emails as admin? We just delete them, and if we need something, we look into the audit log. Small companies might do it different, but we have 50.000+ users - I get hundreds of emails which I delete per mail filter.

Atlassian suggests to use the User provisioning API to avoid that emails, but there I can only deactivate users, not delete them. To delete them, I have to go to ORG API (Atlassian directory, not Identity Provider): "To delete a user's Atlassian account from your verified domain, delete the user from the Atlassian directory in your organization.", so this will again trigger emails. Source: https://support.atlassian.com/provisioning-users/docs/understand-user-provisioning/

So this all is not only about getting too many emails (which we can filter per rule), it results in users not being able to login due to mass email flooding in our servers. Not sure what bigger services like M365 would do - if you are on the black list there, this will also affect other companies, not only the one causing the mail flood.

There are ways around it, but they take time (e.g. claiming more domains and maybe making user managed users which we did not want to manage and keep them in the org forever or delete them in much smaller chunks over a longer time). As Atlassian sends emails again some time later to inform about upcoming deletion, it is also not a solution to remove the Org Admin roles during deletion to reduce the number of users who get emails - we cannot keep them out of their role for weeks.

There must be way introduced to define to whom and when such emails are required to send.

And please explain in detail when which emails are sent to whom, including when emails are sent to ORG admins, so we can prepare in advance.

Boston College is looking into a Google Mail Routing rule to stop these messages from reaching user mailboxes.  Has any one done this? If yes, are you able to share the format of that routing configuration?