Bill Sheboy Expert

Hi @mdeloreto -- Welcome to the Atlassian Community! You may do that with the Advanced Branching feature of automation rules, iterating over the selected values in the custom field: https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935 If you run into any…

Hi @Reynalda Torres What problem are you trying to solve by doing this, and how often does this need happen? That is, "why do this?" Knowing that might reveal other solution approaches the community can suggest. Until we know that... When your team created the Story, with any Subtasks or Checklists, they probably thought…

Hi @Ward Schwillens_ Schwillie Yes, and...to the suggestion by Mikael: The key to using chained rules with the Incoming Webhook trigger is each rule must only perform sequential processing. That is, there can be no branches which lead to parallel processing, or the next rule could start earlier than expected. The reason…

Hello, all! I rarely use the Related Issues Conditions because in my experience with automation rules: * they occasionally do not work as expected, showing no errors in the log, and * there is no documentation of how they are implemented to work. My hypothesis is there are timing problems between the gathering of issues…

Hi @Daniel Tardif Hernandez -- Welcome to the Atlassian Community! The image of the audit log details you show is not for the rule image you show. There are no Log actions in the rule, and so you may be comparing two different things. Regardless of that... The audit log shows the condition check on…

Hi @Laurent.Yen -- Welcome to the Atlassian Community! When all the issue types are checked, or unchecked, all of them display. And when you check types, they are added to the board URL in your browser. For example: myJiraURL/jira/software/c/projects/MYPROJECT/boards/123?issueType=10002 I hypothesize you saved a URL to…

Hi @Mike Monk First thing, I am not using Confluence automation rules, and so my suggestions are based on what I know about automation in general. Please test anything I suggest. With that out of the way... There are similar problems for Jira Automation for issue creation, linking, etc. With those, there is a Re-fetch…

Hi @Darren.Fairweather That is possible, and the challenging part is both the Issue Create and issue linking are slow operations...so some delay is needed. Here is an example to try: * trigger: issue created * action: re-fetch issue (I recommend always adding this action after the Issue Created as that trigger can fire so…

Hi @Max Boerma -- Welcome to the Atlassian Community! For a question like this, please also include an image of the audit log details showing the rule execution. That will provide additional context for what is happening. You may set the sprint to the trigger one by setting the Sprint field to: {{sprint.id}} To do this…

Here are some follow-up questions to try to diagnose this symptom: * What type of project is this: company-managed or team-managed? You may find that at the bottom-left of the screen expanding area. * Are those custom fields configured in Jira or from a marketplace addon / app? * Have you confirmed with admin functions…

Have you confirmed that is the correct smart value for the field, Release Sprint? If not, please do so before proceeding or the values will always be null. Once you have confirmed the smart value, please remove issue from the changelog value. For example: {{#changelog.releasesprint}}{{fromString}}{{/}}

The expression you show in the message body is this: {{#lookupIssues}} {{#if(equals(issueType.name, "Story"))}} * <{{url}}|{{key}}> ({{components.name}}: {{customfield_10260.diff(now).businessDays}} business days or {{customfield_10260.diff(now).hours}} total hours) {{/}} {{/}} I am unclear what you are doing with the…

Please try this update as you had some misplaced parentheses: {{issue.customfield_10149.diff(issue.customfield_101649).hours}}

Yes, I also find the Issue Linked trigger a bit unpredictable regarding which issue is the trigger versus the destination (for directional link types). The only solution I have found is to use if / else conditions in the rule and handle both cases: A --> B, and B --> A. You noted earlier that your rule was global (or…

Thanks for those images; this appears to be a Jira automation rule. When you want a count of issues meeting some criteria in a rule, I recommend using the Lookup Issues action with JQL on the conditions: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues For the matching issues, the…

Hi @Madar, Andrew Yes, and...to Nicolas's answer: In an automation rule, using the date / time formatting produces a text value, such as for sending a message or email. It does not impact the field itself (unless the field was plain text). Kind regards, Bill

Hi @Nick Haller Thanks for putting this information in one place! Yes, and...for the list: Custom formula fields are dynamic, and I do not believe they can be copied with rules. In some cases, the calculation could be recreated using rule logic for assignment to "delivery fields" outside of JPD ideas. People fields are…

Hi @Ricardo Acunzo -- Welcome to the Atlassian Community! Short answer: at this time, for a small number of replacement items I recommend solving a multiple find / replace scenario using a chain of replace() calls or replaceAll if regular expressions are needed. For…

Hi @Aaron Pavez _ServiceRocket_ I recall seeing another post about getting custom field names in rules, and my experiments showed: The {{issue.customfield_12345.name}} does not return the name for Jira Cloud, even though the docs indicate it…

Hi @Trudy P Claspill I do not believe Lookup Issues action for Jira Data Center supports custom fields yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 Perhaps using the {{issue.subtasks}} smart value will allow access to the field. If not, the workaround using Send Web Request and the issue search REST API would…

Hi @Matteo Gabanini There are several ways to do this: * use a series of if / else conditions to test and set the field * use an inline conditional statement to do this in one step * use a lookup table to map the values to the epic keys What do you want to do if the selection field has no value? Deciding that will impact…

Hi @[deleted] -- Welcome to the Atlassian Community! Yes, that is possible, although there is no single "walk over all fields to look for empty" technique that I am aware of. You could do this inline as the comment is created, testing each field of interest. Or, use conditions and created variables to build-up what you…

Hi @Bireshwar Das -- Welcome to the Atlassian Community! Are you a project admin for the project? If so, please use the left-side navigation for: project settings > features > and check if Reports is enabled. Kind regards, Bill

Hi @Christian For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @s_reyna I recommend contacting the vendor of the Exalate product for support on this question: https://marketplace.atlassian.com/apps/1213645/exalate-jira-issue-sync-automation-more?hosting=cloud&tab=support Kind regards, Bill

Hi @Amy Chamberlain Smart values are name, spacing, and case-sensitive...and, they often do not exactly match the display name of the field on the Jira pages. When an incorrect smart value is used, that collapses to null, and often does not work as expected. To learn the correct smart value (or custom field id) for your…

Hi @Елена Елена Your rule is making two edits to the same issue and so it is likely the updates are colliding. I recommend these changes to your rule: * Perform the Delete Link action first * After that, add a Re-fetch Issue action to reload the issue data * Replace the Issue Edit action with the Link Issues action to add…

Hi @Sunny Kanojia -- Welcome to the Atlassian Community! Adding to Tansu's answer: There is definitely an error in what you show for using the diff() function to set the "RCA TAT" field. Please post the smart value expression you have in that field so the community can offer suggestions. Thanks! Kind regards, Bill

Hi @BenWade Do you need a list of the issues or to just see which issues were added / removed after the sprint started? If you just need to see them, please check the Sprint Report or Burn Charts to check the scope change. Kind regards, Bill

Hi @Claudia Pillay -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…