I am talking about taking advantage of the issue event management in JIRA.
We all know about the notification schemes in JIRA and how JIRA sends email to the various subscribers when an event is fired. All we need to do is to make use of this feature.
Following are the simple configuration steps needed.
- Define a template which renders the subject and body of the email message - both html and text version. I have discussed about this in detail in my book. In case if you missed it, check out the email-template-id-mappings. xml file under WEB-INF/classes folder. I have created the following entry:
Note that you can do this programmatically when the plugin is enabled but I am not going into those details here.
- Write the templates defined above. You need 3 templates, all with the same name mailservlet.vm (name defined above).
Subject : The subject file goes into WEB-INF/classes/templates/email/subject folder
Subject will be something simple. We are going to keep it very simple!
Test Mail from Servlet
html : The html file goes into WEB-INF/classes/templates/email/html folder
This can be as fancy as you want. Let us keep it simple, using just 2 velocity params.
#set ($baseUrl = $params.get("baseurl")) Are you having fun reading the <a href="http://www.j-tricks.com">j-tricks</a> tutorial? Take a look at <a href="$baseUrl/browse/$issue.key">$issue.key</a>.
As you can see, there are 2 velocity variables, $params and $issue, that we have used in this template. We will see soon where those comes from.
text : The text file goes into WEB-INF/classes/templates/email/text folder
Again, let us keep it simple as shown:
Are you having fun reading the j-tricks (http://www.j-tricks.com) tutorial? Take a look at $issue.key.
- Restart your JIRA so that the template mapping is effective. No need to do this if you are handling it programmatically when the plugin is enabled.
- Create a custom event and map it to the new template we defined.
- Add the new event to the notification scheme and add subscribers to this event notification.
Now that the template is defined and the event added, we can write the code that feeds the relevant context for the template and then fires the event. In your plugin, all you needed is a few lines of code.
- Create the context needed for the velocity template used by the event. For an issue event, a large number of variables are already available: https://developer.atlassian.com/display/JIRADEV/Contents+of+the+Velocity+Context.
You can see both issue and params, the two velocity variables we used, a part of the list. params here will be populated by us when the event is fired.
A map of variables that will be added to params is created as follows.
Map<String, Object> context = new HashMap<String, Object>();
We are adding just sender and baseurl as those are the 2 ones taken from params in the template above.
- Fire the event. Here 10000L is the id of the event to be fired. We use the custom event that is mapped to our velocity template but the same mechanism can be sued to fire system events as well.
issueEventManager.dispatchEvent(10000L, issue, context, loggedInUser, true);
How about sending it only to selected people and not depending on the notification schemes? Like the share feature in
JIRA5? i.e. send only to selected users? Replace the dispatchEvent with the following.
- Create the map of params as in the above case.
- For each user, create a notification recipient and add it into a Set of recipients.
User user = ComponentAccessor.getUserUtil().getUser("jobin");
NotificationRecipient recipient = new NotificationRecipient(user);
HashSet<NotificationRecipient> recipients = new HashSet<NotificationRecipient>();
- Create an IssueEvent object with our issue, context and the event Id.
IssueEvent event = new IssueEvent(issue, context, loggedInUser, 10000L);
- Create a MailQueueItem using this event, recipient list and the template id. Here 99 is the template id.
MailQueueItem item = issueMailQueueItemFactory.getIssueMailQueueItem(event, 99L, recipients, "");
Note that you will have to enable to jira-core dependency in the pom.xml for IssueMailQueueItemFactory.
- Add the item to the mail queue.
And that's all. The mail queue will take care of dispatching our message.
Have a good day!