-
Bug
-
Resolution: Fixed
-
Highest (View bug fix roadmap)
-
Archived Jira Cloud
-
45
-
Severity 2 - Major
-
31
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
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.
Environment
JIRA Cloud, version: 1000.656.2 (not available in Affects Version/s field)
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.
Expected Results
User B is notified for issue creation and both comment 1 and comment 2.
Actual Results
User B is only notified on comment 1.
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.
Workaround
From jtillett916844748:
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.
Original comment HERE
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
![[Atlassian Service Operations JIRA]](/images/icons/generic_link_16.png "[Atlassian Service Operations JIRA]")
HOT-56742
You do not have permission to view this issue
-
HOT-58746
You do not have permission to view this issue
- is detailed by
-
JDEV-37843 Failed to load
[JRASERVER-63694] Users are not notified of issues/comments created via Email
| Workflow | Original: JAC Bug Workflow v2 [ 2848285 ] | New: JAC Bug Workflow v3 [ 2929897 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Symptom Severity | Original: Major [ 14431 ] | New: Severity 2 - Major [ 15831 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2591335 ] | New: JAC Bug Workflow v2 [ 2848285 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1635575 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2591335 ] |
| Affects Version/s | New: Archived Cloud Version [ 77301 ] | |
| Affects Version/s | Original: 1000.656.2 [ 66180 ] |
| Remote Link | Original: This issue links to "Page (Extranet)" [ 248213 ] |
| 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 Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-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] |
| Link |
New:
This issue relates to |
| Labels | Original: HOT-56742 affects-cloud ondemand-no-workaround | New: HOT-56742 affects-cloud affects-server ondemand-no-workaround |
| Labels | Original: HOT-56742 affects-cloud affects-server ondemand-no-workaround | New: HOT-56742 affects-cloud ondemand-no-workaround |