Automation allows you to focus on the work that matters, removing the need to perform manual, repetitive tasks by allowing your teams to automate their tasks, processes, and workflows. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. Access information related to the last branch that was created. {{issue.description}} - Returns the content in the issue'sDescriptionfield. This value won't work for any other trigger, even if a comment was added as a result (e.g. {{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). {{issue.url}} - Returns the URL of the issue. For example, if the epic has a custom field calledInitiative, then{{issue.epic.Initiative}} will return the value in the Initiative field. Available anywhere smart values are supported, to access the value of a field that has changed. Connect thousands of apps for all your Atlassian products, Run a world-class agile software organization from discovery to delivery and operations, Enable dev, IT ops, and business teams to deliver great service at high velocity, Empower autonomous teams without losing organizational alignment, Great for startups, from incubator to IPO, Get the right tools for your growing business, Docs and resources to build Atlassian apps, Compliance, privacy, platform roadmap, and more, Stories on culture, tech, teams, and tips, Training and certifications for all skill levels, A forum for connecting, sharing, and learning. {{changelog.status}} - Changelog information for theStatus field. Properties are frequently used by add-ons and integrations to store values. https://bitbucket.org/account/repo. Returns the value of the Jira Service Managements scale custom field. The active issue. {{fieldChange.from}}- Returns the previous raw value, e.g. {{pullRequest.sourceBranch}} returns information related to the source branch for the pull request. See all smart values that access and manipulate Jira issue data such as sprint, parent, or version. In this component, we use the following settings:The email address of the reporter is captured in the smart value {{reporter.emailAddress}}, but we need to use it in a URL and therefore will use the smart value {{reporter.emailAddress.urlEncode . Can be combined with other user-related smart values. Visit the marketplace to integrate your build or deployment tool with Jira Cloud. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. For example, checking that all sub-tasks of a parent issue are resolved. Triggers can be set to run on a schedule, and can be customized before being applied to a rule. - Any ideas on this one? Examples of using smart values with lists. {{issue. Get answers to your question from experts in the community, Smart value of trigger issue in automation. 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. Prints the issue key and its status (e.g. This smart value only works for issues that have been added to an epic. If this issue is a sub-task, then parent refers to the parent issue. See all smart values that can access and manipulate text fields, such as issue summary or comments. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. The type of event that triggered the rule. [Custom Field].defaultValue}} - Returns the value displayed on first view of the field. Smart values allow you to access issue data within Jira. After a lot of searches, I found the answer on: https://community.atlassian.com/t5/Jira-questions/Store-Active-Sprint-in-New-Field-Using-Jira-Automation-Script/qaq-p/1695408. Accesses the value in the issue'sAffects versions field. Learn more about using smart values with sections and lists. You can also use this withlists. 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. To get a property in it, we should use{{webhookData.someValue.childValue}}. In progress. You can access the current watchers of an issue. {{deployment.state}} returns the state of the deployment. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. In the project menu, click on Project Settings. Set the Equals condition to true. A representation of a release/version in Jira. Accesses information for the current running rule. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). { {issue. These smart values are only available for the Build successful, Build failed and Build status changed development triggers. Examples of how you can use smart values to access and format items in a list, such as checkboxes and labels. Navigate to your project in Jira. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. See all smart values used to insert conditional logic such as if/equals/and statements into comments and other text fields. : To do,In progress, orDone). For smart values related to the Insight feature in Jira Service Management, see Jira smart values - Assets. {{createdBranches.repository}} - accesses details of the branches' repositories, {{createdBranches.repository.id}} - returns the IDs of each repository, {{createdBranches.repository.name}} - returns the names of each repository. The example below lists each person watching the issue - both their display name and their email address - in bulletpointform. {{issue. The following example sums all of the story points for issues returned from the JQL search. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. 2020-07-20T07:00:00.0+0000. Keep earning points to reach the top of the leaderboard. They are using the curly-brace syntax like { {someSmartValue}} . "sd.public.comment".internal}} -. A build represents the process in which files are converted into their final consumable form. Create a sample project and follow all of the breadcrumbs in the audit log of the rule details. Used with: the Send web request action (Wait for response enabled). In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. Note that environment contains additional nested smart values. {{issue.fixVersions.releaseDate}} - Returns the fix version's release date. Learn how to use these to interact with Jiras REST API. {{createdBranch.repository}} - accesses details of the branchs repository, {{createdBranch.repository.id}} - returns the repositorys ID, {{createdBranch.repository.name}} - returns the repositorys name. Summary Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. Learn more about configuring time tracking. Learn more about using smart values with sections and lists. For example,jira:issue_updated :issue_commented. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. E.g. Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value. {{issue.parent.priority.name}} - Returns the priority of the subtasks's parent issue. These can be combined with other date and time smart values. {{build.refs}} returns the refs of the build, e.g. You could then use this to count the number of issues returned. Please try just two around each side: Of note: what is the type of your field? Each field is a list of changes. [Custom Field]}} - Returns the value in an epic's custom field. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. First, you need a sample from the webhook payload data. Learn how to find the right Jira automation smart values for your issue fields in Jira Cloud. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. You can access all fields of the Epic. Is the IF statement available for Server version? Developers. The issue is not so much with the smart values itself, but with the {{#if }} statement. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. Also provides the customer portal URL for Jira Service Management issues. You're on your way to the next level! {{sprint.startDate}} - Returns the start date of the sprint. There should be a locked field named either "Request Type" or "Customer Request Type" there. 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. 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, Version created, Version updated, and Version released triggers. 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. {{issue.affectedServices.dependentServices}}- Returns the list of services that this issue's services depend on. Returns information related to the created feature flag. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. {{attachment. The spacing format is mentioned in the following article: Smart-value-in-published-article-doesn-t-work. 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. Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. These smart values can only be accessed through other root keys (e.g{{deployment.environment}}). 4877576. We will ensure the story points of the parent and sub-task always remain in sync. Understand the general concepts and best practices of automation in Atlassian Cloud products. {{deployment.environment}} returns information related to the deployment environment. You can view the audit log of an individual rule, project-wide or at a global level. {{sprint.isClosed}} -Returnstrueif the sprint has closed, andfalseif not. {{issue.watchers.emailAddress}} - Returns the watcher's email address. The legacy Insight App will reach end of service on March 31, 2022. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. {{comment.properties}} - Accesses any comment property. Challenges come and go, but your rewards stay with you. {{commit.repository.url}} returns the repositorys URL. Exclusive to the Approval required trigger: {{approval.initiator}} - Returns account id of initiator of request. You must be a registered user to add a comment. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. Accesses an insight field's full name, key, or summary. You can specify a default value to prevent this. {{issue.InsightField}} - Returns the issue summary and issue key, {{issue.InsightField.key}} - Returns the issue key, {{issue.InsightField.summary}} - Returns the issue summary. {{issue.watchers.displayName}} - Returns the watcher's display name. But it looks like functionality for the Jira cloud version. See all smart values related to Assets in Jira Service Management Cloud. Would be good and useful functionality to have. {{issue.timetracking.remainingestimate}} - Returns the value in the Time remaining field. {{branch.repository}} returns information related to the repository the branch belongs to. I would like the value that enters the text field to be the name of the sprint that created the trigger. Some issue properties are more complex, and theyve been described in their own sections on this page. If multiple values are changed (e.g. What goes around comes around! Returns the value of the Jira Service Managements rate custom field. Learn more about services in Jira Service Management. {{issue.reporter.displayName}} - Returns the issue's reporter. Keep earning points to reach the top of the leaderboard. Learn more about date and time smart values. Understand the general concepts and best practices of automation in Atlassian Cloud products. Jira Software Questions Smart value of trigger issue in automation Smart value of trigger issue in automation Eliyahu Klein Jan 09, 2023 Hi, I created an automation that created a value in a short text field. This is how you would return multiple responses using the smart value: Accesses information for a worklog entry that has just been logged against an issue. {{pullRequest.state}} returns the state the pull request is in - Open, Merged, or Declined. {{issue.fix.Versions.archived}} - Returns true if the fix version is archived, andfalse if not. [property]}} Returns a list of issues from a JQL search caused bythe Lookup issues action. For more information on when issues is available, seeRun a rule against issues in bulk. text {{/}}, or is this a Jira-cloud only functionality ? Connect thousands of apps for all your Atlassian products, Run a world-class agile software organization from discovery to delivery and operations, Enable dev, IT ops, and business teams to deliver great service at high velocity, Empower autonomous teams without losing organizational alignment, Great for startups, from incubator to IPO, Get the right tools for your growing business, Docs and resources to build Atlassian apps, Compliance, privacy, platform roadmap, and more, Stories on culture, tech, teams, and tips, Training and certifications for all skill levels, A forum for connecting, sharing, and learning. {{comment.internal}} - forJira Service Management comments, returns false if the comment is visible to customers. And the rule itself? :{{issue.properties.some.value}}. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. You can check this by navigating to the "Custom fields" page in the. This user must have the relevant permissions to trigger the rule, and complete any actions that may be performed. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. There is a feature request for it though - check outAUT-648. Otherwise, register and sign in. Automation is currently available in Jira Software Cloud and Confluence Cloud. Reviewing your audit logs is an effective way of debugging your rules. Because this smart value deals with multiple items (i.e: issues can have many fix versions), it can be used with the#symbol to apply the rule to each individual fix version. Learn more about list smart values. Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. {{versions.name}}- Returns the name of the affects version. For example, you might count how many issues have a priority of 'highest' and then send an alert. These smart values are only available for the Branch created development trigger. Find issues that have the same custom field date as trigger issue. {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. You could then use this to count the number of issues returned. 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. Your image appears to show too many curly-brackets around the value. If this issue is in an Epic, then epic refers to the Epic issue. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. They often contain sub-tasks, are stories that are part of a larger epic, or are simply linked to other issues using certain relationships. All of the issues found by the trigger are then treated as a single bundle of issues. Used with the Version created, Version updated, and Version released triggers. To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. This is more than enough for the interfce to update the issue over API and when it is finished, my automation will jump in and continue. This re-fetches the latest state of the issue from Jira. Learn more about working with related issues. {{version.startDate}} - Returns the version's start date. Smart values are one of the most potent ways to do so. These smart values can only be accessed through other root keys (e.g. {{comment.created}} - Returns the date and time of the comment. {{issue.updated}} - Returns the date the issue was updated. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. {{sprint.endDate}} -Returns the end date of the sprint. Examples of how you can use smart values to set the numerical value of an issues field in your Jira automation rules. https://bitbucket.org/account/repo/TEST-123-some-feature. {{deployment.name}} returns a human-friendly deployment name, e.g. Can you provide a screenshot of your result? {{pullRequest.destinationBranch.repository}} returns information related to the destination branchs repository. If this issue is a sub-task, then parent refers to the parent issue. Used with: the Create feature flag in LaunchDarkly action. Similar to{{issue. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. Returns the value of the Jira Service Managements rate custom field. twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. {{pullRequest.title}} returns the title of the pull request, e.g. Every rule starts with a trigger. There is no Jira smart value referring to approval name (so that we can differentiate when there are multiple approvals in a workflow). Is there a way to similar functionality in Jira-Server? https://bitbucket.org/account/repo/TEST-123-some-feature, {{pullRequest.destinationBranch.repository}}, https://bitbucket.org/{7faf7dee-a29b-4faa-bbc2-d7128a6d3278}/{315a3ecb-1f18-4953-98ae-5890f93073b5}/addon/pipelines/home#!/results/7, [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work], https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. I've tested it on my instance and it yielded only 1 sprint (out of 3 that are ongoing). Learn more about automation triggers. If multiple values are changed, use # to iterate over these. For example, when setting multiple Fix Versions, then you can iterate over these using{{#changelog.fixVersion}}{{toString}}. Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. Just for future visibility (for anyone else who finds this question), I tested a few of the options in the linked question above, and another question which was linked to from there. The smartvalue{{webhookData}}gets the root of the JSON payload. When an epic is marked as done move all of its stories to done also. [Custom Field].id}} - Returns the unique id for the field assigned by Jira. General triggers These triggers can be used across all Jira products. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. Wonderful :). In the below example, we're sending out a notification that someone has added a comment to an issue, perhaps as a Slack message. Automation rules are made up of three parts: triggers that kick off the rule, conditions that refine the rule, and actions that perform tasks in your site. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{attachment.author}}: Returnsthe user who added the attachment. You're on your way to the next level! {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. For example, PROJ-123. 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. Hi John, thanks a lot for your quick response. Properties are frequently used by add-ons and integrations to store values. {{attachment.author.emailAddress}}: Returnsthe email address associated with the user name. Acording with the documentation, Automation JQL condition suport smart values. For example, when an issue is transitioned you can see what status the issue transitioned from. Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. This applies to the legacy Insight app. {{commit.message}} returns the commit message, e.g. It resets every quarter so you always have a chance! {{issue.status}} - Returns the issue's status, {{issue.status.name}} - Returns the issue's status, {{issue.summary}} - Returns the issue's summary, {{issue.versions}} - Returns the issue'sAffects versions. 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. A list of issues that have been created in the rule. Send a daily Slack message with a list of issues still open in the Sprint.