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
This is an interesting case I always wanted to make better: almost every project you come to has a lot of older unreleased tickets, that are already on production for quite some time. And developers (without proper jira management) continue to use the Kanban board that becomes more crowded in the Done / Closed column (and it can hit 400, 1000 tickets and be slow and almost pointless to use). Typical story, huh?
So what to do, if you want to release all those older tickets and don’t bother developers with, say, 450 updates on every ticket that fixVersion has been set to each one of them? The answer (and thanks to AUG Moscow Community) is to swap notification scheme for related projects while releasing.
1. Go to Jira Settings -> Issues -> Notification Schemes (usually there's just one by default)
2. Create a blank scheme (as in the screenshot). It means that the events (like in my case it is ‘Issue Updated’ would not send any notifications).
3. Now go to the Project Settings -> Notification Schemes. Swap the notification scheme for the blank one in the Project Settings
4. Take a look at notification schemes in jira settings (it should not include one project attached to the blank scheme.
5. And finally release the Done/ Closed tickets on the Kanban board -> voila, no email notifications were sent at all.
You’ll still get the events themselves logged in Jira, event if notifications weren't sent.
Might include turning off outgoing emails, but after turning them on events will build up a queue of notification that missed scheduled sendout :) So don’t do this.