• Type: Bug
• Resolution: Fixed
• Priority: Highest
• Component/s: Notification - Email
• Labels:

  • HOT-56742
  • affects-cloud
  • affects-server
  • jsw-s6
  • ondemand-no-workaround

[JRACLOUD-63694] Users are not notified of issues/comments created via Email

Gabriel Senna made changes - 30/Oct/2023 9:06 AM

Labels

Original: HOT-56742 affects-cloud affects-server ondemand-no-workaround

New: HOT-56742 affects-cloud affects-server jsw-s6 ondemand-no-workaround

Monique Khairuliana (Inactive) made changes - 15/Aug/2019 5:33 AM

Workflow	Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1852301 ]	New: JAC Bug Workflow v3 [ 3353307 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

jonah (Inactive) made changes - 02/Apr/2017 11:32 AM

Description

Original: h3. Summary Users in JIRA are not notified of issues or comments created via email, even if they should. Same users are notified of issues or comments to issues if they are created in UI. We've been able to replicate this consistently in clean instances. h3. Environment JIRA Cloud, version: 1000.656.2 (not available in Affects Version/s field) h3. Steps to Reproduce  # Create a ticket via email using User A (with access) - make sure User B is notified for 'Issue Created'  # Add User B as watcher to the ticket - make sure that watcher are notified for 'Comment created'  ** This is an example, we could also replicate this by assigning the ticket to User B, instead  # Add a comment to the ticket via UI (comment 1)  # As User A send a comment to this ticket via email (comment 2). You can use the notification from comment 1. h3. Expected Results User B is notified for issue creation and both comment 1 and comment 2. h3. Actual Results User B is only notified on comment 1. h3. Notes This is very similar to this bug:  https://jira.atlassian.com/browse/JRA-63582 However, that one is for JIRA Server and for Outlook, so I'm not sure if they are related. h3. Workaround From [~jtillett916844748]: {quote} 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. {quote} Original comment [HERE|https://jira.atlassian.com/browse/JRA-63694?focusedCommentId=1006194&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1006194]

New: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRASERVER-63694].   {panel} h3. Summary Users in JIRA are not notified of issues or comments created via email, even if they should. Same users are notified of issues or comments to issues if they are created in UI. We've been able to replicate this consistently in clean instances. h3. Environment JIRA Cloud, version: 1000.656.2 (not available in Affects Version/s field) h3. Steps to Reproduce  # Create a ticket via email using User A (with access) - make sure User B is notified for 'Issue Created'  # Add User B as watcher to the ticket - make sure that watcher are notified for 'Comment created'  ** This is an example, we could also replicate this by assigning the ticket to User B, instead  # Add a comment to the ticket via UI (comment 1)  # As User A send a comment to this ticket via email (comment 2). You can use the notification from comment 1. h3. Expected Results User B is notified for issue creation and both comment 1 and comment 2. h3. Actual Results User B is only notified on comment 1. h3. Notes This is very similar to this bug:  https://jira.atlassian.com/browse/JRA-63582 However, that one is for JIRA Server and for Outlook, so I'm not sure if they are related. h3. Workaround From [~jtillett916844748]: {quote} 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. {quote} Original comment [HERE|https://jira.atlassian.com/browse/JRA-63694?focusedCommentId=1006194&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1006194]

jonah (Inactive) made changes - 02/Apr/2017 11:32 AM

Link

New: This issue is related to JRASERVER-63694 [ JRASERVER-63694 ]

Confluence Escalation Bot (Inactive) made changes - 02/Apr/2017 12:55 AM

Labels

Original: HOT-56742 affects-cloud ondemand-no-workaround

New: HOT-56742 affects-cloud affects-server ondemand-no-workaround

vkharisma made changes - 01/Apr/2017 7:39 PM

Project Import

New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ]

Marek Piwnicki made changes - 23/Mar/2017 1:32 PM

Confluence Escalation Bot (Inactive) made changes - 16/Mar/2017 4:40 AM

Collapse comment: Roman Lutsiv (Inactive) added a comment - 25/Feb/2017 11:28 AM

Roman Lutsiv (Inactive) added a comment - 25/Feb/2017 11:28 AM

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

Expand comment: Roman Lutsiv (Inactive) added a comment - 25/Feb/2017 11:28 AM

Roman Lutsiv (Inactive) added a comment - 25/Feb/2017 11:28 AM 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

Confluence Escalation Bot (Inactive) made changes - 20/Feb/2017 3:49 AM

Load more older events