jira smart values trigger issue
They kick off the execution of your rules. In the below example, we list each fix version that the issue has been added to, followed by the version's release date, in bullet point form. {{repository.name}} returns the name of the repository, e.g. {{version.releaseDate}} - Returns the version's release date. 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. Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. Jira smart values in automation rules. 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. You could then use this to count the number of issues returned. Your thorough reply here helped me in a completely different use case. Note that repository contains additional nested smart values. It is better to use this than name as it cannot be changed. If a field or value doesn't exist, it will return an empty value:{{invalid reference}}. Learn more about list smart values. {{rule.actor}} - Accesses the rule actor user. That is not the correct custom field id for the field you want. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. A build represents the process in which files are converted into their final consumable form. This value won't work for any other trigger, even if a comment was added as a result (e.g. These smart values are only available for the Build successful, Build failed and Build status changed development triggers. Used with: the Create feature flag in LaunchDarkly action. You can view the status of an automation rule to identify if the rule is currently active or not. all fields available to{{issue}}are available here as well. Allows access to data that was sent along with the incoming webhook, for example, the body of the webhook request. {{deployment.state}} returns the state of the deployment. Smart values are variables that you can use in automation action configuration parameters. Accesses the previous issue created in the rule. Reviewing your audit logs is an effective way of debugging your rules. {{createdBranch.product}} - returns the product that the branch was created in (for example, Bitbucket). {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. Do more to earn more! To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. View the list of available triggers. Examples of how you can use smart values to set the numerical value of an issues field in your Jira automation rules. Can be combined with other user smart values. For example, when an issue is transitioned you can see what status the issue transitioned from. This example shows the previous status id (for use in another Edit action). You can specify a default value to prevent this. Can be combined with other user-related smart values. {{issue.issueType.name}} -Returns the issue's type, for exampleStory,Bug, orTask. {{comment.properties}} - Accesses any comment property. Your smart value must identify a specific attachment for this to work. 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). {{rule.name}} - Returns the name of the rule that is currently running. @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 ! {{sprint.completeDate}} -Returns date the sprint was marked as complete. Now whenever this field changes in Jira, this automation rule kicks in. {{addedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to addition of a value. 4877576. Used by triggers that involve adding a comment, such as Issue commented, Issue transitioned, or Issue updated. {{branch.repository}} returns information related to the repository the branch belongs to. Accesses an insight field's full name, key, or summary. 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. You must be a registered user to add a comment. {{version.id}} - Returns the version's ID. In the below example, we're sending out a notification that someone has added a comment to an issue, perhaps as a Slack message. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). The rule is running too quickly after the issue is created. {{issue.fixVersions.name}} - Returns the name of the fix version. There is no Jira smart value referring to approval name (so that we can differentiate when there are multiple approvals in a workflow). However sometimes the two fields holds the same p. {{createdBranches.product}} - returns the products that the branches were created in. Learn more about automation triggers. Otherwise, register and sign in. You're on your way to the next level! What that error tells me one of three things is happening: Let's try this: immediately after your trigger, add two things: a) If the rule works after adding the re-fetch, the cause was #1, b) If the audit log does not show your date, it is either #2 or #3. {{issue. Challenges come and go, but your rewards stay with you. https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}. You can check this by navigating to the "Custom fields" page in theglobal admin section. E.g. Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. If multiple values are changed, use # to iterate over these. {{issue.reporter.displayName}} - Returns the issue's reporter. Set the Equals condition to true. 2020-07-20T07:00:00.0+0000. build#123, {{build.url}} returns the absolute URL of the build, e.g. {{commit.repository.name}} returns the name of the repository, e.g. You could then use this to count the number of issues returned. Access information related to all branches created in the rule, as a list. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. This smart value accesses the changelog, and a list of changes for each field. 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))}}. They must be met for your rule to continue running. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). {{issue.Customer Request Type}} - Returns the customer request type for older Jira instances. There are many ways you can edit a field. {{branch.repository.url}} returns the URL, e.g. 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. The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. {{versions.name}}- Returns the name of the affects version. Story points are integral for many agile teams. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. And we have lots more automation templates and guides for you to use and learn from in the automation template library. Learn more about automation triggers. {{attachment.mimeType}}: Returnsthe file format of the attachment. {{sprint.isStarted}} - Returnstrue if the sprint has started, andfalse if not. On successful request, you will be able access webhook response data using the following smart values: The worklog entry that has just been logged against an issue. @Simeon Ross - Any ideas on this one? {{deployment.environment}} returns information related to the deployment environment. For example, checking that all sub-tasks of a parent issue are resolved. For Jira Service Management requests only. In the form that is shown, enter the details for your new webhook. issue The active issue. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. They allow you to perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks. You're on your way to the next level! All of the issues found by the trigger are then treated as a single bundle of issues. Challenges come and go, but your rewards stay with you. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{issue.affectedServices.changeApprovers}}, {{issue.affectedServices.changeApprovers.displayName}}, {{issue.affectedServices.dependentServices}}, {{issue.affectedServices.dependentServices.tier}}, {{issue.Request Type.currentStatus.status}}, {{comment.properties. Step 3: Set up the condition like this: Change the field's value to Issue Type. {{issue.comments.last.body}} - Returns the body of the last comment. We will ensure the story points of the parent and sub-task always remain in sync. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. Share the love by gifting kudos to your peers. {{issue.assignee.displayName}} - Returns the issue's assignee.