The issue is not so much with the smart values itself, but with the {{#if }} statement. {{fieldChange}}only contains the first changed value. What goes around comes around! Special conditions and actions are available to create powerful rules that can work across complex issue relationships. [property]}} You can view the audit log of an individual rule, project-wide or at a global level. Learn how to use these to interact with Jiras REST API. Your image appears to show too many curly-brackets around the value. You could then use this to count the number of issues returned. 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. {{attachment.author}}: Returnsthe user who added the attachment. Can be combined with other user-related smart values. {{createdBranch.repository.url}} - returns the repositorys URL. Learn more about using smart values with sections and lists. Is the IF statement available for Server version? Learn more about user smart values. What third-party applications can I integrate with? 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. There are many ways you can edit a field. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. {{version.releaseDate}} - Returns the version's release date. Learn about the concepts and procedures related to automation in Jira Cloud. A list of issues that have been created in the rule. Get answers to your question from experts in the community, Smart value of trigger issue in automation. Learn more about configuring time tracking. And the rule itself? Returns the value of the Jira Service Managements scale custom field. They enable customizing automation actions to be useful for your team and your customers. You can find some automation templates to help you get started within the product library. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. You can access all fields of the Epic. If multiple values are changed, use # to iterate over these. Returns the value of the Jira Service Managements rate custom field. Accesses the values in an issue'sAffected services field. {{issue.parent.priority.name}} - Returns the priority of the subtasks's parent issue. For Jira Service Management requests only. Examples of using smart values with lists. Looking forward to see it implemented soon! Possible states include pending, in_progress, successful, failed, cancelled, rolled_back, or unknown. But it looks like functionality for the Jira cloud version. In this template, we show you how to sum up the story points of all sub-tasks then update the parent issue with this value. These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers. If you've already registered, sign in. my-awesome-repository. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. First, you need a sample from the webhook payload data. And we have lots more automation templates and guides for you to use and learn from in the automation template library. Or .displayName if accountId doe not work as hoped. These can be combined with other date and time smart values. Share the love by gifting kudos to your peers. this is only available for some triggers. Accesses a Tempo Account field's properties. {{versions.description}}- Returns the description of the affects version. If this issue is a sub-task, then parent refers to the parent issue. I am glad to learn that helped you. Any idea if this will be added, and if so when? {{issue. Andit appears you are using Server/Data Center version, as the Re-fetch action does not have the "delay rule" option for Cloud. {{issue. {{branch.name}} returns the name of the branch, e.g. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. They can add significant power and complexity to your rules. {{comment.visibility.type}} - Returns the comment restriction type if any, e.g. Added by: Sprint created, started or completed triggers. Affects version of an issue as a list. Using this branch component, we can move away from the main trunk of the rule and work on related issues. I'll mention the docs discrepancies to the person that maintains our documentation. {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. Is the IF statement available for Server version? Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. Used to access information about an issue's epic. {{issue.epic. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. 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. 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. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. {{sprint.startDate}} - Returns the start date of the sprint. Examples of using smart values with text strings. all fields available to{{issue}}are available here as well. I've not been able to find such kind of information. These can be combined with other user smart values. 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. {{approval.decision}} - Returns the final decision of the approval. E.g. For example, {{attachment.first.size}} will return the file size of the first attachment. FR Jira Dev Aug 05, 2021 I currently have an Automation workflow that creates multiple tasks and subtasks. Learn about the concepts and procedures related to automation in Jira Cloud. Learn more about date and time smart values. For example, you might count how many issues have a priority of 'highest' and then send an alert. The trigger for automation is starting a new sprint (trigger = start sprint). Please share more details and screenshots in order to be able to help you. View the list of available triggers. Simply combine these components to create rules that can do anything from auto-closing old issues to notifying specific teams when a release has been shipped. 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. See all smart values related to accessing Jira project details. If youre an Automation for Jira app customer on a server product, check out the Automation for Jira documentation for Jira Server. For more information on this, see Configuring a webhook later on this page. Keep earning points to reach the top of the leaderboard. If a condition fails, the rule will stop running and no actions following the condition will be performed. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. With the 're-fetch issue data' action (which I seldom use), I noticed that this can put the automation execution on-hold for the whole 5 seconds! Allows access to data that was sent along with the incoming webhook, for example, the body of the webhook request. The URL to access the issue. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. 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. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Examples of how you can use smart values to set the numerical value of an issues field in your Jira automation rules. Accesses information for the version that triggered the rule. This smart value requires an expensive reload of issue data and should only be used in situations where subsequent actions need to have visibility of the latest state of an issue, e.g. 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. This value supportsDate and Time functions. Available anywhere smart values are supported, to access the value of a field that has changed. Available only for the pull request created trigger. Smart values are variables that you can use in automation action configuration parameters. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. What third-party applications can I integrate with? {{commit.repository}} returns the information related to the repository. Accesses the value in the issue'sAffects versions field. General triggers These triggers can be used across all Jira products. Select the Issue fields condition from the New condition drop-down menu. {{issue.assignee.displayName}} - Returns the issue's assignee. {{issue. They allow you to perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks. {{issue.comments.author.displayName}} - Returns the comment authors. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. Navigate to your project in Jira. Smart values - syntax and formatting; Jira smart values - issues; Jira smart values - conditional logic; . Prints the issue key and its status (e.g. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). Challenges come and go, but your rewards stay with you. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. Join now to unlock these features and more. Can be combined with other date smart values. Accesses time tracking estimates. Approval required: accesses information when an issue that requires approval is created or updated, or when new approvers are added to an issue. Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. Triggers can be set to run manually, based on a condition you set or scheduled. 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. Note that repository contains additional nested smart values. Find issues that have the same custom field date as trigger issue. This will return a list of values, if the issue has more than one attachment. What third-party applications can I integrate with? {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value. {{issue.Story Points}} - Returns the issue's story point estimate (company-managed Jira Software Cloud only). See all smart values that access and manipulate Jira issue data such as sprint, parent, or version. Go to templates. 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. {{version.startDate}} - Returns the version's start date. That is not the correct custom field id for the field you want. Is there any information on the web available about the "{{#if functionality)? All of the issues found by the trigger are then treated as a single bundle of issues. Used with: Create branch in Bitbucket, Create branch in GitHub, and Create branch in GitLab actions. Returns the value of the Jira Service Managements scale custom field. The rule is running too quickly after the issue is created. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. Visit the marketplace to integrate your build or deployment tool with Jira Cloud. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. When an epic is marked as done move all of its stories to done also. The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. {{attachment.author.emailAddress}}: Returnsthe email address associated with the user name. For more information on when issues is available, seeRun a rule against issues in bulk. {{commit.repository.name}} returns the name of the repository, e.g. [xxx].size}}: Returnsthe file size of a specific attachment. {{issue.components.name}}- Returns the values in the issue'sComponentfield. Each field is a list of changes. There should be a locked field named either "Request Type" or "Customer Request Type" there. it is not supported in server version now. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. The rule triggers on 'Issue created' and is followed by the 'Send web request' component. Is there a smart value that returns me only the name of the trigger sprint or at least only the name of the open sprint? action: log to the audit file this value. You're on your way to the next level! Accesses information for the current running rule. 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. This value supports Date and Time functions. Properties are frequently used by add-ons and integrations to store values. {{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). 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. This example returns the new value of an issue'sSummary field after it has been changed. Examples of how you can use smart values to manipulate and format dates in your Jira automation rules. - theIssue transitionedtrigger). You can access all fields of the Epic. Developers. Smart values in Jira automation. Every rule starts with a trigger. You can also trigger rules to run from third party services like Bitbucket or GitHub. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. for a select field. These smart values can only be accessed through other root keys (e.g{{deployment.environment}}). Refers to the original issue when you branch the chain. A deployment represents the process in which a product is released in an environment. 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. To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. Connect your source code management, build or deployment tool to use these smart values. {{addedfieldChange.values}} - Returns the new value/values added. As ever, test this rule out in your own instance. Conditions allow you to narrow the scope of your rule. It some places it pops up, but there is no real explanation. Learn how to find the right Jira automation smart values for your issue fields in Jira Cloud. 2020-07-20T07:00:00.0+0000. Accesses information related to a file attachment on an issue. Share the love by gifting kudos to your peers. Learn more about user smart values. Also provides the customer portal URL for Jira Service Management issues. As for if and when the support will go to server, I have no idea. You can access all fields of the parent. Join now to unlock these features and more. {{addedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to addition of a value. If a customer has not responded to an issue in 5 days, close the issue and leave a comment. 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. After testing, disable both the HTTP dump and access logs to avoid performance issues. Affects version of an issue as a list. Learn more about list smart values. {{sprint.goal}} - Returns the sprint goal. Note that repository contains additional nested smart values. Returns a list of issues from a JQL search caused bythe Lookup issues action. Triggers, conditions, and actions are the building blocks of automation. You can also use this withlists. {{attachment.author.accountId}}: Returnsthe ID associated with the user name. { {issue. This value won't work for any other trigger, even if a comment was added as a result (e.g. {{issue.parent.key}} - Returns the issue key of the subtask's parent issue. {{issue.affectedServices.tier}} - Returns the tiers of the issue's Affected services. In the following example, we list each comment that an issue has, and include the author and creation date/time: In this example, we return the name of the person who added the last comment on an issue: Used to access the values in an issue's Components field. {{issue.watchers.displayName}} - Returns the watcher's display name. 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. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. See all smart values used to insert conditional logic such as if/equals/and statements into comments and other text fields. . {{issue.watchers.emailAddress}} - Returns the watcher's email address. The issue smart values are used to access information related to the rules active issue, which is the issue the rule is currently acting on. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. {{issue.created}} - Returns the issue's creation date. You can check this by navigating to the "Custom fields" page in theglobal admin section. Learn more about user smart values. In this way, approval returns two different values depending on the trigger being Approval required or Approval completed - https://support . Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. If you've already registered, sign in. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. Go to Jira administration console > System > Webhooks (in the Advanced section). Note that environment contains additional nested smart values. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. {{flag.name}} returns the name of the feature flag. 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. 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. {{issue.fix.Versions.archived}} - Returns true if the fix version is archived, andfalse if not. [property]}}, you can also access custom field information on your issues. If a rule is inactive, it will not execute until it is enabled. 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 also use this withlists. Only one word but It changes the whole picture. Learn more about date smart values. I created an automation that created a value in a short text field. Can be used with both Approval required and Approval completed triggers: {{approval.createdDate}} - Returns creation date of approval. Can be combined with other user smart values. They must be met for your rule to continue running. You can check this by navigating to the "Custom fields" page in theglobal admin section. It looks like our Jira-server does not the{{#if }} statement :(, Get answers to your question from experts in the community, Share a use case, discuss your favorite features, or get input from the community, Smart value use of "{{#if }} does not seem to work, {{#if(issue.assignee.equals(issue.coordinator.accountId))}}. You must be a registered user to add a comment. You can also use the quick search (keyboard shortcut is . {{changelog.issuetype}} - Changelog information for theIssue type field. Otherwise, register and sign in. For example, if the epic has a custom field calledInitiative, then{{issue.epic.Initiative}} will return the value in the Initiative field. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. 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. awesome commit handles everything, {{commit.url}} returns the absolute URL of the commit, e.g. Issue commented, Added by: Clone Issue Action, Create Issue Action, Create Sub-tasks Action, A list of issues that have been created in the rule, The type of event that triggered the rule such as: jira:issue_updated :issue_commented. Use an IDE like Visual Studio Code to find the path. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. {{branch.repository}}). Learn more about date smart values. Syntax example The smartvalue { {webhookData}} gets the root of the JSON payload. Do more to earn more! 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 arehere). Also provides the customer portal URL for Jira Service Management issues. "sd.public.comment".internal}} -. Access information related to the last branch that was created. {{issue.issueType.name}} -Returns the issue's type, for exampleStory,Bug, orTask. Triggers: Triggers wait for defined events to take place in your Jira instance and will then execute the automation rule. 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. {{createdBranch.product}} - returns the product that the branch was created in (for example, Bitbucket). This re-fetches the latest state of the issue from Jira. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. 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. If this issue is a sub-task, then parent refers to the parent issue. 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. Used with the Version created, Version updated, and Version released triggers. You can access the current watchers of an issue. Added by: Jira Triggers that edit an issue, All the fields that were changed.