-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
9.0.0, 9.12.8
-
9
-
5
-
Severity 3 - Minor
-
7
-
Issue Summary
The logic that decides whether a mention notification should be sent from a JSM issue when a user does not have application access (no license) is different, depending if batched notifications are enabled or not.
Note: JSM refers to "Jira Service Management"
Environment
- Replicated with JSM 5.12.6, but we suspect that this behavior is replicable in any version from 5.0.0 (and potentially any version from 4.0.0)
- This issue does not occur with Jira Core and Jira Software projects, but only with JSM projects
- In Jira Core and JSW projects, the mention notification will be sent to unlicensed users, whether notification batching is enabled or not
- The Feature Flag mentioned in the KB article Jira notifications (batched and non-batched) not sent anymore to users who don't have application access after Jira upgrade to 8.19.0+ has no impact on this issue, since it does not impact how mention notifications work
Steps to Reproduce
- Setup a JSM application on any version from 5.0.0
- Make sure that Batched Notifications are enabled in ⚙ > System > Batching email notifications
- To speed up the testing process, set batching to 2min
- Create a JSM project
- Create a new user, and don't grant this user application access
- Make sure that this user is granted the browse projects permission in this project (via the Permission Scheme configuration)
- Create a new JSM issue
- Tag the user in this JSM issue
- Wait for about 2min
Expected Results
The mentioned users should receive a notification saying that someone mentioned them in the ticket, as it's the case when Batched Notifications are disabled:
Actual Results
No notification is sent to the user.
Workaround
Grant the user application access (via a license)
Side note
External notification is sent when the ticket is created by the customer via the service desk.
Suggested fix for the bug
Make the behavior consistent across all types of projects, and regardless is the notification batching is enabled or not, by:
- either not sending the mention notification to unlicensed users
- or sending the mention notification to unlicensed users
- relates to
-
BOAR-736 You do not have permission to view this issue
[JRASERVER-77638] Inconsistent behavior of the mention notifications in JSM issues when batching is enabled vs disabled
| Support reference count | Original: 4 | New: 5 |
| Remote Link | New: This issue links to "BOAR-736 (JIRA Server (Bulldog))" [ 982680 ] |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |
| UIS | New: 7 |
| Support reference count | Original: 1 | New: 2 |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Labels | New: boosters |
| Description |
Original:
h3. Issue Summary
The logic that decides whether a mention notification should be sent from a JSM issue when a user does not have application access (no license) is different, depending if batched notifications are enabled or not. Note: JSM refers to "Jira Service Management" h3. Environment - Replicated with JSM 5.12.6, but we suspect that this behavior is replicable in any version from 5.0.0 (and potentially any version from 4.0.0) - This issue does not occur with Jira Core and Jira Software projects, but only with JSM projects -- In Jira Core and JSW projects, the mention notification will be sent to unlicensed users, whether notification batching is enabled or not - The Feature Flag mentioned in the KB article [Jira notifications (batched and non-batched) not sent anymore to users who don't have application access after Jira upgrade to 8.19.0+|https://confluence.atlassian.com/jirakb/jira-notifications-batched-and-non-batched-not-sent-anymore-to-some-users-after-jira-upgrade-to-8-19-0+-1096091978.html] has *no impact on this issue, since it does not impact how mention notifications work* h3. Steps to Reproduce # Setup a JSM application on any version from 5.0.0 # Make sure that Batched Notifications are enabled in *⚙ > System > Batching email notifications* ## To speed up testing process, set batching to 2min # Create a JSM project # Create a new user, and don't grant this user application access # Make sure that this user is granted the *browse projects* permission in this project (via the Permission Scheme configuration) # Create a new JSM issue # Tag the user in this JSM issue !Issue_Comment.png|thumbnail! # Wait for about 15min h3. Expected Results The mentioned users should receive a notification saying that someone mentioned them in the ticket, as it's the case when Batched Notifications are disabled: !NotificationSentWithBatchingDisabled.png|thumbnail! h3. Actual Results No notification is sent to the user. h3. Workaround Grant the user application access (via a license) h3. Suggested fix for the bug Make the behavior consistent across all types of projects, and regardless is the notification batching is enabled or not, by: * either not sending the mention notification to unlicensed users * or sending the mention notification to unlicensed users |
New:
h3. Issue Summary
The logic that decides whether a mention notification should be sent from a JSM issue when a user does not have application access (no license) is different, depending if batched notifications are enabled or not. Note: JSM refers to "Jira Service Management" h3. Environment - Replicated with JSM 5.12.6, but we suspect that this behavior is replicable in any version from 5.0.0 (and potentially any version from 4.0.0) - This issue does not occur with Jira Core and Jira Software projects, but only with JSM projects -- In Jira Core and JSW projects, the mention notification will be sent to unlicensed users, whether notification batching is enabled or not - The Feature Flag mentioned in the KB article [Jira notifications (batched and non-batched) not sent anymore to users who don't have application access after Jira upgrade to 8.19.0+|https://confluence.atlassian.com/jirakb/jira-notifications-batched-and-non-batched-not-sent-anymore-to-some-users-after-jira-upgrade-to-8-19-0+-1096091978.html] has *no impact on this issue, since it does not impact how mention notifications work* h3. Steps to Reproduce # Setup a JSM application on any version from 5.0.0 # Make sure that Batched Notifications are enabled in *⚙ > System > Batching email notifications* ## To speed up the testing process, set batching to 2min # Create a JSM project # Create a new user, and don't grant this user application access # Make sure that this user is granted the *browse projects* permission in this project (via the Permission Scheme configuration) # Create a new JSM issue # Tag the user in this JSM issue !Issue_Comment.png|thumbnail! # Wait for about 2min h3. Expected Results The mentioned users should receive a notification saying that someone mentioned them in the ticket, as it's the case when Batched Notifications are disabled: !NotificationSentWithBatchingDisabled.png|thumbnail! h3. Actual Results No notification is sent to the user. h3. Workaround Grant the user application access (via a license) h3. Side note External notification is sent when the ticket is created by the customer via the service desk. h3. Suggested fix for the bug Make the behavior consistent across all types of projects, and regardless is the notification batching is enabled or not, by: * either not sending the mention notification to unlicensed users * or sending the mention notification to unlicensed users |
| Description |
Original:
h3. Issue Summary
The logic that decides whether a mention notification should be sent from a JSM issue when a user does not have application access (no license) is different, depending if batched notifications are enabled or not. Note: JSM refers to "Jira Service Management" h3. Environment - Replicated with JSM 5.12.6, but we suspect that this behavior is replicable in any version from 5.0.0 (and potentially any version from 4.0.0) - This issue does not occur with Jira Core and Jira Software projects, but only with JSM projects -- In Jira Core and JSW projects, the mention notification will be sent to unlicensed users, whether notification batching is enabled or not - The Feature Flag mentioned in the KB article [Jira notifications (batched and non-batched) not sent anymore to users who don't have application access after Jira upgrade to 8.19.0+|https://confluence.atlassian.com/jirakb/jira-notifications-batched-and-non-batched-not-sent-anymore-to-some-users-after-jira-upgrade-to-8-19-0+-1096091978.html] has *no impact on this issue, since it does not impact how mention notifications work* h3. Steps to Reproduce # Setup a JSM application on any version from 5.0.0 # Make sure that Batched Notifications are enabled in *⚙ > System > Batching email notifications* # Create a JSM project # Create a new user, and don't grant this user application access # Make sure that this user is granted the *browse projects* permission in this project (via the Permission Scheme configuration) # Create a new JSM issue # Tag the user in this JSM issue !Issue_Comment.png|thumbnail! # Wait for about 15min h3. Expected Results The mentioned users should receive a notification saying that someone mentioned them in the ticket, as it's the case when Batched Notifications are disabled: !NotificationSentWithBatchingDisabled.png|thumbnail! h3. Actual Results No notification is sent to the user. h3. Workaround Grant the user application access (via a license) h3. Suggested fix for the bug Make the behavior consistent across all types of projects, and regardless is the notification batching is enabled or not, by: * either not sending the mention notification to unlicensed users * or sending the mention notification to unlicensed users |
New:
h3. Issue Summary
The logic that decides whether a mention notification should be sent from a JSM issue when a user does not have application access (no license) is different, depending if batched notifications are enabled or not. Note: JSM refers to "Jira Service Management" h3. Environment - Replicated with JSM 5.12.6, but we suspect that this behavior is replicable in any version from 5.0.0 (and potentially any version from 4.0.0) - This issue does not occur with Jira Core and Jira Software projects, but only with JSM projects -- In Jira Core and JSW projects, the mention notification will be sent to unlicensed users, whether notification batching is enabled or not - The Feature Flag mentioned in the KB article [Jira notifications (batched and non-batched) not sent anymore to users who don't have application access after Jira upgrade to 8.19.0+|https://confluence.atlassian.com/jirakb/jira-notifications-batched-and-non-batched-not-sent-anymore-to-some-users-after-jira-upgrade-to-8-19-0+-1096091978.html] has *no impact on this issue, since it does not impact how mention notifications work* h3. Steps to Reproduce # Setup a JSM application on any version from 5.0.0 # Make sure that Batched Notifications are enabled in *⚙ > System > Batching email notifications* ## To speed up testing process, set batching to 2min # Create a JSM project # Create a new user, and don't grant this user application access # Make sure that this user is granted the *browse projects* permission in this project (via the Permission Scheme configuration) # Create a new JSM issue # Tag the user in this JSM issue !Issue_Comment.png|thumbnail! # Wait for about 15min h3. Expected Results The mentioned users should receive a notification saying that someone mentioned them in the ticket, as it's the case when Batched Notifications are disabled: !NotificationSentWithBatchingDisabled.png|thumbnail! h3. Actual Results No notification is sent to the user. h3. Workaround Grant the user application access (via a license) h3. Suggested fix for the bug Make the behavior consistent across all types of projects, and regardless is the notification batching is enabled or not, by: * either not sending the mention notification to unlicensed users * or sending the mention notification to unlicensed users |