Testing and Editing Scheduler Email
Editing the email template and sending test email from the scheduler requires the Tempo Administrator permission.
The Tempo scheduler can be programmed to send reminder emails to users about their worklogs. Administrators can send an email for testing from the scheduler. Clicking the List Users... link shows a list of all users who receive the email reminder.
Test Scheduler Email
To test the scheduler email:
Click Jira settings :settings_dc: at the top-right, and then select Manage apps.
Under Tempo in the sidebar at the left, select Scheduler.
Click the Test Scheduler Email link.
The Send Test Email screen is displayed.
Select an Email type, either Status Reminder or Late Reminder.
Select whether this is a Period, Weekly or Biweekly reminder.
Specify what day the Week ends on.
Select a user in the Calculate status for user field. If the field is left empty, the current user will be used. The test email will include the calculated period status for the selected user.
Write the email address you want to use for the test in the Send email to field. By default, this is the email address for the current user.
Click Send to finish and check the user's inbox for an email.
Editing the Email Reminder Template
If you already made changes to the scheduler email template in earlier versions of Tempo Timesheets, you can edit the scheduler email to fit the needs of your organization.
Click Jira settings :settings_dc: at the top-right, and then select Manage apps.
Under Tempo in the sidebar at the left, select Scheduler.
To open the template, click the edit icon for the reminder you want to edit.
Use the list of Available parameters at the right to change the HTML. See tables below.
Use the Show Preview button at the bottom to view the changes you have done.
When you are finished, click Save.
Available Parameters
General parameters
Parameter Name | Description |
|---|---|
userFirstName | User first name used in the greeting |
userFullName | User full name used in the greeting |
reminderType | The types can be Period, Weekly, or Biweekly |
dateFrom | Start date of the period being closed |
dateTo | End date of the period being closed |
closingDate | Closing date/time of the period being closed, e.g. when the close scheduler runs |
hoursRequired | Users required hours for the period being closed |
hoursLogged | Users logged hours for the period being closed |
hoursDifference | The difference between required and logged hours for the period being closed |
now | Date and time of the user timesheet status, e.g. when the status is sent |
baseURL | The JIRA URL used in the P.S. section info |
statusClass | Used to highlight hour difference with red if hours are missing |
Note
The following parameters are only available for the weekly or biweekly status emails. These parameters add information about the status of current Tempo period.
Parameters for period
Parameter name | Description |
|---|---|
period-dateFrom | Start date of the period |
period-dateTo | End date of the period |
period-hoursRequired | Users required hours for the period |
period-hoursLogged | Users logged hours for the period |
period-hoursRequired-today | Users required hours for the period from period start through scheduler close date |
period-hoursLogged-today | Users logged hours for the period from period start through scheduler close date |
period-hoursDifference | Difference between required and logged hours in the period |
period-statusClass | Used to highlight hour difference with red if hours are missing |
Note
The following parameters are only available for the weekly or biweekly status emails when the 2nd period is enabled in Tempo. These parameters add information about the status of current Tempo 2nd period.
Parameters for 2nd period
Parameter Name | Description |
|---|---|
period2-dateFrom | Start date of the period |
period2-dateTo | End date of the period |
period2-hoursRequired | Users required hours for the period |
period2-hoursLogged | Users logged hours for the period |
period2-hoursRequired-today | Users required hours for the period from period start through scheduler close date |
period2-hoursLogged-today | Users logged hours for the period from period start through scheduler close date |
period2-hoursDifference | Difference between required and logged hours in the period |
period2-statusClass | Used to highlight hour difference with red if hours are missing |
Related Topics