{"type":"doc","content":[{"type":"layoutSection","marks":[{"type":"breakout","attrs":{"mode":"full-width"}}],"content":[{"type":"layoutColumn","attrs":{"width":66.66},"content":[{"type":"heading","attrs":{"level":1},"content":[{"text":"Overview","type":"text"}]},{"type":"paragraph","content":[{"text":"R4J can be configured to send email notifications to designated users every time a ","type":"text"},{"text":"suspect","type":"text","marks":[{"type":"em"}]},{"text":" is triggered. See ","type":"text"},{"text":"Configuring the Suspect Logic","type":"text","marks":[{"type":"link","attrs":{"href":"/wiki/spaces/REQ4J/pages/5406964"}}]},{"text":" to learn how to configure suspect triggers.","type":"text"}]},{"type":"paragraph","content":[{"text":"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. The template for the email can be customized by the Jira administrator.","type":"text"}]},{"type":"paragraph","content":[{"text":"Notifications are sent from the email address of the suspect’s project - see ","type":"text"},{"text":"Configuring a project's email address","type":"text","marks":[{"type":"link","attrs":{"href":"https://easesolutions.atlassian.net/wiki/spaces/REQ4J/pages/1393950900/External+Web+References#Email-Configuration"}}]},{"text":".","type":"text"}]}]},{"type":"layoutColumn","attrs":{"width":33.33},"content":[{"type":"extension","attrs":{"layout":"default","extensionType":"com.atlassian.confluence.macro.core","extensionKey":"toc","parameters":{"macroParams":{"minLevel":{"value":"1"},"maxLevel":{"value":"7"}},"macroMetadata":{"macroId":{"value":"d4036f7fecb346a1e9f6a5b7649800b7"},"schemaVersion":{"value":"1"},"title":"Table of Contents"}},"localId":"f2080673-2e95-4995-b3b0-a1e908785ada"}}]}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"Customizing email content","type":"text"}]},{"type":"paragraph","content":[{"text":"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. XSLT (Extensible Stylesheet Language Transformations) 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.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"How to customize the suspect template","type":"text"}]},{"type":"paragraph","content":[{"text":"To customize the XSLT template you must be a Jira Administrator.","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Select the ","type":"text"},{"text":"Jira adminstration icon > Manage apps","type":"text","marks":[{"type":"strong"}]},{"text":", then select ","type":"text"},{"text":"R4J - Requirements Management for Jira > E-Mail Templates","type":"text","marks":[{"type":"strong"}]},{"text":" from the sidebar. (Keyboard shortcut: Enter \".\" and start typing \"e-mail templates\".)","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Select the","type":"text"},{"text":" Suspect Notification","type":"text","marks":[{"type":"strong"}]},{"text":" template from the drop down menu.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Edit the XSLT template within the text area below the drop down menu.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Select the ","type":"text"},{"text":"Save","type":"text","marks":[{"type":"strong"}]},{"text":" button to save the template.","type":"text"}]}]}]},{"type":"paragraph","content":[{"text":"There are two other options:","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Preview","type":"text","marks":[{"type":"strong"}]},{"text":": Shows the results of applying the template to an issue.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Reset","type":"text","marks":[{"type":"strong"}]},{"text":": Returns the template back to the default.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"XML representation of a suspect","type":"text"}]},{"type":"codeBlock","attrs":{"language":"xml"},"content":[{"text":"\n\n URL of your JIRA instance\n Name of your JIRA instance\n\n \n Issue key\n

Summary

\n Description\n Issue type\n Formatted link to issue\n \n\n \n Username\n User's full display name\n Formatted link to user\n \n\n Time of suspect change\n\n -> List of linked issue(s)\n \n Issue key\n

Summary

\n Description\n Issue type\n Formatted link to issue\n \n \n\n","type":"text"}]},{"type":"paragraph"}],"version":1}

Browser not supported