Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Mail Body Initializer templates is a concept to initialize the Body field in the Email Screen when you want to send emails manually. Contexts can define a single Mail Body Initializer template.

These templates are regular email templates that you can develop in Email This Issue, however you must understand how they work in conjunction with the templates you use to render the final email.

How Mail Body Initializer templates work

They can be composed using HTML, velocity, may contain issue fields, or regular text or anything.

When you open the Email screen, the Context related to the current issue is determined. If the Context is configured with a Mail Body Initializer template, the template is evaluated and the result is set in the Body field.

it is a good practice to add a distinquishable Template Category name for these templates so that they can be easily identified. So far all is easy.

Templates to send emails prepared with Mail Body Initializer Templates

Contexts have an Email Template attribute. This specifies the template used to send the emails sent manually. If you configure the Context with a Mail Body Initializer template, you should not use the same template to send the email, otherwise all content will be duplicated in the email because the Body field is added to the template via the variable $!mailBody. Or more generically, Email Templates  and Mail Body Initializer templates should not have overlapping content to avoid duplication of content in the email.

Image Removed

Instead, if you have a Mail Body Initializer template, we recommend you create a template as simple as $!mailBody and select it in the Context's Email Template field.

Image Removed

...

Expertisefinder redirect
forcedfalse
dest{"value":"https://docs.meta-inf.hu/email-this-issue-for-jira-server-data-center/documentation/outgoing-emails/email-templates/using-mail-body-initializer-templates"}
typeurl
enabledtrue

Thank you for visiting our old product documentation site. Note that we no longer store or update our documentation here.

Please navigate to our new documentation site and update your bookmarks accordingly. If you're looking for the former content of this page, click here.