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; } } }

Email notifications common file

Oliver Weiser

Hi experts,

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,

Oliver

Accepted answers

All comments

Nic Brough -Adaptavist-

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)

Oliver Weiser

Hi Nic,

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,

Oliver

Nic Brough -Adaptavist-

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.

Oliver Weiser

It looks like the difference is between customer and agent.

For customers the changes are visible, for agents they are not...

Regards,

Oliver

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

jira-core