User information
 Loading ...
Show article in Knowledge Base

 Variables that can be used in email reply templates Export knowledge base Export     SubscribeSubscribe      Show article info

Using variables in the email reply templates allow you to show values from the issue in the email

By using variables in the email templates you can fetch dynamic values from the system and create an up-to-date email automatically. When you then click on "Add to content", the variables are parsed and added to the e-mail content.


Parsing variables mean that they are translated from the cryptic variable format into the actual values.


For example, if you have the variable $! in the template text, it will be translated into the name of the actual status that the issue has.


Note: The actual names of some fields and terms are dependent on the terminology settings. These are shown with the default names, with an asterisk. 

All field names can also be changed in the issue field configuration.



Variable Gets
$! Name of product *
$!projectIssue.issueKey Issue Key 
$!projectIssue.ticketId Ticket Id
$! Title of issue
$! Name of Service Level Agreement
$!projectName Name of project* the issue is in
$!dueDate Due date
$notificationContents Contents of notification. This is in part generated by system.
$! Issue type
$! Issue status
$! Issue severity
$!issuePriority Issue priority
$!creatorUserName User name of the issue Reporter
$!creatorUserEmail Email adress to the issue Reporter
$!creatorPhone Phone number to the issue Reporter
$!creatorHomePhone Home phone number to the issue Reporter
$!creatorCellPhone Cell phone number to the issue Reporter
$!currentOwnerUserName User name of the current issue Owner
$!currentOwnerPhone Phone number to the current issue Owner
$!currentOwnerHomePhone Home phone number to the current issue Owner
$!currentOwnerCellPhone Cell phone number to the current issue Owner
$!responsibleUserName User name of the issue Developer*
$!responsibleUserEmail Email adress to the issue Developer*
$!projectIssue.reporterSystemUser.username Username of the reporter 
$! Name of the project iteration*
$! Component 
$!projectIssue.customer.customerName Company name
$!projectIssue.reporterCompany.customerName Reporter company 
$!projectIssue.issueSource.value Issue source 
$! Issue resolution
$! Issue urgency
$! Escalation level
$!projectIssue.description Issue description - this is the main text content of issue.
$!projectIssue.affectedVersions Affected iterations/versions*


Build number
$!projectIssue.buildListText Build list text
$!projectIssue.publishExternal Published flag
$! Name of the Developer*
$! Name of current Owner
$!createDate Created date
$!completionDate Completion day (first time issue was set to complete)
$!modifiedDate Modified date
$!projectIssue.originalEstimatedTime Original estimated time
$!projectIssue.ticketURLCode Ticket URL code
$!projectIssue.remainingTime Remaining time
$!projectIssue.actualTime Actual time
$! Name of user that last replied to this issue
$! Parent project issue title
$!projectIssue.numberOfSubIssues Number of sub issues this issue has
$!projectIssue.subIssueOrder Sub issue order this issue has
$!projectIssue.permissionType Permission type
$!projectIssue.permissionValue Permission value
$!startDate Start date
$!projectIssue.allTags Tags field on issue
$!projectIssue.billingAmount Billing amount
$!projectIssue.costAmount Cost amount
$!projectIssue.fixedPrice Fixed price
$!projectIssue.fixedTime Fixed time


In progress date (when issue was first set to in progress)


Sub issues done in order
$!projectIssue.originalEmailFormat Original email format
$!projectIssue.permissionForUsers User permissions
$!projectIssue.permissionValueReadOnly Permission value read only
$! Product* name
$!nextBreachDate Next breach date
$!projectIssue.latestReplyIsBySupportUser Latest reply is by support user
 $!projectIssue.solution Solution
$!projectIssue.rankInVersion Rank in version
$!projectIssue.numberOfLinks Number of links
$!projectIssue.currentOwnerUserGroup.userGroupName Name of  the user group that the current Owner has
$!projectIssue.cCAddresses CC addresses
$!projectIssue.permissionForCustomers Permission for company
$! Release name
$!projectIssue.affectedReleaseNames Names of affected releases
$!projectIssue.storyPoints Story points
$!projectIssue.containsRecipients Contains recipients
$!projectIssue.issueNotIncludedInRecurringSeries Issue not included in recurring series


$!publishExternalDate Publish external date
$!projectIssue.isVoteable Issue is voteable
$!projectIssue.numberOfComments Number of comments
$!projectIssue.issueRank Issue rank
$!projectIssue.rating Rating
$!projectIssue.productComponentNames Product component name
$!projectIssue.sLAPlanManually SLA has been manually set on issue
$!projectIssue.globalRank Global rank
$!projectIssue.bCCAddresses BCC addresses
$!projectIssue.sourceDirectionName Source direction
$!projectIssue.externalId External id
$!projectIssue.attachmentCount Number of attachments
$!issueRatingLink A link for rating an issue  Read more here



Variables for custom issue fields:


Different custom issue fields are all added with the following variables:




where the X is the index number of the custom field.


You can find this number for a given custom field by opening the issue field configuration for the project (General - Settings - Issue configuration - Issue fields, select the configuration in that page). Then go to the field, and click on the ?-icon (which is blue for custom fields, and green for standard fields) to open the field info popup. In that popup, you see the index number for the field. 


For example, if you have a custom field called "SampleField" and you look up its index to be 22, then you should use the variable $!projectIssue.getCompanyCustomFieldValue(22) 







User comments
 Loading ...