Earlier this month, we upgraded our production Jira DC environment from Jira 7.13.11 to Jira 8.5.1. The instance is on the larger end of the scale (14,000 projects, 1.4M issues, ~ 10,000 users in 104 countries) so there were numerous benefits we were looking forward to - such as the Lucene upgrade, CDN, general code improvements - and - batched email. Instead of sending one email for every action in Jira, you can have Jira "wait" for a period of time (say 10 minutes) and any actions in that period for a single issue will be sent in one email (it doesn't combine all actions from every issue in that period, I expect this is due to the ingestion of any replies. If you get an email for issue JIRAPROJ-1 and JIRAPROJ-2 and you reply via email, how will the ingestion system know what issue you're replying to.
Our system was sending out somewhere in the vicinity of 950,000 emails per month. (https://community.atlassian.com/t5/Jira-articles/Maximizing-business-value-from-your-log-files-insights-in-to-app/ba-p/1126471 touches on the monitoring process we use to collect this metric).
After enabling batched emails, we saw a reduction of ~ 25% in email volume.
I noticed on my Facebook feed someone had shared an article on the environmental cost of email/spam - each email sent has a footprint - transmission, processing (anti-spam/virus etc), and ongoing storage etc, so I did some rough calculations.
* This is not meant to be scientific analysis, nor do I want this thread to head to a flame war on climate change science / climate change denial.
** I think my maths is correct, but.... every chance I may have miscalculated somewhere too
*** This also means that the environmental cost of emails (~ 8,550,000 per year) we are still sending out is 34.2 metric tons, or 3.39 drives around the globe.
Craig Castle-MeadCommunity Leader
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