Bill Sheboy Expert

Thanks for that information, and let's look at a simple example for one of the cases: * trigger: field value changes for Start date * branch: to parent* action: lookup work items, with JQL of* parent = {{issue.key}} * smart values condition: to confirm a value is found...* first value: {{lookupIssues.Start date.min}} *…

Hi @Cali -- Welcome to the Atlassian Community! That information is not available from the REST API yet and so rule cannot see it either. Here is a suggestion to add that capability: https://jira.atlassian.com/browse/JRACLOUD-93136 Kind regards, Bill

I do not believe there is anything built-in to do this. There is no built-in, generic-handle-all-possible-cases parser for field content. And, such a parser would need to identify steps to take when: * the field is updated / cleared, * the created work items are tampered with, * what to do when an Atlassian outage prevents…

Hi @Christian Gonzalez I suggest building those version names for the conditions, etc. one time and saving them with Create Variable for reuse. That will reduce the risk of typos / errors from the repetition. Kind regards, Bill

The {{destinationIssue}} smart value is only available with the Work Item Linked or Work Item Link Deleted triggers: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Issue-linked If the trigger work item is the JPD one, you may change the expression to use the {{triggerIssue}} smart value:…

This other case is different, and reveals there are other scenarios to handle. (More on that in a moment...) Your original scenario was: GIVEN a parent work item with child work items WHEN field <X> or <Y> change in the parent THEN copy the field values to the children Your new one is: GIVEN a parent work item with fields…

Just to confirm, are you using Jira Cloud or Server / Data Center? I notice your Slack message uses the plural {{issues}} smart value, but that is only supported with Server / Data Center for bulk-handling. Your rule appears to only access one work item, so please change to the singular {{issue}} one. Some other things I…

Hi @Alexandra Nikitin -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log…

Hi @Gergana.Damyanova Without seeing the specifics of your entire rule... For each Send Web Request action, have you enabled the option to wait before the rule proceeds: Delay execution of subsequent rule actions until we've received a response for this web request If not, please enable that and re-test. Kind regards, Bill

Hi @Tom Removing the duplicates may be done using the distinct list function: https://confluence.atlassian.com/automation/jira-smart-values-lists-993924868.html#Jirasmartvalueslists-list.distinctlist.distinct Your current rule is triggered on a change to a Subtask, and so the lookup issues action should only return…

Hi @Ronny_matthies -- Welcome to the Atlassian Community! First, I recommend not using bot tools (even the built-in one from Atlassian) unless you carefully review and understand the rule logic. Such "guessers" cannot access the configuration of your specific products, site, work item types, etc., and so often provide…

Hi @Jo-Lee Bertrand Adding to the suggestions from @Trudy P Claspill When do you want that field to change as the rule shown might always edit the field? For example, do you want the parent set to the earliest Start Date for all of its child work items? Or perhaps the latest date? Doing this would require using the Lookup…

Hi @Sujatha Venigalla -- Welcome to the Atlassian Community! First, what problem are you trying to solve by typing text into a work item's Description field as if it is a bot / agent to process instructions? That is, "why do this", rather than just creating the work items? Next, your post seems to indicate you are using…

Another observation: the "branch at the same time" feature is only available for Premium and Enterprise levels, but the new rules list filter for "Advanced Components" shows up for all levels, including Free. Either this is another defect, or...are there other advanced component features to-be-released that will work for…

Thanks for the clarification, @Mireya Cintora on the issue types. And, I had a stray trailing comma in my example which is breaking the JSON. Please remove the final one after the customfield_12248 section. I updated my earlier post to reflect both of those changes. As a final observation: the Advanced Component feature…

Hi @Vrijesh Jeswant -- Welcome to the Atlassian Community! Yes, and...to the suggestions from @Trudy P Claspill There are two formats of the conditional expressions: {{#if(some smart value expression)}}return this when true{{/}} and {{if(some smart value expression, "return text when true", "return text when false")}}…

Hi @Quinn Campbell Without seeing the specifics of your rules / audit log details... By default, the actions of one rule will not trigger other rules. This prevents mistakes and runaway rule looping. When you intentionally want a rule to trigger based on the actions of other rules, in the downstream rule, enable this…

Hi @Pradeep For a specific "serial number" value, can you find the other issues using JQL? If so, you could create an automation rule triggered on Issue Created which then branches to the other issues with the JQL to add the links to the trigger issue. Kind regards, Bill

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks! Regarding examples from Jira Data Center (and from bot-generated suggestions), the automation features of Cloud, Server, and Data Center are different, with Cloud…

Hi @Omar Taha -- Welcome to the Atlassian Community! You are using a marketplace app added to Jira; I recommend contacting that app's vendor for support: https://marketplace.atlassian.com/apps/1219099/stagil-tables-todo-checklists-reports-data-sync-apis?hosting=datacenter&tab=support Kind regards, Bill

Hi @Satyajit Das -- Welcome to the Atlassian Community! Do you mean for a Jira Scrum board with Sprints? If so, please see the built-in Sprint Report. If not, please clarify your question to help the community offer suggestions. Kind regards, Bill

Hi @Simon Chan Thank you for the information about the new Enterprise and Premium license features. It appears the conditions on trigger feature is available for all license levels. For the feature to add conditions on triggers, will the racetrack timing problems be addressed? Specifically, there is a problem where the…

My apologies if I was unclear as it appears you my suggestions in the wrong places. Let's confirm what you are trying to accomplish. Which one is it? * add the person who triggered the rule (i.e., {{initiator}} ) to the custom field values * for a list of accountID values in a created variable, add all of them to the field…

Based upon that information, there may be something up with the field or the project configuration. As you appear to be on a paid Jira license, I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support to take a look behind the scenes: https://support.atlassian.com/contact/#/ When you hear back…

Hi @brian.kurzius -- Welcome to the Atlassian Community! The {{issue.fixVersions}} smart value is a list, and thus your condition could be comparing something like this to true: true, false, true, true In your condition, you could collapse all of the version states together with the distinct list function so only one value…

Thank you for that information, and... I recommend moving the condition testing the trigger work item is an Epic outside of the groups, as it is common to both. Then use this JSON expression, substituting in the custom field ID values for the two different fields: { "fields": { "customfield_12345" : { "value":…

Hi @Mireya Cintora For a cascading field, you set both the "parent" and "child" values at once with JSON: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Cascading-select-custom-field For example: { "fields": { "customfield_12345" : { "value": "parent_option1", "child": { "value" :…

I am not aware of any others. When I tried with two fields and "accidentally" selected the global one in the project, that description appeared with field (rather than the project-specific one). You appear to be on a paid Jira license, so I recommend asking your Jira Site Admin to submit a ticket to Atlassian Support to…

Let's start with your rule... The create variable action is saving the value from the field, which appears to be a multiple-selection user one. The way you are doing that, it uses the default attribute (i.e., accountId) and uses the default join with a comma followed by a space. But your split() only uses a comma (as does…

Hi @Ahmud Auleear Just a ping on the automation-related questions for this change: https://community.atlassian.com/forums/Jira-articles/We-re-removing-the-default-text-renderer-in-Jira/bc-p/3026348#M19069 Thanks!