Introduction
JIRA email notifications have recently experienced inconsistencies for some users, presenting a challenge for efficient workflow management. This article addresses a reported issue where certain users receive detailed JIRA ticket notifications, while others only receive a basic mention alert. We’ll explore the potential causes and provide a solution to ensure consistent notification delivery.
Main Content
The variation in JIRA notification formats stems from several configurable features. Standard JIRA notifications, known as Jira (internal) notifications, are configured by Jira Administrators and cannot be customized by end-users. These notifications are triggered by events and sent to specific users based on a defined Notification Scheme, which can vary across projects. For team-managed projects, the project administrator controls these schemes.
However, JIRA Service Management (JSM) projects introduce a distinction. Customer notifications, sent to clients rather than agents, *are* configurable by the Project Administrator. This allows for tailored content based on user roles – Agents (Service Desk Teams) versus Customers. Furthermore, Automation Rules can also generate emails, adding another layer of potential configuration.
Conclusion
To resolve this discrepancy, it’s crucial to identify whether the affected user is receiving standard JIRA notifications or JSM customer notifications. Confirming the project type and verifying the notification scheme settings, managed by the Project Administrator, will pinpoint the source of the difference. Addressing these settings will ensure all users receive the complete JIRA ticket information they require.
Source: https://community.atlassian.com/forums/Jira-questions/JIRA-email-notification-format-template-has-changed-for-some/qaq-p/2894196
Leave a Reply