Can be combined with other date and time smart values. TEST-123-some-feature, {{repository.url}} returns the absolute URL of the repository, e.g. Affects version of an issue as a list. {{createdBranch.repository}} - accesses details of the branchs repository, {{createdBranch.repository.id}} - returns the repositorys ID, {{createdBranch.repository.name}} - returns the repositorys name. Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. Create a sample project and follow all of the breadcrumbs in the audit log of the rule details. Whenever you want to edit a field in Jira, use the Edit issue action. PROJ-213, {{issue.epic.status.name}} - Returns the epic's status, e.g. issue The active issue. Otherwise, register and sign in. Try adding.accountId after coordinator (so{{#if(issue.assignee.equals(issue.coordinator.accountId))}}. {{attachment. The smartvalue{{webhookData}}gets the root of the JSON payload. If I use a smart value of type: {{sprint.name}} the field returns me all the sprints that exist in the "sprint" field, including those that are already closed. Returns the issue's comments. I created an automation that created a value in a short text field. Can you please assist us in working out the following issues? role. Andit appears you are using Server/Data Center version, as the Re-fetch action does not have the "delay rule" option for Cloud. Learn more about list smart values. You can also trigger rules to run from third party services like Bitbucket or GitHub. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. Learn more about user smart values. They allow you to access . Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. The spacing format is mentioned in the following article: Smart-value-in-published-article-doesn-t-work. {{addedfieldChange.values}} - Returns the new value/values added. Can be used with both Approval required and Approval completed triggers: {{approval.createdDate}} - Returns creation date of approval. We do not currently support accessing fields within insight objects. If this issue is in an Epic, then epic refers to the Epic issue. Used with: Create branch in Bitbucket, Create branch in GitHub, and Create branch in GitLab actions. Possible states include pending, in_progress, successful, failed, cancelled, rolled_back, or unknown. Through the dot notation you can access fields like issue type, status and custom fields (details on how you can use these to interact with Jira's REST api are here) awesome commit handles everything, {{commit.url}} returns the absolute URL of the commit, e.g. Refers to the original issue when you branch the chain. The option to created linked issues (and then pick the blocked option) exists, but only to pick the issue from the trigger value or the most recently created issue to create a link. A good tip for checking your progress is to say aloud what you have built so far: Whenever the field value changes for story points AND it is a sub-task. Can be combined with other date and time smart values. - Any ideas on this one? Accesses the values in an issue'sAffected services field. Learn more about automation triggers. I've tested it on my instance and it yielded only 1 sprint (out of 3 that are ongoing). After testing, disable both the HTTP dump and access logs to avoid performance issues. Through the dot notation you can access fields like issue type, status and custom fields (details on how you can use these to interact with Jira's REST api are here) Also provides the customer portal URL for Jira Service Management issues. {{commit.repository}} returns the information related to the repository. See all smart values used to insert conditional logic such as if/equals/and statements into comments and other text fields. Learn more about working with related issues. You can access all fields of the Epic. They are variables in the sense that their actual values will be calculated while the automation rule is being executed: You can use two types of smart values: {{pullRequest.destinationBranch}} returns the name of the destination branch, e.g.master, {{pullRequest.destinationBranch.url}} returns the URL of the destination branch, e.g. Are you looking for server documentation? [Custom Field].description}} - Returns the text displayed below the custom field viewed in the Simple Search column. For example, if the epic has a custom field calledInitiative, then{{issue.epic.Initiative}} will return the value in the Initiative field. The URL to access the issue. Now whenever this field changes in Jira, this automation rule kicks in. Used with: the Send web request action (Wait for response enabled). You can set triggers to run on a schedule or as needed. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). Navigate to your project in Jira. General triggers These triggers can be used across all Jira products. [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work]. {{changelog.issuetype}} - Changelog information for theIssue type field. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. In this way, approval returns two different values depending on the trigger being Approval required or Approval completed - https://support . In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. Learn how to integrate your source code management tool with Jira Cloud, Visit the marketplace to integrate your build or deployment tool with Jira Cloud. https://bitbucket.org/account/repo/TEST-123-some-feature. They allow you to access and manipulate almost any data in Jira. Join now to unlock these features and more. {{issue.duedate}} - Returns theissue's due date. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. all fields available to{{issue}}are available here as well. We will ensure the story points of the parent and sub-task always remain in sync. What goes around comes around! You can specify a default value to prevent this. {{webhookResponse.status}} - response code e.g. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. Can be combined with other user-related smart values. Because this smart value deals with multiple items (i.e: issues can have many watchers), it can be used with the#symbol to apply the rule to each individual component. What third-party applications can I integrate with? Smart values - syntax and formatting; Jira smart values - issues; Jira smart values - conditional logic; . To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. If you've already registered, sign in. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. If a customer has not responded to an issue in 5 days, close the issue and leave a comment. {{issue.url.customer}} - Returns the customer portal URL (forJira Service Management requests). {{issue.affectedServices.tier}} - Returns the tiers of the issue's Affected services. You could then use this to count the number of issues returned. This applies to the legacy Insight app. Accesses information for the version that triggered the rule. Keep earning points to reach the top of the leaderboard. {{deployment.environment}} returns information related to the deployment environment. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. You could then use this to count the number of issues returned. Or you could count how many issues have the same label, same fixVersion, etc. Here is an example automation rule which can be used as a templated rule for creating a Release Center Epic from any (or selected) Jira Software project versions automatically: Rule step. Returns the value of the Jira Service Managements scale custom field. This will return a list of values, if the issue has more than one attachment. At the same time, it would be to good to mention that it is Jira-cloud functionality only. Which Jira-server version supports the use of smart value: "{{#if }} text {{/}}, or is this a Jira-cloud only functionality ? {{versions.description}}- Returns the description of the affects version. You can access all fields of the parent. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. You can access the current watchers of an issue. Can be combined with other user smart values. These can be combined with other user smart values. You can also use the quick search (keyboard shortcut is . In the project menu, click on Project Settings. Reviewing your audit logs is an effective way of debugging your rules. Field value changed Available in Server Lite: No 2020-07-20T07:00:00.0+0000. Again say it aloud: Whenever the field value changes for story points AND it is a sub-taskTHEN for the parent of the sub-task. Possible states include pending, in_progress, successful, failed, cancelled, or unknown. The rule is running too quickly after the issue is created. The spacing format is mentioned in the following article: New automation smart values in Jira Cloud, https://jira.atlassian.com/browse/JIRAAUTOSERVER-212, Smart-value-in-published-article-doesn-t-work. Here, we choose the Issue fields' condition and clarify that the issue type we are looking out for is a sub-task. {{issue.description}} - Returns the content in the issue'sDescriptionfield. Because this smart value deals with multiple items (i.e: issues can have many components), it can be used with the#symbol to apply the rule to each individual component. {{issue.comments.author.displayName}} - Returns the comment authors. Prints the issue key and its status (e.g. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. For more information on when issues is available, see, Multiple comments on the active issue (this example is explained in detail in, Properties for versions include:name, description, archived, released, releaseDate, "Customer Request Type" in older instances of Jira. Understand the general concepts and best practices of automation in Atlassian Cloud products. Learn more about using smart values with sections and lists. {{fieldChange.from}}- Returns the previous raw value, e.g. {{fieldChange}}only contains the first changed value. {{branch.name}} returns the name of the branch, e.g. {{issue.epic. {{issue.timetracking.remainingestimate}} - Returns the value in the Time remaining field. For example, if the Assignee of a field changes, you could add a comment to the issue to note who the previous assignee was, and who the new assignee is. {{attachment.author.emailAddress}}: Returnsthe email address associated with the user name. Accesses information related to a file attachment on an issue. 2020-07-20T07:00:00.0+0000. You could then use this to count the number of issues returned. A build represents the process in which files are converted into their final consumable form. Learn how to use these to interact with Jiras REST API. {{createdBranch.repository.url}} - returns the repositorys URL. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. Triggers, conditions, and actions are the building blocks of automation. Check out how we use smart values in our Jira automation template library. If it has a time you may need to strip off the time part for the comparison by changing the format: {{triggerIssue.customfield_10043.jqlDate}}. For example, PROJ-123. Jira automation - Data Center and Server (Latest), Examples of using smart values with dates, Examples of using smart values with lists, Examples of using math expression smart values, Examples of using smart values with text strings. {{version.name}} - Returns the version's name. {{environment.name}} returns the use-provided name for the environment, e.g. Here you can access any issue property. This means that when using automation, actions often need to apply, not only to the source issue that triggered the rule, but also to any issues that are related to the source issue. {{issue.affectedServices.dependentServices}}- Returns the list of services that this issue's services depend on. Through the dot notation you can access fields like issue type, status and custom fields (details on how you can use these to interact with Jira's REST api are, A list of issues generated by a trigger that runs a JQL search (, trigger when set to process in bulk). @Simeon Ross - Any ideas on this one? Learn more about list smart values. If a field or value doesn't exist, it will return an empty value:{{invalid reference}}. Approval required: accesses information when an issue that requires approval is created or updated, or when new approvers are added to an issue. {{assignee.displayName}} - Returns the assignee, {{reporter.displayName}} - Returns the reporter, {{issueType.name}} - Returns the issue type, {{resolution}} - Returns the resolution status, {{created}} - Returns the date the issue was created, {{updated}} - Returns the date the issue was updated, {{Story Points}} - Returns the story points for the issue (company-managed Jira Software), {{Story point estimate}} - Returns the story points for the issue (team-managed Jira Software). Share the love by gifting kudos to your peers. Learn more about date and time smart values. Syntax example The smartvalue { {webhookData}} gets the root of the JSON payload. Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. Create and configure Jira automation rules, Branch automation rules to perform actions on related issues, Issue data (Automation format) payload for Send Web Request, Issue data (Jira format) payload for Send Web Request action, Limitations in team-managed projects for automation rules, Permissions required for Jira Cloud automation rules, Test a Jira automation rule using the Manual trigger, Transfer Jira automation rules from one user to another, Differences between Automation in Jira Server and Jira Cloud, Examples of using math expression smart values, Examples of using smart values with dates, Examples of using smart values with lists, Examples of using smart values with text strings, Use Jira automation rules to modify issues, Convert wiki markup to HTML or plain text in Jira automation, Move an issue to another project using automation, Learn how to use these to interact with Jiras REST API. Every rule starts with a trigger. {{flag.key}} returns the key of the feature flag. Added by: Send web request with "Wait for response" checkedOn successful request, you will be able access webhook response data using the following smart values: Multiple responses can be access via the following fields: Added by: Worklogged TriggerThe worklog entry that has just been logged against an issue. {{issue.Customer Request Type}} - Returns the customer request type for older Jira instances. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. Added by: Send web request with "Wait for response" checkedOn successful request, you will be able access webhook response data using the following smart values: Multiple responses can be access via the following fields: Added by: Worklogged TriggerThe worklog entry that has just been logged against an issue. For Jira Service Management requests only. all fields available to{{issue}}are available here as well. Also provides the customer portal URL for Jira Service Management issues. You must be a registered user to add a comment. [Custom Field]}} - Returns the value in an epic's custom field. If this issue is a sub-task, then parent refers to the parent issue. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. Each field is a list of changes. These smart values are only available for the Build successful, Build failed and Build status changed development triggers. For example if a rule has both a Create branch in GitHub action and a Create branch in GitLab action, {{createdBranches}} will return the values of both branches as a list. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. Note that repository contains additional nested smart values. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. The URL to access the issue. {{issue.watchers.emailAddress}} - Returns the watcher's email address. {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value. {{branch.repository}}). The URL to access the issue. If this issue is in an Epic, then epic refers to the Epic issue. Jira smart values - issues To test what your smart value returns, use the manual trigger with log action and the result displays in the audit log. Visit the marketplace to integrate your build or deployment tool with Jira Cloud. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Smart values allow you to access and manipulate a wide range of issue data within your site. {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. These smart values are only available for the Branch created development trigger. They kick off the execution of your rules. I'll mention the docs discrepancies to the person that maintains our documentation. text {{/}}, or is this a Jira-cloud only functionality ? twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. {{issue.project}} - the project this issue is a part of. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms. Step 4: Add 'Edit Issue' action . Join now to unlock these features and more. Accesses the value in the issue'sAffects versions field. There should be a locked field named either "Request Type" or "Customer Request Type" there. Properties are frequently used by add-ons and integrations to store values. You can access all fields of the parent. A representation of a release/version in Jira. You can also use this with, . for a select field. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. {{comment.properties}} - Accesses any comment property. In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- Challenges come and go, but your rewards stay with you. {{issue.TempoAccountField}} - Returns the name of the account, {{issue.TempoAccountField.id}} - Returns the ID of the account, {{issue.TempoAccountField.name}} - Returns the name of the account, {{issue.TempoAccountField.value}} - Returns the name of the account, Can be used with: the Approval required trigger and the Approval completed trigger. Learn more about list smart values. {{issue.issueType.name}} -Returns the issue's type, for exampleStory,Bug, orTask. It some places it pops up, but there is no real explanation. Returns the value of the Jira Service Managements rate custom field. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. Understand the general concepts and best practices of automation in Atlassian Cloud products. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. You can check this by navigating to the "Custom fields" page in theglobal admin section. Used with the Version created, Version updated, and Version released triggers. The following example sums all of the story points for issues returned from the JQL search. Returns information related to all feature flags created in throughout the rule or branch, as a list. For example, you can use the following smart values to send a Slack message that includes the issue key and issue summary: { {issue.key}} { {issue.summary}} Check out how we use smart values in our Jira automation template library. build#123, {{build.url}} returns the absolute URL of the build, e.g. For example, wheninvalid referencedoesn't contain a value, you can printHello worldusing{{invalid reference|"Hello world"}}. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. Used with: any triggers that edit an issue. You can access all fields of the Epic. {{attachment.mimeType}}: Returnsthe file format of the attachment. Instead using Re-fetch for Cloud slows the rule for about 1 second (or more). There are many ways you can edit a field. This smart value only works for issues that have been added to an epic. {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. [Custom Field].id}} - Returns the unique id for the field assigned by Jira. {{issue. {{issue.fixVersions.name}} - Returns the name of the fix version. You can access the current watchers of an issue. Affects version of an issue as a list. Learn about the concepts and procedures related to automation in Jira Cloud. Learn more about automation triggers. Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. Share the love by gifting kudos to your peers. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. Learn more about using smart values with sections and lists. It may contain, for example, branches and tags names.This value is optional and may be an empty list. All of the issues found by the trigger are then treated as a single bundle of issues. {{issue.security.id}} - Returns the security level ID. You can check this by navigating to the "Custom fields" page in theglobal admin section. Learn more about configuring time tracking. If you've already registered, sign in. The comment that triggers the rule is stored in this smart value. They often contain sub-tasks, are stories that are part of a larger epic, or are simply linked to other issues using certain relationships. In the below example, we're sending out a notification that someone has added a comment to an issue, perhaps as a Slack message. A pull request represents proposed changes before they are integrated into an official project. View the list of available triggers. As for if and when the support will go to server, I have no idea. Triggers: Triggers wait for defined events to take place in your Jira instance and will then execute the automation rule. I've not been able to find such kind of information. https://bitbucket.org/{7faf7dee-a29b-4faa-bbc2-d7128a6d3278}/{315a3ecb-1f18-4953-98ae-5890f93073b5}/addon/pipelines/home#!/results/7, {{build.state}} returns the state of the build. You're on your way to the next level! You can check this by navigating to the "Custom fields" page in the. This can be almost anything you want. These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers.