Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. The trigger for automation is starting a new sprint (trigger = start sprint). TEST-123-some-feature, {{pullRequest.sourceBranch.url}} returns the URL of the source branch, e.g.https://bitbucket.org/account/repo/TEST-123-some-feature. Learn how to use these to interact with Jiras REST API. They can add significant power and complexity to your rules. Using this branch component, we can move away from the main trunk of the rule and work on related issues. Join now to unlock these features and more. Properties are frequently used by add-ons and integrations to store values. {{versions.description}}- Returns the description of the affects version. Try adding.accountId after coordinator (so{{#if(issue.assignee.equals(issue.coordinator.accountId))}}. Ive tried with both format that you mentioned: Thanks, Sofia. {{repository.name}} returns the name of the repository, e.g. {fieldChange.toString}}- Returns the new value as displayed. Learn more about automation triggers. The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. In this case, we want to perform an action on the parent of the sub-task so in the dropdown menu, we choose Parent. In the form that is shown, enter the details for your new webhook. 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. [Custom Field].name}} - Returns the visible label displayed on the left of the field. 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. Returns a list of issues from a JQL search caused bythe Lookup issues action. Can be combined with other user smart values. @Daniel Ramotowski, more people seem to be interested in this functionality, as there was already a ticket open forhttps://jira.atlassian.com/browse/JIRAAUTOSERVER-212 ! It may contain, for example, branches and tags names.This value is optional and may be an empty list. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. For example, when setting multiple Fix Versions, then you can iterate over these using{{#changelog.fixVersion}}{{toString}}. Get answers to your question from experts in the community, Smart value of trigger issue in automation. If youre an Automation for Jira app customer on a server product, check out the Automation for Jira documentation for Jira Server. For example, checking that all sub-tasks of a parent issue are resolved. TEST-123-some-feature, {{branch.url}} returns the URL of the branch, e.g. {{sprint.isStarted}} - Returnstrue if the sprint has started, andfalse if not. Here you can access any issue property. You could then use this to count the number of issues returned. This example shows the previous status id (for use in another Edit action). Accesses an insight field's full name, key, or summary. Share the love by gifting kudos to your peers. Each DevOps trigger makes relevant smart values available, related to commits, changesets, committer users . {{issue.comments.first.body}} - Returns the body of the first comment. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. Can be combined with other user-related smart values. Whenever you want to edit a field in Jira, use the Edit issue action. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. You can access the current watchers of an issue. {{pullRequest.createdDate}} returns the time (UTC) when the pull request was created, e.g. {{versions.name}}- Returns the name of the affects version. However sometimes the two fields holds the same person, resulting in an email with twice the same name. {{issue.Customer Request Type}} - Returns the customer request type for older Jira instances. {{version.name}} - Returns the version's name. Jira smart values in automation rules. Accesses time tracking estimates. You must be a registered user to add a comment. An environment represents a distinct ecosystem where products are deployed to. Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. You can access all fields of the parent. {{issue.watchers.displayName}} - Returns the watcher's display name. Every rule starts with a trigger. The rule is running too quickly after the issue is created. build#123, {{build.url}} returns the absolute URL of the build, e.g. The URL to access the issue. Possible states include pending, in_progress, successful, failed, cancelled, or unknown. Learn more about working with related issues. View topic Find the smart value for a field Learn how to find the right Jira automation smart values for your issue fields in Jira Cloud. : To do,In progress, orDone). Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. {{sprint.goal}} - Returns the sprint goal. Check out how we use smart values in our Jira automation template library. Do more to earn more! A representation of a release/version in Jira. However, you can now change the rule actor for your automation rules. A condition refines the rule so it wont act too broadly. Returns information related to the created feature flag. Join now to unlock these features and more. All of the issues found by the trigger are then treated as a single bundle of issues. global admin section. If this issue is a sub-task, then parent refers to the parent issue. You can also use this with, . The active issue. Learn more about using smart values with sections and lists. Available only for the pull request created trigger. 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. You can access all fields of the parent. I found both of these smart values seemed to work: If neither of these work for you, there are a few other options in those linked questions you can try :), {{sprint.name}} returns only the sprint that started and which triggered this automation event. Used with the Version created, Version updated, and Version released triggers. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. {{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. If multiple values are changed, use # to iterate over these. 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. These smart values are only available for the Commit created development trigger. {{issue. These smart values are only available for the Pull request created, Pull request declined and Pull request mergedtriggers. {{attachment.mimeType}}: Returnsthe file format of the attachment. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. This example shows the previous status for issues that are transitioned. @Simeon Ross - Any ideas on this one? Acording with the documentation, Automation JQL condition suport smart values. Can be combined with other date smart values. I recall there are suggestions in the backlog to add "wait until the prior step finishes" or "delay X seconds" actions. If multiple values are changed (e.g. The URL to access the issue. [Custom Field].id}} - Returns the unique id for the field assigned by Jira. {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. Use{{fieldChange.fromString}}and{{fieldChange.toString}}to access display values and{{fieldChange.from}}and{{fieldChange.to}}to access raw values (for a select field for example). Accesses the value in the issue'sAffects versions field. E.g. {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Learn more about using smart values with sections and lists. You can check this by navigating to the "Custom fields" page in theglobal admin section. If this issue is in an Epic, then epic refers to the Epic issue. You can access an insight field's full name, key, or summary through the following smart values: You can access a Tempo Account field's properties through the following smart values: To test what your smart value returns, use the, The active issue. Are you looking for server documentation? {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. This value supportsDate and Time functions, e.g. Examples of how you can use smart values to access and format items in a list, such as checkboxes and labels. Learn about the concepts and procedures related to automation in Jira Cloud. These smart values are only available for the Deployment successful, Deployment failed and Deployment status changed developmenttriggers. {{issue.created}} - Returns the issue's creation date. Affects version of an issue as a list. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). The comment that triggers the rule is stored in this smart value. 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). {{issue.reporter.displayName}} - Returns the issue's reporter. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. See all smart values used to insert conditional logic such as if/equals/and statements into comments and other text fields. {{comment.visibility.type}} - Returns the comment restriction type if any, e.g. 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. Smart values are variables that you can use in automation action configuration parameters. Can be combined with other date and time smart values. Learn more about services in Jira Service Management. {{sprint.startDate}} - Returns the start date of the sprint. General triggers These triggers can be used across all Jira products. {{version.id}} - Returns the version's ID. I suspect not. Accesses any issue property. {{webhookResponse.status}} - response code e.g. Returns information related to all feature flags created in throughout the rule or branch, as a list. 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. You could then use this to count the number of issues returned. Learn more about automation triggers. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). {{branch.name}} returns the name of the branch, e.g. Create a sample project and follow all of the breadcrumbs in the audit log of the rule details. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. 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. {{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. For example, if a rule uses the Create feature flag in LaunchDarkly action multiple times, {{flags} will return the information for all feature flags created, as a list. Because this smart value deals with multiple items (i.e: issues can have many Affects versions), it can be used with the#symbol to apply the rule to each individual component. {{commit.repository.name}} returns the name of the repository, e.g. Can you please assist us in working out the following issues? Examples of using smart values with dates. 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. for a select field. Examples of using smart values with lists. All of the issues found by the trigger are then treated as a single bundle of issues. {{flags.key}} returns the key of the feature flag. Accesses a Tempo Account field's properties. Actions are the doers of your rule. You can access an insight field's full name, key, or summary through the following smart values: You can access a Tempo Account field's properties through the following smart values: To test what your smart value returns, use the, The active issue. You can also use this with, . {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. I've tested it on my instance and it yielded only 1 sprint (out of 3 that are ongoing). 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. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. 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. The URL to access the issue. For example, {{attachment.first.size}} will return the file size of the first attachment. 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. Issues in Jira rarely exist in isolation. You could then use this to count the number of issues returned. Step 3: Set up the condition like this: Change the field's value to Issue Type. When an epic is marked as done move all of its stories to done also. {{issue.affectedServices.name}} - Returns the names of the issue's Affected services. for a select field. {{version.released}} - Returnstrue if the version is released, andfalse if not. Please share more details and screenshots in order to be able to help you. We do not currently support accessing fields within insight objects. All of the issues found by the trigger are then treated as a single bundle of issues. If you've already registered, sign in. {{issue.affectedServices.dependentServices}}- Returns the list of services that this issue's services depend on. {{addedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to addition of a value. . Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. {{issue.comments.author.displayName}} - Returns the comment authors. We select the exact field we are listening out for, in this case story points. 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. Use{{fieldChange.fromString}}and{{fieldChange.toString}}to access display values and{{fieldChange.from}}and{{fieldChange.to}}to access raw values (for a select field for example). Select Automations - Create Rule. {{issue.resolution}} - Returns the issue's resolution. https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}. OMGYou're right. Thanks for sharing the link back in this question, it might help others in future! See all smart values that take issue fields and convert them into JSON format. For example,jira:issue_updated :issue_commented. Navigate to your project in Jira. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. Note that repository contains additional nested smart values. Note that environment contains additional nested smart values. {{comment.body}} - Returns the body of the comment that triggered the rule. {{issue.comments.size}} - Returns the number of comments on the issue. Because this smart value deals with multiple items (i.e: issues usually have many comments), it can be used with the # symbol to apply the rule to each individual comment. Learn more about using smart values with sections and lists. In my use case I am receiving data from an API interface and the problem is that my automation is executed based on the transition and later there are a few branches, where one of them is selected based on some value in a custom field. {{worklog.visibility}} -available when the worklog is restricted, {{worklog.visibility.type}} -available when the worklog is restricted, {{worklog.visibility.value}} -available when the worklog is restricted. You were right, the rule was running too quickly, so the field was empty.I modify de trigger to give it time, and got the result expected. 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. Learn more about list smart values. ), then type 'webhooks'. You can also use the quick search (keyboard shortcut is . {{issue.updated}} - Returns the date the issue was updated. A selection of smart values make Jira issue details readily available for Automation for Jira rules. {{versions.releaseDate}}- Returns the affects version's release date. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). What third-party applications can I integrate with? {{build.refs}} returns the refs of the build, e.g. This value supportsDate and Time functions. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. [Custom Field].description}} - Returns the text displayed below the custom field viewed in the Simple Search column. 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, 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, Automation for Jira documentation for Jira Server.