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
Here's what I have done to stop those annoying Resolved-2-Closed email notifications:
I wish I could just remove post function #5 and hopefully the above solution did not break anything else.
Hi @Marek and welcome to the Community!
If you are simply trying to disable the notification that is generated when the issue moves from Resolved (or Canceled) to Closed, the solution given to me by Support was to disable "Customer-visible status changed" in the project's Customer notifications settings.
This will turn off any status change notifications that do not include a public comment, such as Reply to customer.
If this answers your question please consider marking the answer as Accepted, as this will help others find the solution in the future!
@kees.van.leeuwen After I did step 1-3, notifications for Closed cases ceased.
Are changes being made on the issue still after closure?
Cause then it is linked to the issue updated part. (and might be a best practice to restrict that).
Then if they are watchers or the assignee they will still get them when the "Issue Updated" is triggered.
Issue Closed will only handle the transition towards the Closed status.
Do you see what email they get exactly? Is is a notification template you can relate back to a specific action?
It can also be that you have a "Send Email" postfunction on the Transition to Closed (which is then not handled by the notification scheme) depending on whether you have some apps able to send emails.
All that that rules does it move the issue to the "closed" status. This doens't send email on its own.
The transition to the status however that could be an event that sends an email.
If the notification scheme doesn't send anything you can always see whether there is an email postfunction set up on the state transition on the flow itself.
(or see if there is another automation set up to send out an email when the issue goes to closed)
I would not just remove the people from the generic event. That would indeed be used at other places.
Removing the Generic Event from the flow itself could be an option tho.
Keep in mind that if someone changes the notification scheme these things will start going again.
perhaps better to make your own custom event and link that to the transition?