nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to create custom email templates in JIRA?

Andrew Ting

Hi,

I am trying to create a custom email template. I have modified the email-template-id-mappings.xml file as follows:

<name>HR Issue Resolved</name>

<template>hrissueresolved.vm</template>

<templatetype>issueevent</templatetype>

</templatemapping>

I have created the hrissueresolved.vm file under the subject and html folders on the server. NOTE: I have not created this file under the text folder as we only use html emails.

I have added a new event called "HR Issue Resolved" to Events in JIRA. I have modified our workflow so that this event is fired when an issue is resolved. I have restarted JIRA. When I tested our workflow, I do not receive any email.

Can anyone please help me out? Thanks!

Accepted answers

All comments

William Crighton _CCC_

questions:

JIRA version?
cloud or server?
contents of mail queue during/after you trigger event?
have you tested using a pre-existing template? (remove your velocity prowess from equation)
contents of atlassian-jira.log and the mail log (like pages of stack traces)

-wc

William Crighton _CCC_

updated answer with better questions

Andrew Ting

JIRA 6.3.15 Server The new email template is based off the issueresolved.vm template. I know it works because if I directly modify the issueresolved.vm template and fire the "Issue Resolved" event when my issue closes, I do get an email and with the modified contents I am expecting. So I know the template is correct. Thanks.

MattS

Yes, this is part of why customizing JIRA email templates is harder than it feels like it should be. Test with an unmodified copy of issueresolved,vm in hrissueresolved.vm. Make sure the transition is using your custom event and has been published. Make sure your issue is of the right type to be using the workflow. Once all that is working then start modifying the velocity template one small change at a time. You can use velocity.properties to not have to restart JIRA for every change. Then be ready to test hrissueresolved.vm at every upgrade. Are you sure you really need a new template? I generally encourage people to click on the View Issue link in email whenever I can

William Crighton _CCC_

thanks Matt - I'd make that the answer

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration