Bill Sheboy Expert

Hi @Lexi Huefner Have you tried using the parent and child syntax for the cascading field, as described here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Cascading-select-custom-field Kind regards, Bill

Yes, I understand how the last works. With your iterator structure, the use of last is placed such that there should not be a trailing comma (due to the filter)...unless there is something present.

Thanks for that information, Patrick! As the team appears to be regularly using the Kanban board, what do you think about making the delay visible on the board, using either card colors or a quick filter? You could use this JQL to detect for all days, not just business days: project = myProjectName AND NOT status CHANGED…

Hi @Patrick Parson -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? Knowing that will help the community provide better suggestions. Thanks! Until we have that info... What you ask is not possible with out-of-the-box features... * If you have a marketplace addon for JQL it might be…

Hi @[deleted] Yes, there is...If you want to check for EMPTY or not "XYZ" you could use this: project = myProjectName AND ( labels IS EMPTY OR labels NOT IN (XYZ) ) If you want there to always be a label, and just not XYZ, you could use this: project = myProjectName AND labels IS NOT EMPTY AND labels NOT IN (XYZ) To learn…

After saving a filter with a name, users can subscribe to it, choosing the cadence for it to send an email of the results. This option is available from your list of filters. Please look here for more information on doing…

Please take a look earlier in this thread where the variables are created to do this: varRemoveLabels and varAddLabels. Instead of creating variables, you would use the expressions directly in two different issue updates with JSON, with the issue re-fetch between them.

First thing, thanks for that information as I was able to reproduce the symptom you are seeing! Next thing: I recommend submitting a ticket to the Atlassian support team for this one. There appears to be some remaining thing/object after the smart value, list filter, perhaps caused by this syntax using the iterator with an…

Thanks for clarifying, @Cory Tsang I have not tried this, but it appears those links are "remote issue links", and there is a REST API to manage them: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-remote-links/#api-group-issue-remote-links Perhaps you could extract the URL from the description…

HI @Anil What have you tried thus far to do this? If you have a rule you are working on, please post images of your complete rule and the audit log details showing the execution...and describe what is not working as you expect. That will provide context for the community to offer suggestions. If you have not started a rule…

I thought you were trying to use this regular expression in an automation rule, in which case the entire expression would be enclosed in quotation marks...unless it is already in a created variable. If not in a rule, how are you using this regular expression?

Hi @Tobias Have you considered the idea of creating saved filters for the relevant issues, and then using subscriptions to remind the team leaders to create any reporting? That seems a simple approach to solve what you have described. Kind regards, Bill

Hi @Josiah Brown -- Welcome to the Atlassian Community! Often the challenge is when there are nested quotation marks, as it seems you are trying: one set for the format() and another wrapping the regular expression. I believe a work-around is to create the regular expression as a variable using Create Variable, and…

Hi @Marc Formisano -- Welcome to the Atlassian Community! Adding to the answer from @Darryl Lee ...please consider the answers to these questions as they may help the community offer suggestions: Are you using Jira Cloud or Server/Data Center? What is the type of the field, "worked iterations"? Is your scenario "when I…

Hi @Richardson_ Jordan _CGI Federal_ If you mean with an automation for Jira rule, the answer is probably "yes". The only limitation is if the specific custom field is supported by automation rules. Do you have an automation rule already? If so, please post images of your complete rule and the audit log details showing the…

Hi @Rick Moerloos When I tested your first smart value expression for removing the teamLabels it did not leave any trailing commas for several test scenarios. Would you please post an example where it did leaving a trailing comma? Also I recommend writing that expression directly to the audit log as that may confirm if the…

Hi @Adam Ziecik First thing: I am using Jira Cloud and so I cannot test my suggestions on this one... Next, it appears Atlassian has started work on adding the Create Variable action to the Server/Data Center version of automation rules. You can follow this suggestion for progress…

Hi @Michael Couillard Yes, and...to the answer provided: Do you ever expect multiple "bug" references in a single text line of the field? If so, consider first splitting up the field as the match() function can only find the first entry per text line. For example: {{issue.Testing Notes.toLowerCase().split("\n").join("…

Melissa, will the "less than" always work if the values are reversed in magnitude? If not, you can enforce the comparison order with the absolute value operator, abs, added to the end of that expression.

Sorry, I should have clarified earlier...I believe with the expression you showed originally you were encountering two problems: * get takes text parameters for lookup tables, and * the scoping problem in list iterators, and so it cannot "see" the table. You could verify this by hard-coding a status id (or name) as text in…

Hi @Tanguy Crusson Thanks again for the responsiveness from the JPD team! Kind regards, Bill

That seems to match "as implemented" as the keys passed to get() for lookup tables must be text (as opposed to the get function for lists which are numeric).

Sounds like the advanced compare is a text compare, and not a numeric one! And one of those values is not dropping unnecessary zero value, decimals digits. So a couple of work-arounds are... * use the format() function to force the values to have the same format for comparison * use a single math operation and compare to…

Hi @Mimi Peters From what you describe, you can do that using the built-in math operations for automation rules, as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ Kind regards, Bill

Hi @Sam Adams When you have multiple labels you want to add (for the linked issues), you will need an "add" clause for each one in the JSON. This can be done by iterating over the issue links in the list to build a JSON expression for each. Please try that approach and let me know if need more details. Kind regards, Bill

I was not suggesting to try "copy from parent" again from the edit options. Instead you can try editing the field and entering the smart value directly: {{issue.parent.myCustomField}} When you do this, the smart value expression will appear below the edit value, and you can select it so the rule will use it.

Hi @Melissa Kibrick Yes, and...to Trudy's answer: if you post images of your complete rule and the audit log details showing the rule execution those may help identify the cause, and exclude any causes from the rule structure/organization. Thanks! Kind regards, Bill

Hi @Margots Kapacs This is intentional to prevent errors from creating looping in rule execution. When you want one rule to trigger another through changes to issues, in the "downstream" rule to be triggered, change the setting in the rule details to "Allow Rule Trigger". Kind regards, Bill

Hi @Peter Heidorn Please look here for the answer from Atlassian on this symptom, as they describe improving the design to prevent this: https://community.atlassian.com/t5/Jira-Product-Discovery-questions/1000-Sub-issues-limit/qaq-p/2341506 Kind regards, Bill

Let's try this...When an issue has a parent, some of the fields appear to be directly available to a rule, such as like below. This does not always work for all fields; if it did a single rule could pull in a lot of issues/data in a chain. {{issue.parent.myCustomField}} I believe with the relationships your issue is using,…