-
Suggestion
-
Resolution: Low Engagement
-
None
-
2
-
When performing several changes in an issue through a screen (like the Edit screen), this might trigger several notifications at the same time for the same user, this notifications reach the Mail Queue and , at the time of flushing the mail queue, JIRA follows some unclear rules to create one consolidated notification containing all of them (it seems to appear as a new notification with an 'envelope' icon screenshot-1.png
, but this is purely a conjecture and it might be just JIRA indicating that it is flushing the notifications one by one) using one of the notifications to be the 'title' (like 'Assigned' or 'Updated') but will also include all the other changes made in it.
When multiple notifications for the same user are in the Mail Queue, by testing it seems the current behavior to choose the 'title' is:
- If an "Issue Assigned" is among the notifications, it is chosen to be the title.
- If there is no "Issue Assigned" notification, an "Issue updated" notification will be sent with all the changes.
- For some reason, if one of the changes made is Work logged added, it triggers a completely separate notification in adition to the "assigned" or "updated" notification, and might even contain changes that are alread included in them ( see example, the due date and assignee change ware included in both notifications screenshot-2.png
) - Comments added through a screen do not trigger the "Commented notification" nor are included in the list of changes made.
The suggestion is to make a dedicated documentation page for the JIRA Mail Queue (as there is none to be found at the moment), including the rules and priorities for the notifications.
Notes:
- All the tests were done using the 'Reporter' as test subject. All changes to the issue were done by an admin user.
- The test was done in clean JIRA Software Server 7.3.8 and 7.4.0.
- Changing the order of the fields in the screen does not seem to affect the behavior.
- is related to
-
- Gathering Interest
[JRASERVER-65718] Document how Mail Queue works, including how JIRA prioritizes notifications when more than one is triggered for the same user ( like in Edit issue)
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Labels | Original: Notifications | New: Notifications cleanup-seos-fy25 |
| Workflow | Original: JAC Suggestion Workflow [ 3054064 ] | New: JAC Suggestion Workflow 3 [ 3683805 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2619352 ] | New: JAC Suggestion Workflow [ 3054064 ] |
| Support reference count | Original: 1 | New: 2 |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2592880 ] | New: Confluence Workflow - Public Facing v4 [ 2619352 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2415784 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2592880 ] |
| Support reference count | New: 1 |
| Description |
Original:
When performing several changes in an issue through a screen (like the Edit screen), this might trigger several notifications at the same time for the same user, this notifications reach the Mail Queue and , at the time of flushing the mail queue, JIRA follows some unclear rules to create one consolidated notification containing all of them (it seems to appear as a new notification with an 'envelope' icon [^screenshot-1.png] , but this is purely a conjecture and it might be just JIRA indicating that it is flushing the notifications one by one) using one of the notifications to be the 'title' (like 'Assigned' or 'Updated') but will also include all the other changes made in it.
When multiple notifications for the same user are in the Mail Queue, by testing it seems the current behavior to chose the 'title' is: # If an "Issue Assigned" is among the notifications, it is chosen to be the title. # If there is no "Issue Assigned" notification, an "Issue updated" notification will be sent with all the changes. # For some reason, if one of the changes made is Work logged added, it triggers a completely separate notification in adition to the "assigned" or "updated" notification, and might even contain changes that are alread included in them ( see example, the due date and assignee change ware included in both notifications [^screenshot-2.png]) # Comments added through a screen do not trigger the "Commented notification" nor are included in the list of changes made. The suggestion is to make a dedicated documentation page for the JIRA Mail Queue (as there is none to be found at the moment), including the rules and priorities for the notifications. Notes: * All the tests were done using the 'Reporter' as test subject. All changes to the issue were done by an admin user. * The test was done in clean JIRA Software Server 7.3.8 and 7.4.0. * Changing the order of the fields in the screen does not seem to affect the behavior. |
New:
When performing several changes in an issue through a screen (like the Edit screen), this might trigger several notifications at the same time for the same user, this notifications reach the Mail Queue and , at the time of flushing the mail queue, JIRA follows some unclear rules to create one consolidated notification containing all of them (it seems to appear as a new notification with an 'envelope' icon [^screenshot-1.png] , but this is purely a conjecture and it might be just JIRA indicating that it is flushing the notifications one by one) using one of the notifications to be the 'title' (like 'Assigned' or 'Updated') but will also include all the other changes made in it.
When multiple notifications for the same user are in the Mail Queue, by testing it seems the current behavior to choose the 'title' is: # If an "Issue Assigned" is among the notifications, it is chosen to be the title. # If there is no "Issue Assigned" notification, an "Issue updated" notification will be sent with all the changes. # For some reason, if one of the changes made is Work logged added, it triggers a completely separate notification in adition to the "assigned" or "updated" notification, and might even contain changes that are alread included in them ( see example, the due date and assignee change ware included in both notifications [^screenshot-2.png]) # Comments added through a screen do not trigger the "Commented notification" nor are included in the list of changes made. The suggestion is to make a dedicated documentation page for the JIRA Mail Queue (as there is none to be found at the moment), including the rules and priorities for the notifications. Notes: * All the tests were done using the 'Reporter' as test subject. All changes to the issue were done by an admin user. * The test was done in clean JIRA Software Server 7.3.8 and 7.4.0. * Changing the order of the fields in the screen does not seem to affect the behavior. |
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center