HOW TO: Create an email notification for a pending due date – "Reminder"

Summary

This step-by-step article describes how to create an email notification to be sent to the owner of an issue when a "due date" is approaching i.e. a reminder notice.

Methodology

Reminder emails make use of the following RMTrack features:

Steps

  1. First we need a reminder date field to use for the automatic transition:
    1. Determine the "base date" that you want to use for the calculation of the reminder date. This can be any existing date field. Either a 'stock' date field e.g. DateOpened, or a custom date field that you have added to RMTrack e.g. DueDate.
    2. Create a new computed field for the reminder date:
      1. Customize > Issue Fields > New
      2. Field name: (e.g.) ReminderDate
      3. Friendly name: Reminder Date
      4. Description: Date to trigger automatic transitions for email notification
      5. Security: Computed fields are by definition not updateable. If you want to hide the ReminderDate from certain groups you can select them here.
      6. Date Type/Representation: Click the “Advanced” checkbox
      7. Display as: Date
      8. SQL Expression: (the following example will compute a date that is 7 days before the DueDate)
        dateadd(dd, -7, Issues.DueDate)
        (Please request assistance for other variations of computed date fields)
    3. Note: You can now use the Reminder Date as you would any other field. It can be added to your Data Entry forms, and layouts – but it does not need to be – it can remain an 'internal' date.
  2. Now we need to create an automatic transition in the Workflow. We are going to need to create a new Resolution State to automatically transition issues to when the Reminder date arrives:
    1. Go to Administration > Customize > Workflows
    2. Open the workflow you want to work with.
    3. Create a new Resolution State by drawing a new box on the diagram. Generally, you will want to create the new resolution state between the step that you want the reminder sent from and the step that an issue would normally proceed to. For example, let's say you want to send reminders to developers that have issues waiting to be fixed... your current workflow might look like: After adding a "Reminder" resolution state your new workflow might look like: Notice the dashed line and arrow going from 'To be fixed' to 'Reminder'; this indicates that this is an 'automatic transition'.
    4. To create the automatic transition, draw an arrow from one resolution state to another. On the Transition Properties dialogue box, switch to the "Automatic" tab.
    5. Check the Automatic Transition checkbox.
    6. There are two ways to automatically transition an issue:
      1. After an elapsed period of time i.e. the issue has remained in the current resolution state for 'n' hours
      2. After this date has passed i.e. after an issue field date has passed – in this case 'Reminder Date'.
    7. You may choose to re-assign the issue at this point or leave it assigned to the current assignee. Re-assignment is good for escalation of issues, leaving it assigned to the current user is good for reminders.
    8. Remember to create a manual transition from the Reminder state to wherever it would have gone without the reminder. And you probably want to leave the original transition (in case the work is done before the reminder date).
    9. Save your workflow changes.
  3. Finally we need to create the email notification rule.
    1. Go to Administration > Projects > E-Mail Notifications.
    2. NOTE: The rule that we are going to create is based on a workflow transition therefore it MUST be created at the Project level as each project can use a different workflow.
    3. Select the Project for the rule from the Project dropdown.
    4. Click the 'New' button.
    5. Give the rule a name e.g. Reminder
    6. Select an email template for the rule to use (for more information on email templates, please see the Administration guide).
    7. Select the 'When an existing issue traverses this workflow action' and select the appropriate transition from the dropdown.
    8. Select the recipient for the email. For reminders this should generally be 'The user the issue is currently assigned to'.
    9. Save the email rule

That's it! In the above example, whenever any issue reaches a date 7 days before the Due Date, RMTrack will automatically move the issue to the Reminder state. That move will trigger an email to be sent to the user that is currently assigned the issue. The user can then complete their task and move the issue on as they normally would.

Applies to

RMTrack Issue Tracking - All versions

Keywords: Due Date, Reminder, Email Notification