As I have analyzed through Atlassian community, it looks like I have to hack the core code of issue updated listener. Is it like should i create a listener and check whether the event is issue updated and then the issue status and then flag off notification? If yes, how to flag off notification via code. Please input
or, Is it I have to edit the core JIRA code, then Can you help me where to add that if condition ?
At a high level, this is pretty straightforward:
This approach is fairly non-intrusive; from the listener side, you are basically just adding a conditional event, and each project admin can choose to notify on it, or not, as is appropriate.
Actually, it looks like you wanted "Open Issue Updated". If it was me, I'd create both events and two listeners, so you have complete flexibility (an admin may want to see the closed updates). Just invert the logic of the condition for the "Open" event.
Creating a new listener may not help you, because unless you remove the notification scheme from the project, JIRA will dend event notifications. If you remove, issue updated event grom the scheme, your listener will have to implement the update notification as you described. There may be several addons that support what you need, one of them is email this issue: https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.emailissue/server/overview
Beside many other things, It has support for conditional notifications out of the box.
@Tibor Hegyi [META-INF] : As our requirement is only this, I am not fully agreeing in buying an addon. I believe we can develop a plugin for this specific requirement. I wanted to know, If I have configured issue update notification, is there any ways in writing a listener and setting notification off for that particular issue based on defined conditions ?
Like issueeventdispatcher -> setnotification false. Will it have any effect ? I want to know before I put effort.
Thank you for you inputs. If you can help, I would be more happy
No, JIRA is going to pick up the "issue updated" event and fire a notification whatever you do.
You do not need to hack the core code, but you do need a new listener or something like the add-on Tibor mentions.
Without the addon, you will need to find/write a listener that sends an email when it detects "issue updated". JIRA's notification stuff works like that already, but the bit you need to add is "unless status is closed".
Once you have that working, or you've used the suggested add-on, you then change your notification scheme so that it sends mail to nobody on the issue updated event (because the listener or add-on will be sending a duplicate)
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot