Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Improved content
Section Column
Email notifications


R4J can be configured to send email notifications to


designated users every time a suspect is triggered.

The notifications can be send to one or more of the following users:

  • the assignee of the issue that triggered the suspect
  • the reporter of the issue that triggered the suspect
  • specific users
By default the email notification contains all available information regarding

See Configuring the Suspect Logic to learn how to configure suspect triggers.

The default email notification contains a great deal of information about the suspect. This includes the name and key of the issue that triggered the suspect,


information about the user who made the changes leading to the suspect as well as linked issues that might be affected by the changes.


On this page:

Table of Contents
exclude(result|issue|suspectUser|suspects|XML Field Description).*

Related pages:

XSLT Reference

Enable email notifications

Email notifications can be configured separately for each project. See Suspect Configuration for more information.

To disable email notifications for a project you can just un-check all recipients in suspect configuration view.

Configure a project's email address

The email notifications will be sent from the corresponding project email address.

This address is part of the Jira project settings. See 

The template for the email can be customized by the Jira administrator.

Notifications are sent from the email address of the suspect’s project - see Configuring a project's email address

 for more information.


Table of Contents

Customizing email content

Just like

Like Jira itself, R4J generates emails in reaction to specific events.


Unlike Jira, R4J uses XSLT for generating email notifications instead of the Apache Velocity template engine

, R4J is using XSLT for generating email notifications


stands for '

(Extensible Stylesheet Language Transformations

' and

) can be used to transform XML documents into other formats. The emails are generated by R4J in HTML format using a


template written in XSLT together with


an XML document containing all necessary information regarding the suspect.

How to customize

email templates
  • Log in as Jira Administrator
  • Choose Image Removed> Add-ons
  • Select

    the suspect template

    To customize the XSLT template you must be a Jira Administrator.

    • Select the Jira adminstration icon > Manage apps, then select R4J - Requirements Management for

    Jira > E
    • Jira > E-Mail Templates from the sidebar

    (info) Keyboard shortcut 'g' + 'g' + start typing 'E-Mail Templates'
    • . (Keyboard shortcut: Enter "." and start typing "e-mail templates".)

    • Select the Suspect Notification

    • template from the drop down menu

    to edit
    • .

    • Edit

    • the XSLT template within the text area

    • below the drop down menu.

    Click on
    • Select the Save button to save the template

    You can also display a preview of your template by clicking the Preview button and reset the template shown in the text area back to the default one by clicking the Reset button.


    While it's possible to select the recipients separately for each project, the email template will apply globally to all projects used with the R4J plugin.

    Template Data Structure

    Code Block
    titleXML represantation of the data regarding a suspect
    • .

    There are two other options:

    • Preview: Shows the results of applying the template to an issue.

    • Reset: Returns the template back to the default.

    XML representation of a suspect

    Code Block
    of your JIRA instance</baseUrl>
      <instanceName>Name of your JIRA instance</instanceName>
        <key>Issue key</key>
        <type>Issue type</type>
        <link>Formatted link to issue</link>
        <displayName>User's full display name</displayName>
        <link>Formatted link to user</link>
      <suspectTime>Time of suspect change</suspectTime>
      <suspects> -> List of linked issue(s)
          <key>Issue key</key>
          <type>Issue type</type>
          <link>Formatted link to issue</link>

    XML Field Description


    Top level element for the data regarding the suspect.


    Url to your JIRA instance

    instanceNamename of your JIRA instance
    issuethe issue that triggered the suspect
    suspectUserthe user who made the changes leading to the suspect
    suspectTimedate and time of the changes
    suspectsa list of all issues linked to the issue that triggered the suspect


    keythe JIRA issue key
    summarythe issue summary
    descriptionthe issue description
    typethe issue type
    linka formatted link to the issue


    FieldDescriptionusernamethe usernamedisplayNamethe user's full namelinka formatted link to the user


    A list of all issues linked to the issue that triggered the suspect. Contains one or more objects of type issue.