[feature/ISSUE-123-some-work, feature/ISSUE-456-more-work]. {{pullRequest.destinationBranch.repository}} returns information related to the destination branchs repository. 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. {{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. 4877576. 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. They allow you to perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Returns the issue's comments. Learn more about user smart values. 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. . {{comment.author}} - Returns the ID of comment's author. action: log to the audit file this value. {{issue.resolution}} - Returns the issue's resolution. {{commit.repository}} returns the information related to the repository. In your site, the rule actor will be set as Automation app user. See all smart values that can manipulate the values of items in a list. A deployment represents the process in which a product is released in an environment. There should be a locked field named either "Request Type" or "Customer Request Type" there. To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. Navigate to your project in Jira. 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. At the same time, it would be to good to mention that it is Jira-cloud functionality only. Also provides the customer portal URL forJira Service Management requests. Otherwise, register and sign in. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. Affects version of an issue as a list. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. For smart values related to the Insight feature in Jira Service Management, see Jira smart values - Assets. Learn more about working with related issues. {{commit.repository.url}} returns the repositorys URL. Learn more about automation triggers. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). You can also use the quick search (keyboard shortcut is . A branch represents an independent line of development. {{createdBranch.product}} - returns the product that the branch was created in (for example, Bitbucket). The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. When a PR is merged in Bitbucket/GitHub/GitLab, then transition the issue in Jira. I created an automation that created a value in a short text 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. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. If this issue is in an Epic, then epic refers to the Epic issue. Using this branch component, we can move away from the main trunk of the rule and work on related issues. {{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). Join now to unlock these features and more. Learn more about using smart values with sections and lists. You're on your way to the next level! 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. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. The following smart values are available to access and format development information from a connected source code management tool. If more than one flag has been created throughout the rule, {{flag}} will return the most recently-created flag. PROJ-213, {{issue.epic.status.name}} - Returns the epic's status, e.g. Keep earning points to reach the top of the leaderboard. 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. Each field is a list of changes. 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. "sd.public.comment".internal}}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. {{pullRequest.state}} returns the state the pull request is in - Open, Merged, or Declined. TEST-123-some-feature, {{branch.url}} returns the URL of the branch, e.g. {{issue. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. And we have lots more automation templates and guides for you to use and learn from in the automation template library. Andit appears you are using Server/Data Center version, as the Re-fetch action does not have the "delay rule" option for Cloud. Access information related to the last branch that was created. Is the IF statement available for Server version? Note that repository contains additional nested smart values. You can access all fields of the Epic.
Solved: Using Automation to Link issues in a workflow with This value won't work for any other trigger, even if a comment was added as a result (e.g.
Jira Automation: Building New Rules in 5 Easy Steps - Hevo Data Learn about the concepts and procedures related to automation in Jira Cloud. See all smart values related to Assets in Jira Service Management 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. 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)
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}}. Ive tried with both format that you mentioned: Thanks, Sofia. Accesses a Tempo Account field's properties. There should be a locked field named either "Request Type" or "Customer Request Type" there. Smart values are variables that you can use in automation action configuration parameters. Otherwise, register and sign in. They often contain sub-tasks, are stories that are part of a larger epic, or are simply linked to other issues using certain relationships. Get answers to your question from experts in the community, Smart value of trigger issue in automation. Your image appears to show too many curly-brackets around the value. The example below lists each person watching the issue - both their display name and their email address - in bulletpointform. {{version.id}} - Returns the version's ID. These smart values can only be accessed through other root keys (e.g. {{issue.url.customer}} - Returns the customer portal URL (forJira Service Management requests). Syntax example The smartvalue { {webhookData}} gets the root of the JSON payload. Or you could count how many issues have the same label, same fixVersion, etc.
These smart values are only available for the Deployment successful, Deployment failed and Deployment status changed developmenttriggers. Note that repository contains additional nested smart values. For more information on when issues is available, seeRun a rule against issues in bulk. {{issue.duedate}} - Returns theissue's due date. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. {{comment.properties. 7, {{deployment.url}} returns the absolute URL of the deployment, e.g. {{sprint.name}} - Returns the sprint name. {{version.description}} - Returns the version's description. 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. See all smart values used to insert conditional logic such as if/equals/and statements into comments and other text fields. 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. That looks a little odd. Triggers can be set to run manually, based on a condition you set or scheduled. This example returns an issue's previous type, after it has been changed. {{issue.reporter.displayName}} - Returns the issue's reporter. Used with: the Send web request action (Wait for response enabled). {{comment.body}} - Returns the body of the comment that triggered the rule. {{rule.actor}} - Accesses the rule actor user. Refers to the original issue that triggered the rule; used when you branch the chain. {{attachment.filename}}: Returns the filename of the attachment. You can check this by navigating to the "Custom fields" page in theglobal admin section. This can be almost anything you want.