You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Project Setting ---->Automation-----> Rule is defined in such way that if it Satisfies the certain condition
Email must be triggered , we could not receive an email
This Breaks after the Jira Upgrade.
We apologise that our first description was too brief.
We have recently upgraded Jira from version 8.13.1 to version 8.20.1 (from version 4.13.1 to version 4.20.1 for Service Management).
Yes, the normal Jira notifications get triggered and there is no error in the mail logs.
Previously, we sent a notification to Customer Technical Service by adding a comment with the mention of the Customer Technical Service user account when creating the issue.
We used 2 ways to do this:
However, after migration, these notifications are no longer sent. This is a problem for us because we have contracts with SLAs with our customers.
I created a support ticket here: SDS-62086
Thank you in advance for helping us.
Thanks @NGATDev .
No errors in the script. E-mails are working. So, something in between the script trigger to the e-mai server is not working properly. Suggest to follow up with the support ticket you have.
The only other thing I would try is remove one of the automation setups and add it back and see if that changes anything.
I have seen with Atlassian support team and after many investigations this is related to a know bug JSDSERVER-10909.
If the issue is created on the portal view, the mentioned user is added to the Request Participants and he only receives the notification that tells him he is added to the Request Participants but not the one with the mention.
If the issue is created on the agent view, the mentioned user is not added to the Request Participants and he only receives the notification with the mention.
The fact that the added to Request Participants notification has a link to the portal view of the issue and the notification with the mention has a link to the agent view of the issue seems to be also important there.
I hope the correction of the bug will correct also the notification :)