These are the data points used to bring the values from Jira to your release notes content. The variables will be replaced by actual values for given data points. Some examples are projectName, fixVersion, userName, etc.
When you use such variables, upon execution of the template, variables are replaced with actual values.
List of supported output variables
Variables (Users) | Syntax |
|---|
userName userEmail versionDriver versionApprovers
| [userName] [userEmail] [versionDriver] [versionApprovers]
|
Variables (Project) | Syntax |
projectName projectld projectKey
| [projectName] [projectld] [projectKey]
|
variables (Version) | Syntax |
version Name versionDesc release Date versionld versionURL startDate
| [version Name] [versionDesc] [release Date] [versionld] [versionURL] [startDate]
|
Variables (Sprint) | Syntax |
sprintName sprintId sprintGoal sprintStartdate sprintEnddate sprintCompletedate sprintState
| [sprintName] [sprintId] [sprintGoal] [sprintStartdate] [sprintEnddate] [sprintCompletedate] [sprintState]
|
Variables (Date & Time) | Syntax |
timestamp currentDate currentDatetime
| timestamp currentDate currentDatetime
|
Variables (Confluence) | Syntax |
confluenceURL confluencePageId
| [confluenceURL] [confluencePageId] This variable works similarly to the Confluence URL variable. For example - There are two actions in the rule. First action has to be Confluence action, second action could be any template action like Email, PDF, etc. that has the [ConfluencePageId] variable. When the first action is executed, its page ID is parsed in the second action and the id variable is replaced with the page ID created from the first action
|
releasePageURL (only available in Release page notification and LinkedIn announcement template type) | |