Bill Sheboy Expert

Hi @Golan Shoval Gil -- Welcome to the Atlassian Community! My understanding is the pull request (PR) smart value {{pullRequest}} is only available to automation rules when one of the PR-related triggers is used: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--Pull-request-- Another…

Thank you for that information. To send one single email, please use the Lookup Issues action I noted: * remove the Send Email action from inside the branch * before the branch...* add a Lookup Issues action with JQL to find the child issues * add a Send Email action to list the issues, where...* the From date is the…

I am unclear how to mix those options as they seem mutually exclusive... To prevent display of a row with a 0 quantity, wrap each row with a conditional, smart value expression to test for a 0 or empty quantity: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ To display all rows,…

Thanks for that information! The log is showing the variable is empty. As the field is one of the text types, please change your created variable action to: * name: customval * smart value: {{lookupIssues.customfield_12971}} This will produce a comma-separated values list of the issue data. If you wanted those to have the…

I wonder if the Due Date field is empty...I see your rule is using the Issue Created trigger. That one can fire so quickly that some issue data may not yet be available to the rule. The fix for that is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule a bit,…

Hi @Luciano Nunes De Lima Yes, project-scope rules now count toward usage limits. Here is the September 2023 announcement when Atlassian changed the packaging model for how usage is counted: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update With that change, some rule actions do not count as…

Hi @Sérgio Baixo Yes, that is possible. The rule needs to have multiple-project or global scope to change issues in different projects. Your Jira Site Admin will need to change the rule scope using global automation, admin access. Kind regards, Bill

Hi @Ron Aisen What do you want to do when a quantity value is 0 or empty: * do not display that row in the table * display the row with a 0 Quantity and Cost Summary * something else Kind regards, Bill

Hi @Sathishkumar Sundaram For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions / branches, * an image of the…

Hi @Fabrice Gantois To match on several possible words in the field, please try using the Smart Values Condition with a regular expression: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#--smart-values---condition For example, the second value with the regular expression could be:…

Hi @Vasanta Kumaar When you use an Issue Fields Condition with the "contains" test, it is checking the entire value, and not a list of values. And thus your test on "GHE, Exepedia" does not match. And it has a typo, as that should probably be "Expedia". To match a list of values, please use the Advanced Compare Condition…

Hi @Dmitry Alabyan First, I would confirm the custom field exists in the new project. Next, a Jira Work Management (JWM) project could be team-managed or company-managed. For the team-managed ones, the custom fields are distinct for each project, and so... When an automation rule is copied from one to another (or between…

Hi @SilkeS Thank you for this information. With this change, what additional post-filtering features based upon such lozenges have the community organizers considered, such as selectable hiding of content from such partners to allow focusing on questions / answers from other customers and Atlassian team members (rather…

Awesome, and well done adding the extra steps needed!

Whatever the name of the variable is, the declaration and uses need to match. Let's try for some alignment checks: * please add a write to the audit log after the variable is created my variable is: {{whatever the name is now}} * test your rule * post an image of the audit log details showing the latest rule execution *…

Would you please post images of your Edit Issue Fields action and of the audit log details showing the rule execution? Thanks!

Thanks for that information, and please try what I suggested using the Lookup Issues action with JQL to get the data needed: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues * trigger: issue created * action: re-fetch issue * condition: issue type equals Request * condition: linked…

Hi @Erin E You could try one of the markup formats for links in the field: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=links Kind regards, Bill

Hi @Michael Zarucki -- Welcome to the Atlassian Community! Assigning issues based on a schedule for Jira Work Management (JWM) could be done using an automation rule and the Assign Issue action, with rule conditions to decide who to assign and when.…

Hi @JAMJAR -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions /…

Hi @Josh Schoenick For more context, please show images of your complete rule, the Edit Object action, and the audit log details showing the rule execution. Kind regards, Bill

Smart values are name, spacing, and case-sensitive. When an unknown smart value is used, that returns as null. Thus it appears your variable name does not match what is used in the edit's JSON. Please change them to match and re-test. Thanks!

Awesome; I am glad to learn that helped!

Hi @dsaveri -- Welcome to the Atlassian Community! Short answer: the syntax you are using is incorrect for logical conditions. I recommend pausing to review the syntax, and then incrementally creating your conditions, storing the results in created variables and writing them to the audit log for testing. Once they are…

Hi @Aristos Smirniotis When an automation rule accesses the smart values for the connected issues, it only loads a few of their fields, such as Key, Summary, Status, etc. These connected issues, smart values include at least: * {{issue.parent}} * {{issue.subtasks}} * {{issue.issuelinks}} If instead the rule pulled in all…

Hi @Abhishek -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions /…

Based on that log entry, there is something wrong with either your created variable or the edit. The audit log entry showing what you tried for the JSON is incorrectly, so update it to exactly match what you are using in the edit issue action. Next, please post an image of the create of customval and the edit.

Hi @Seenivasan K Adding to the suggestions from @Aaron Pavez _ServiceRocket_ In the linked post Aaron provided, that scenario was to Add Watchers, and so branching was appropriate. But you are trying to select values in a multiple-select user field, correct? If so, branching is a bad idea: advanced branching executes in…

Hi @Charisse Robison Yes, and...to Trudy's ideas: There are several open suggestions to fix the "design choice" which created multiple story points fields in Jira, such as this one. You may watch / vote for it to see progress: https://jira.atlassian.com/browse/JSWCLOUD-17173 Kind regards, Bill

Sorry, as I had a typo missing the closing quotation mark around the "fields" element. Please add that and re-test. FYI...stuff like this is a good reason to first create the JSON in an editor which highlights matching syntax (i.e., quotes, brackets, etc.) and once it is correct, add it to the rule editor.