Bill Sheboy Expert

The flag is a different field, named Flagged. Please use that field in the edit action, leaving the value as empty to clear it.

First, please stay engaged with the help @Piet Pieters is providing so you get one rule working correctly. Then, after you have decided the scenarios needed, you can copy that rule and adjust the triggers / conditions, as needed. For example with the Issue Created scenario... * trigger: issue created * action: re-fetch…

Apologies again...my original post had two typos: curly bracket instead of close parenthesis and missing curly bracket at end. Here is the corrected one: diff of values: {{issue.customfield_10109.diff(issue.customfield_10110).minutes}}

First, I recommend removing that complete JSON for your rule. Asking people to import you rule into their sites may be less helpful than posting images of your rule, the actions, and the audit log details. Next, please see my original recommendation, try to implement it, and if you run into challenges explain what is not…

Thanks for testing that with the rule action. And, the bot answer seems to be referring to smart values for issues, not for rule actions. A workaround you can use is calling the REST API endpoint to add the form to the issue using the Send Web Request action. You will need the list of the form id values for that (and…

Hi @FrancoB -- Welcome to the Atlassian Community! IMO, the match() function in automation rules does not consistently handle things like text containing newlines, and other formatting. As a result, it can terminate the searching earlier than expected. A workaround for that is to first replace all the newlines before the…

Hi @Jonathan Carvalho -- Welcome to the Atlassian Community! There appears to be some odd behavior for that function, perhaps related to time zones. Regardless... Perhaps try this instead, assuming your field is a date or date / time field: {{issue.employeeStartDate.minusBusinessDays(1)}} Kind regards, Bill

The function startOfDay() is a date / time value, and if your field "Scheduled Date/Time" is also date / time, they are unlikely to match exactly. Perhaps adjust to find values within "today" with this: project = "DC OPS Turnover" AND Flagged IS NOT EMPTY AND "Scheduled Date/Time" >= startOfDay() AND "Scheduled Date/Time"…

If you mean the issue's Flagged field, isn't that the one you want to clear? And so the scheduled trigger JQL could be: project = "DC OPS Turnover" AND Flagged IS NOT EMPTY AND "Scheduled Date/Time" = startOfDay() Then clear the Flagged field with the edit.

First for those writes to the audit log, please add some labeling to confirm what we are observing. For example: firstLevelLinkedIssueKey: {{firstLevelLinkedIssueKey}} Next, for more context please show images of the entire updated automation rule and of the entire audit log details for that rule execution. Those will help…

Hi @Andras Gombos I believe that change started rolling out at the end of June 2024: https://confluence.atlassian.com/cloud/blog/2024/07/atlassian-cloud-changes-jun-24-to-jul-1-2024#AtlassianCloudchangesJun24toJul1,2024-ImprovedsearchusingsummaryanddescriptionfieldsFD-63933 Based on this week's blog entry, the change is…

Hi @Igor Titov After your rule's trigger, please try adding conditions to check what is needed. For example, you could use the changelog smart value to test if the prior value was not empty with the smart value condition: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- Kind…

Hi @Gaurav Arora As you have multiple criteria (i.e., start date and id) to select the Sprint for the cloned issue, the rule would need to use the Send Web Request action to call the Jira REST API to gather the sprints for the project, filter as needed, and then select the one to use. Kind regards, Bill

Hi @Julien Rey What are your plans to update your KB article to handle the possibility of empty field values for the additions / removals with the dynamic JSON, beyond the disclaimer added at the end of the article? If the article cannot describe those changes, please consider removing that suggested solution to potential…

Do you only want to add the new users? If so, replace "remove" with "add". Next, have you confirmed there are users to add before attempting to make the edit? Finally, to help diagnose this, please write that entire expression to the audit log. That will help to confirm if there is something invalid in the JSON.

Yes, I expected that to still fail...and, you are only showing part of the audit log entry for the rule execution. Please show the entire log entry's details. That will show the writes to the log to confirm the smart values which were just added.

Would you please post images of the create variable actions and of the audit log details showing the rule execution? Thanks!

Are you using Jira Cloud or Server / Data Center? I believe that may impact the format of the link representation. You can confirm the representation by writing the comment to the audit log to see the format of the smart link. For example, this is what I see for Jira Cloud in a comment: here is a comment with a URL…

Although it is not obvious with the rule editor, many of the edit fields which have a dropdown values list have the ability to accept a smart value expression. Please try this with the Attach Forms action and a test rule: * in the edit field, type in a smart value representing the form * when you do, it will appear below…

Those final created variables, varAddedUsers and varRemovedUsers, are comma-separated value lists of users. They must be parsed to create the needed JSON syntax: https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html There are several possible edit scenarios (from the trigger issue's…

Greetings, everyone! Let's pause and try some basic diagnostics to help... @Jessica Rubeo , in your rule please add a write to the audit log with these expressions, and then run it, posting the audit log details from the execution: customfield_10109 equals: {{issue.customfield_10109}} customfield_10110 equals:…

Oops...my mistake; thanks, Trudy! We cannot see the write to the log in what was posted. Seeing what was written with the write to the audit log may explain why the Log Work action is failing. (Although I suspect removing the math function wrapper will help.)

Hi @Jessica Rubeo -- Welcome to the Atlassian Community! Adding to Trudy's suggestions: There is a typo in your write to the audit log: it is missing the closing parenthesis for the call to the diff() function. That is why it shows the "Error rendering smart-values..." Update: striking through this suggestion. Kind…

Hi @Devlend Maul The match() function does not handle text with newlines, and other formatting, well for fields like Comments and Description. One workaround to get better matches is to add a split(" ") immediately before the match() call, as that will reduce the scope the regular expression tries to search. For example,…

Awesome; I am glad to learn that helped! Regarding documentation, in the automation documentation on the match() function, it links to some regular expression information from the Java spec that rules are based…

Hi @Tom Scoggin Because the DEV value is a substring of DEV-APPROVAL, the expression for match() will need to exact match, perhaps using the start and end tokens: {{#if(labels.match("^(DEV)$").size.gt(0))}} Kind regards, Bill

Hi @craig_hill -- Welcome to the Atlassian Community! It is theoretically possible to use several automation rules to clone many parent / child issues and relink them correctly. Although, and IMO, such solutions are brittle as they are prone to timing problems from branching, waiting for issues to be created, handling…

Hi @marcus.glynn -- Welcome to the Atlassian Community! Those appear to be from the marketplace addon Rich Filters for Jira Dashboard, and not built-in features of Jira Cloud. Please check the vendor's documentation or contact their support…

Hi @Michael Robinson -- Welcome to the Atlassian Community! As Laurie described, there is no built-in way to do that yet. One possible workaround uses knowledge about how mentions are implemented, allowing searching of all text fields. Please note this is not just the comments field. To do this... * mentions are…

Hi @Natasha Richardson -- Welcome to the Atlassian Community! Rules do not support nested branching, and so a workaround for your scenario is: * once inside of the branch on the linked issues of the trigger issue... * use the {{issue.issuelinks}} smart value and list filtering / conditions to check the linked issues of…