Hi ialexeyenko, I am not sure if you are able to pick up the Cloud fix because there were multiple changes to emails sending functionality for Vertigo, but here are fix PRs:

• PR1
• PR2
• PR3

I'd recommend talking to bkelley@atlassian.com who implemented majority of email changes for Vertigo if you need a context behind these fixes. Thanks

Resolved for us as well. Thanks!

We are experiencing the same issues per JRA-63582, but we are running on premise JIRA server 7.2.0.  I don't see this issue listed in bug fixes for 7.3.  Is there a fix for on prem?

thanks

The issue with email notifications not sent on adding issue comments through email is resolved now. The fix is available for all customers.

Looks like the email notifications aren't going out right away...there are some delays in some cases. I'm assuming this is still being worked on? An official update would be nice. 

Looks to be good for us too!

I think this may be fixed - but I'm waiting on an update to this ticket. I've tested various scenarios (submitting ticket via email, via JIRA platform, commenting via email/platform) and we've received notifications. 

Please provide a confirmation if this has been fixed?

Yes, this is greatly affecting our turn around on tickets and customers are noticing. If it helps to research it, only our 2 newest JIRA users are affected. Everyone else, created earlier are ok and receiving notifications. 

Hi guys,

you might not be aware but this bug has critical effects on some cloud customers as they handle their first level support (or similar) with their clients via JIRA and not getting notifications about new tickets results in slow response times thus broken SLAs.

We do have one customer of this case at the moment and I can see their frustration with this bug. Please fix this asap.

Kind regards,

Chris

Same issue here with the addition that issues created automatically with the "Automation for JIRA" add-on, also do not send email notifications.

Same issues.

We are experiencing the same. Issues are being missed. Please fix.

any news?

We are having this issue as well. Some agents are informed and others are not.

We are experiencing this issue as well. Please prioritize as this is seriously hindering our workflow!

We are experiencing this as well. So far, only 2 users on 2 tickets have been affected. The tickets were created via email, and the comments are also being created via email. Watchers and assignees are not notified of new comments. 

Semhal's last comment makes things more clear for me. I have not tested that scenario. 

Updates and comments submitted via email are not creating notifications for us as well. 

I am definitely seeing non-notification on both comments and creates using JIRA OnDemand.

Updates/Comments don't appear broken for me, only issue creation notifications.

Note:  Workaround only works for New ticket creation and not the Updates/Comments that are made via subsequent email response. 

Not sure if this helps but on the Ticket I submitted outside of this one to JIRA I asked the resolution time frame... The following is the answer I received. 

Felipe van Schaik Willig

10/Jan/17 8:57 AM
Hi, Kari.

There's no public ETA at the moment, but the fix is already merged and it will de deployed to the staging environment tomorrow, so the prod environment should be getting this the next day, that is by Thursday or Friday.

-Felipe

Thank you Jeff. The workaround works. Mine fires every 5 minutes. The notification is not pretty but at least it's something.

Atlassian guys what will it take for you to fix this ASAP?

I also created a custom event, and that event is not firing on issues created via email either. It appears that the root cause is triggered events not firing on issues created from email. With the time of this correlating to the release of the ability to easily create tickets from AGILE boards, I would say the bug is in the issue creation code stemming from the new feature. 

Can anyone confirm if the notifications fire when you do a quick create from a board?

FYI, a workaround would be to create a filter to look at issues created in the past 15 minutes and create a subscription to fire every 15 minutes. Dirty, but it's something.

Not receiving any notifications for new tickets to our internal support group of agents, and not receiving any customer update notifications, causing work flow issues,

This is causing a critical issue to business workflow for us - please fix ASAP

Posted details on reproducing here:

https://answers.atlassian.com/questions/45972479/project-role-members-not-being-notified-of-issue-created-event

You all haven't learned that Atlassian doesn't care one little bit about their cloud customers?  They talk a good game about trying to build their cloud services, but any time there is an issue with cloud products they don't bother to help.  See the many year old JIRA ticket about getting CNAME's for cloud products; they don't care.

Critical issue for us as well. So many of our departments rely on this for daily workflow.

This is impacting my response times because issues are being missed.  It is mission critical for my team to be notified!  Please advise ASAP.

Is anybody from Atlassian listening??? This is no doubt a critical issue turning into a blocker for most of your users.

Our developers have also reported starting around 1/5/2017 that they are not receiving notifications of comments and issues created via email sent to our Atlassian cloud account resulting in untimely response to critical issues this is above a High priority to our organization as our projects and workflows depend heavily on communication through email.

We really need a release date on this issue. It impacts our change policy, our help deck, all of our workflows and our critical lines of business. What is the time frame for resolution?

Hello I am the winner of the game number 182 I have won 37 weapons yet come to me The exchange offer was not taken and 20 hours passed

Hi, we are also experiencing this. It's very important to the business that we get this resolved as soon as possible. 

We are also having the same issue. Please fix this ASAP. This is very critical.

This issue is also affecting us and is a critcal (if not blocker) issue for us. 

pascal.mielke738489501: This is the same issue indeed. It was already mentioned in the title but now I have updated the description (summary) to make it clear.

Thanks,
Dario

This is far more important than a High issue.  This is a blocker/critical/firm breaking.  

We can no longer count on JIRA to help us run our business.  The business workflows we have built for our firm are now broken, and we will move many of them away from JIRA since JIRA cloud is no longer dependable.

This is a crucial bug of enormous import.  

Please fix this. Issues are being missed because no one is being alerts. This is a massive problem. 

In your reprouction about tjis error you explain it with a comment via eMail. Is it the same with the creation of a issue via eMail. Thats sounds like about your Topic!?

I second the request for this to be urgently worked on. We are greatly impacted by this today.

Please arrange for immediate fix, this affects massively our work