...
Once the plugin is installed, a new menu appears in the Add-ons administration page left menu, as shown below (you may have to reload page if plugin was just installed).
Plugin configuration
...
In the screenshot below, you can see the administration screen as it is when a context is selected, and no template is selected. This is the template creation mode.
Template title
Enter a title for your template. Please note templates titles are unique. You cannot create two templates with the same title.
Custom Text Elements
This allows you to choose between 0 to 5 custom text zones in your templates. One custom text area will be displayed in issue view for each of them.
Allow canned texts
Allows users to use one of the prepared canned answers in the custom text areas, instead of typing them.
Canned text categories
When the allow canned texts checkbox is checked, then a list of existing canned texts groups is displayed, and you can select any combination of them. Global canned texts are canned answers that can be used in any case, not restricted to a specific category of issues.
Subject template
The subject template is the template of the mail subject. You can enter a line of text, and include placeholders if necessary (more on placeholders later).
...
- [summary]
- Replaced by the issue summary
- [description]
- Replaced by the issue description
- [last-comment]
- Replaced by the last issue comment
- [custom-field-XXX]
- Replaced by the value of the custom field identified by its id (XXX must be replaced by the custom field value) in the processed issue.
- If the field contains a date, the default format will be used : yyyy-MM-dd HH:mm:ss
- [custom-text]
- Adds the custom text entered in the email sending form.
- [custom-field-XXX|yyyy-MM-dd HH:mm:ss]
- Same placeholder as above, but with a date/time format. If the custom field contains a date, it will be displayed using the provided format.
- [issue.XXX]
- Allows to include any issue field value. XXX must be replaced by the name of the field to extract. For example, to extract the issue creation date, the placeholder must be : [issue.created]
- If the field contains a date, the default format will be used : yyyy-MM-dd HH:mm:ss
- Available issue fields :
- reporter : the issue reporter
- assignee : the issue assignee
- reporterId : the reporter username
- assigneeId : the assignee username
- created : the issue creation date
- updated : the issue update date
- resolution : the issue resolution status
- status : the issue workflow status
- priority : the issue priority
- issueType : the issue type
- votes : the number of votes of this issue
- watches : the number of watchers for this issue
- resolutionDate : the issue resolution date
- dueDate : the issue due date
- summary : the issue summary
- description : the issue description
- key : the issue key (for example DEMO-1)
- affectedVersion : the list of affected version for this issue
- fixVersions : the list of fix versions for this issue
- [issue.XXX|yyyy-MM-dd HH:mm:ss]
- Same placeholder as above, but with a date/time format. If the issue field contains a date, it will be displayed using the provided format.
| Warning | ||
|---|---|---|
| ||
If you use issue.XXX placeholders (issue.summary, issue.description, ...), the generic formatter of Jira is used, and it may add some HTML formatting around your field's value. If you want to use this placeholder but do not want HTML formatting, you can add the |markup=no at the end of the placeholder. It will remove Jira's formatting. Ex: [issue.summary|markup=no] But we strongly discourage this. Where possible, use the specialized placeholder (instead of issue.summary, use summary). Specialized placeholders have their own specific formatter, which will always provide a correct output. |
History
History allow you to consult sent notifications
...