We need to add one static sentence to all email notifications, in the subject AND the body.
Please help finding the files that need to be modified.
We tried header.vm, footer.vm and a few more in /WEB-INF/classes/templates/email/html/includes with no effect.
We restarted the JIRA service after each change.
Thanks for your help,
The header and footer .vm files you have found are the right place to do this, so the question is what you changed and why it's not working. Can you make a really simple change to the footer.vm (just add a line of plain text at the bottom), restart JIRA and then tell us what you get when you comment on an issue (assuming your account is set up to get html email rather than plain text)
Thank you for your reply.
I actually got this to work for adding comments now.
The thing is: The display footer is different in the "Created" notification.
When looking at the "issuecreated.vm" it still includes the same footer.
Can you give a tip on where to put my text so it displays for all notifications?
Thanks and regads,
Ok, that's good that you're able to see changes.
Your text should just go in the header or footer, as they're included in all emails about issues (except subscriptions). So the question is what's different about the create. I'm assuming you made your working change in the footer and not in the body of the comment email, so we need to look at why that's different. Assuming the create and comment vms both say #parse(footer.vm) in the same way, then we just need to look at the footer.vm and where your code is in it.
Ah, hang on, that's Service Desk mails, not JIRA Core. Service Desk mails are built with different templates - they're bundled inside the Service Desk application and are really difficult to get at, because you have to unpack it, hack them and re-pack it. It's not something I can recommend (as I've never got any repacking to work)
So the files in /WEB-INF/classes/templates/email/html/includes are used when an agent does something in JIRA itself.
Well, then I need the file(s) that I need to change in Service Desk
Actually we modified a few soy files in service desk already, so rebundling is not a problem.
Can you please let me know which file(s) I need to adjust?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events