{fieldChange.toString}}- Returns the new value as displayed. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. {{issue.resolution}} - Returns the issue's resolution. {{commit.repository.name}} returns the name of the repository, e.g. Challenges come and go, but your rewards stay with you. 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. {{issue.latest.description}} - Returns the status's description. Affects version of an issue as a list. [Custom Field].name}} - Returns the visible label displayed on the left of the field. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. Now whenever the story points of a sub-task changes, it will be reflected in the parent issue. 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? It resets every quarter so you always have a chance! Learn more about automation triggers. 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. View topic Examples of using math expression smart values Your thorough reply here helped me in a completely different use case. For example, {{attachment.first.size}} will return the file size of the first attachment. : To do,In progress, orDone). { {issue. Each of your rules will have an audit log that you can review to see when the rule was triggered, the final result of the execution, and any actions that may have been performed. And the rule itself? Find issues that have the same custom field date as trigger issue. Please raise suggestion ticket in our public tracker, https://jira.atlassian.com/projects/JIRAAUTOSERVER. Access information related to all branches created in the rule, as a list. Is the IF statement available for Server version? Which Jira-server version supports the use of smart value: "{{#if . }} this is only available for some triggers. {{issue.parent.priority.name}} - Returns the priority of the subtasks's parent issue. These smart values are only available for the Commit created development trigger. Use an IDE like Visual Studio Code to find the path. Used with: the Create feature flag in LaunchDarkly action. E.g. The rule actor is the user who executes a rule. 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.watchers.displayName}} - Returns the watcher's display name. {{attachment.author.timeZone}}: Returns the timezone the user is registered being in; this doesn't change dynamically based upon where the user logs in from, it is the timeZone registered in their user account. {{deployment.environment}} returns information related to the deployment environment. {{issue.issueType.name}} -Returns the issue's type, for exampleStory,Bug, orTask. {{issue.description}} - Returns the content in the issue'sDescriptionfield. For example, PROJ-123. {{sprint.name}} - Returns the sprint name. I've tested it on my instance and it yielded only 1 sprint (out of 3 that are ongoing). Issues in Jira rarely exist in isolation. I created an automation that created a value in a short text field. awesome commit handles everything, {{commit.url}} returns the absolute URL of the commit, e.g. Every rule starts with a trigger. {{branch.name}} returns the name of the branch, e.g. If youre an Automation for Jira app customer on a server product, check out the Automation for Jira documentation for Jira Server. They can add significant power and complexity to your rules. :{{issue.properties.some.value}}. Learn more about date and time smart values. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. Exclusive to the Approval required trigger: {{approval.initiator}} - Returns account id of initiator of request. I suspect not. {{issue.Request Type.requestType.name}} - Returns the customer request type. The URL to access the issue. Returns the value of the Jira Service Managements scale custom field. Can be combined with other date and time smart values. You can view the audit log of an individual rule, project-wide or at a global level. For example, when setting multiple Fix Versions, then you can iterate over these using{{#changelog.fixVersion}}{{toString}}. Accesses the previous issue created in the rule. These can be combined with other user smart values. "sd.public.comment".internal}}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. Click Create a webhook. You can also use this withlists. We select the exact field we are listening out for, in this case story points. {{changelog.issuetype}} - Changelog information for theIssue type field. These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. For example, you can set up your rule to only escalate an issue if it is high priority. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. Try adding.accountId after coordinator (so{{#if(issue.assignee.equals(issue.coordinator.accountId))}}. Accesses information related to a file attachment on an issue. my-awesome-repository. {{issue.fix.Versions.archived}} - Returns true if the fix version is archived, andfalse if not. It some places it pops up, but there is no real explanation. 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. Get answers to your question from experts in the community, Automation JQL condition: using smart values. The rule is running too quickly after the issue is created. For example, you might count how many issues have a priority of 'highest' and then send an alert. If multiple values are changed (e.g. A branch represents an independent line of development. {{deployment.name}} returns a human-friendly deployment name, e.g. build#123, {{build.url}} returns the absolute URL of the build, e.g. Used with: the Send web request action (Wait for response enabled). Create a sample project and follow all of the breadcrumbs in the audit log of the rule details. {{deployment.state}} returns the state of the deployment. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. {{version.description}} - Returns the version's description. I am glad to learn that helped you. If this issue is a sub-task, then parent refers to the parent issue. Learn more about using smart values with sections and lists. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. Approval required: accesses information when an issue that requires approval is created or updated, or when new approvers are added to an issue. 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 how to integrate your source code management tool with Jira Cloud, Visit the marketplace to integrate your build or deployment tool with Jira Cloud. Possible states include pending, in_progress, successful, failed, cancelled, or unknown. I've not been able to find such kind of information. {{approval.decision}} - Returns the final decision of the approval. Accesses the details of a subtask's parent issue. {{commit.hash}} returns the SHA1 hash of the commit, e.g.4877576951f3eda43625d3345058e702dad3df0d. What are conditions? Learn more about user smart values. 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.comments.last.body}} - Returns the body of the last comment. Go to Jira administration console > System > Webhooks (in the Advanced section). Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. . All properties available to{{issue}}are also available on this smart value. 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. 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. {{fieldChange.from}}- Returns the previous raw value, e.g. If this issue is in an Epic, then epic refers to the Epic issue. In this way, approval returns two different values depending on the trigger being Approval required or Approval completed - https://support . Your image appears to show too many curly-brackets around the value. 2020-07-20T07:00:00.0+0000. Can be combined with other user smart values. "sd.public.comment".internal}} -. {{fieldChange}}only contains the first changed 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. 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. {{comment.visibility.type}} - Returns the comment restriction type if any, e.g. You're on your way to the next level! 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! {{issue.fixVersions.description}} - Returns the description of the fix version. We use the following smart-value to sum up story points from all sub-tasks: {{issue.subtasks.Story Points.sum}}. Learn more about list smart values. Please try just two around each side: Of note: what is the type of your field? In progress. Using this branch component, we can move away from the main trunk of the rule and work on related issues. Please share more details and screenshots in order to be able to help you. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. A build represents the process in which files are converted into their final consumable form. They enable customizing automation actions to be useful for your team and your customers. 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) I would like the value that enters the text field to be the name of the sprint that created the trigger. {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. For example, you might count how many issues have a priority of 'highest' and then send an alert. {{createdBranches.product}} - returns the products that the branches were created in. You can view the status of an automation rule to identify if the rule is currently active or not. {{attachment.created}}: Returnsthe date and time the attachment was added to the issue. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. {{sprint.isStarted}} - Returnstrue if the sprint has started, andfalse if not. ISSUE-12: Fix bugs, {{pullRequest.url}} returns the absolute URL of the pull request, e.g.https://bitbucket.org/pull-request/182. The following smart values are available to access and format development information from a connected source code management tool. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. {{issue. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. Check out how we use smart values in our Jira automation template library. it is not supported in server version now. {{issue.key}} - Returns the issue's key, which is a unique identifier comprised of the project key and the issue's number. Thisshould not be usedsince it requires an expensive reload of issue data. Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. Accesses the value in the issue'sAffects versions field. Learn more about date and time smart values. I'll ask one of their team to update you here. 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. What goes around comes around! You could then use this to count the number of issues returned. Otherwise, register and sign in. 7, {{deployment.url}} returns the absolute URL of the deployment, e.g. Returns the value of the Jira Service Managements rate custom field. This applies to the legacy Insight app. {{approval.addedApprovers}} - Returns the set of approvers added to issue. In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- https://bitbucket.org/account/repo. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. {{commit.message}} returns the commit message, e.g. If multiple values are changed, use # to iterate over these. 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. Jira smart values in automation rules. The trigger for automation is starting a new sprint (trigger = start sprint). . Accesses information for the current running rule. {{deletedFieldChanged.values}} - Returns the value/values deleted. {{comment.properties}} - Accesses any comment property. {{branch.repository}}). [Custom Field].id}} - Returns the unique id for the field assigned by Jira. You can check this by navigating to the "Custom fields" page in the. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. Similar to{{issue. Learn more about automation triggers. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. If more than one flag has been created throughout the rule, {{flag}} will return the most recently-created flag. Learn more about using smart values with sections and lists. Join now to unlock these features and more. What third-party applications can I integrate with? Smart values in Jira automation. Can be combined with other date smart values. [Custom Field]}} - Returns the value in an epic's custom field. @Simeon Ross - Any ideas on this one? At the same time, it would be to good to mention that it is Jira-cloud functionality only. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. 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. A repository represents a collection of files and associated metadata. Do you have any idea how I find active sprint smart value? That looks a little odd. Reviewing your audit logs is an effective way of debugging your rules. For example, if the epic has a custom field calledInitiative, then{{issue.epic.Initiative}} will return the value in the Initiative field. TEST-123-some-feature, {{repository.url}} returns the absolute URL of the repository, e.g. {{issue.fixVersions.releaseDate}} - Returns the fix version's release date. {{issue.url}} - Returns the URL of the issue. Learn more about using smart values with sections and lists. Allows access to data that was sent along with the incoming webhook, for example, the body of the webhook request. For example, wheninvalid referencedoesn't contain a value, you can printHello worldusing{{invalid reference|"Hello world"}}. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. For example, if a rule is created that will comment on an issue when executed, the rule actor must have the Add comment permission, otherwise the rule will result in an error. {{versions.description}}- Returns the description of the affects version. With our simple no-code rule builder, you can create automation rules to take care of everything from the most simple repetitive tasks to the most complex scenarios - all in a few clicks. This smart value only works for issues that have been added to an epic. All of the issues found by the trigger are then treated as a single bundle of issues. {{branch.repository}} returns information related to the repository the branch belongs to. After testing, disable both the HTTP dump and access logs to avoid performance issues. 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))}}. role. Can be combined with other user-related smart values. Affects version of an issue as a list. Learn more about configuring time tracking. This will return a list of values, if the issue has more than one attachment. Returns information related to the created feature flag. {{comment.properties. They allow you to perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks. Examples of using smart values with lists. You can check this by navigating to the "Custom fields" page in theglobal admin section. Otherwise, register and sign in. Visit the marketplace to integrate your build or deployment tool with Jira Cloud. 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. {{build.refs}} returns the refs of the build, e.g. {{build.name}} returns the name of the build, e.g. The URL to access the issue. What third-party applications can I integrate with? Every rule starts with a trigger. Or you could count how many issues have the same label, same fixVersion, etc. Keep earning points to reach the top of the leaderboard. {{sprint.goal}} - Returns the sprint goal. Automation is currently available in Jira Software Cloud and Confluence Cloud. You're on your way to the next level! {{versions.releaseDate}}- Returns the affects version's release date. This was something we have added since the split and I suspect that the server team has not caught up. However sometimes the two fields holds the same person, resulting in an email with twice the same name. It may contain, for example, branches and tags names.This value is optional and may be an empty list. Learn more about services in Jira Service Management. {{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. There should be a locked field named either "Request Type" or "Customer Request Type" there. 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. General triggers include: Field value changed - when a field value is changed Form submitted - when forms attached to an issue are submitted The active issue. You can access the current watchers of an issue. Learn more about date and time smart values. I recall there are suggestions in the backlog to add "wait until the prior step finishes" or "delay X seconds" actions. action: Re-fetch issue (This will slow down the rule by reloading the newly created issue, as all of the data may not be ready when the rule runs.). text {{/}}, or is this a Jira-cloud only functionality ? Used with: the Clone issue, Create issue, and Create sub-tasks actions. 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. Learn more about using smart values with sections and lists. This re-fetches the latest state of the issue from Jira. Learn more about using smart values with sections and lists. {{issue.watchers.emailAddress}} - Returns the watcher's email address. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request.