JETI's key feature is an issue operation you can invoke from the view issue screen.
Open the Email Screen to send manual (ad-hoc) emails
Compose your emails easily
The email screen is a UI to compose emails manually:
- set recipients (To, Cc, Bcc), recipients may be users, external email addresses, roles, groups, custom fields, and virtual users (Project lead, watchers, assignee, reporter)
- enter the email subject and email body
- add attachments or attach files to the email
- use predefined message to add complex content to the email body with single click
The email screen shows the issue details on the right hand side for easy reference, there is no need to open the issue in a separate tab of the browser.
While composing your email, you can set various email options. Email options are preset from the global defaults but can be overridden using the Send & Remember settings button. These user preferences are stored in cookies and are reused next time you send emails.
If you choose, "Send & Remember Settings", the email recipient configuration is also stored and reused next time.
You can select the issue attachments you want to attach to the email and append all issue comments as well. Your recipients will receive all pieces of information necessary to fully understand the issue they receive.
Quote Comments in Mail Body
The right hand side of the email screen shows the issue details including the comments visible to the current user. Comments may be qouted in the mail body with a single click.
Initialize Email Body with Prefill Templates
When you open the Email Screen using the Email button, you can start to compose the emails. To make this process easier, you can prefill the Email Body with dynamic content.
To initialize the email body, you need to develop an email template and select it in the Context's "Mail Body Initializer Template" field.
Never use the same templates to prefill body and send emails
Mail Body Initializer templates are purely used to initialize the Body field in the email screen. When the email is sent, the formatted, preinitialized and possibly modified Body will be submitted as if it was entered manually.
Therefore the template used to generate the final email will include this formatted, rich Body value via the $!mailBody variable. This means, if you used the same template, the preformatted content may be added twice to the email.
If you use a prefill template, the email template you send with may be as simply as the $!mailBody variable.
Multiple Email Templates
Contexts may be configured with multiple template categories. Templates from the selected categories are listed in the email screen. Emails are generated from the selected template.
Once you have composed your email recipients, subject, body and options, you can preview what the email will look like for the recipients.
To preview, click the Preview button.
Once clicked, the page will reload and the preview dialog shows the email details and content generated using the selected template.
Note: email recipients are resolved to email addresses.
Execute Workflow Transitions
Email This Issue supports execution of workflow transitions right after sending emails manually. To activate this feature, the Jira administrator must prepare the workflow.
Transitions marked by a transition property jeti.on.send.email.transition with value true are subject to be executed.
If no transition is marked in the current status
Then no transitions are executed automatically.
If only one transition is marked in the current status
Then this transition is executed automatically.
If multiple transitions are marked in the current status
Then upon sending the email, a popup screen is shown to select the transition to be executed. Transitions may be skipped by selecting Send Email Only.
Transition screen is not shown regardless if the transition is configured to popup a screen.
Conditions are bypassed but validators are applied.
The selected transition is executed after the email is sent. Failure to send the email will skip the transition. Although, the failure to execute transition will not prevent the emails from being sent.
It may be a good practice to add transitions to the workflow statuses that are hidden from the user interface and executed only when emails are sent.