Bill Sheboy Expert

Hi, @Eran Roiter Sorry for the delay in responding as I have been offline for a few weeks. Did you see my earlier questions about what is a "Father issue"? How well does what I described match your scenario? And...please note well that links are directional, and so your related issues condition could have problems. That…

Hi @Marco Calluso For the multiple-selection field symptom you describe, the fix is to not use branching (as that runs in parallel and will walk-over prior results). Instead use a single issue edit with using JSON to add the values with advanced…

Hi @LENA BURLAK -- Welcome to the Atlassian Community! Your rule will need some changes to work with a user list... First, I do not believe Jira Cloud automation rules can use the user's display name to assign issues. Instead the account id value must be used. There are several ways to solve this: * Include the account id…

Hi @Tom Rouillard FYI those old Greenhopper APIs are likely deprecated and unsupported. Please consider other solution approaches to avoid surprises. Kind regards, Bill

Hi @Jonas Kopka -- Welcome to the Atlassian Community! The Jira version (Cloud, Server, or Data Center) of automation, the field type, and the project type can impact when the value attribute is needed in rule math operations. For example, it appears some of the JPD fields may use the value as the default attribute rather…

Hi @Gary J That may be done using the Lookup Issues action with JQL, as described in my post above. Kind regards, Bill

Hi @Chaya Created Variables are text but the function plusDays() is expecting a number parameter. Please convert that using asNumber. Assuming your variable is named "days" that would parameter would be: days.asNumber By the way...I recommend using a naming convention with variablesto avoid the possibility of collision…

You seem to want to calculate the Lead Time (from created to completed) or some form of cycle time (such as Build Cycle Time, from start of work to completed). As already described, the built-in JQL cannot calculate the difference and cannot exclude the weekend days (for more than a single specific week). You would need…

Thanks, Michael. From my observations... That symptom / defect allowing drag-and-drop for branches (and some condition types) appeared intermittently for a couple of years with Jira Cloud automation rules. As it apparently was not designed to do that, the resulting behavior seemed a bit random. I did note when such a rule…

Hi @Esau Espinoza -- Welcome to the Atlassian Community! Custom fields of People type are implemented as multiple-select, even when the single-user option was selected. This applies to all team-managed, or other project types, using People type fields. The solution is to use the array format for the JSON, as the error…

Rene, the filter issue, dashboard gadget can show the Resolution field. Do you mean the saved filter used by the gadget only includes "Fixed" Resolution issues in the JQL? Regarding which Resolution values to show, several of the suggestions / defects I have created were: * bundled with others, * closed without a solution…

Hi @Chris S_ For Jira Data Center, there is no branch that spans both types as there are different linkages for epic -> story and story -> sub-task. You may address this using an if / else condition and branches inside. For example: * trigger: issue transitioned to Complete * if / else condition:* field condition: issue…

Thanks, Trudy! The definition of the duration variable and increment of the date seem comingled / different from your linked solution. If they are separated again it should work, with the key being how much to increment: * by the same amount as the trigger issue's due date change, or * some other amount.

Hi @Jessel Bentley In my opinion, this depends upon what you want to measure and influence... This symptom is an anti-pattern, sometimes called "design by defect", where stakeholders try to get elevated priority by submitting an enhancement request as a defect. It could also be an education issue where a product's…

Hi @Joe Mraz -- Welcome to the Atlassian Community! In your rule's create variable action for "duration" you use this smart value expression: {{issue.dueDate.plusBusinessDays(diff))}} That is not valid as "diff" has no meaning / value there. Were you trying to use the change in value for the Due Date of the trigger issue?…

Hi @Val Gendleman Without seeing the specifics of your rule...you could check if the date is on a weekend using the format() function, and if so make an adjustment using the toBusinessDayBackwards function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format---…

Hi @Mike Bronner -- Welcome to the Atlassian Community! I do not believe that trigger supplies the headers and here are the suggestions to add that capability: https://jira.atlassian.com/browse/AUTO-928 https://jira.atlassian.com/browse/JIRAAUTOSERVER-997 You may want to check in the developer community for this…

Hi @Leyla Kinaze First thing, I recommend confirming that is the correct smart value for the Target Start field, either by writing it to the audit log or using this how-to article: https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html Next, is the "new sprint" start date always…

Hi @Brad Hebert -- Welcome to the Atlassian Community! There are two possible causes for this symptom... First, the Issue Created trigger can fire so quickly that some data is not yet available to the rule. As linking happens after issue creation, it is likely the data is missing when that condition is attempted by the…

Hi @Rene C. [Atlassian Support] I suggest adding the Resolution field to the relevant gadgets to help to see final disposition. Thanks! Kind regards, Bill

Short answer: no, JQL is needed. The scenario you are trying to solve seems to be this: GIVEN there is an epic named "Out of Office" AND that epic has child features with Due Date values WHEN such a feature's Due Date is before 9 am today (i.e., it is late) AND the feature is not already completed or in "Test Complete"…

Hi @Laura Cagüe -- 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…

Hi @Shikha Verma Please stop posting content from bot / generated tools. This answer cannot work as once inside of a branch, issues outside of the branch cannot be updated. Kind regards, Bill

Hi @Vipin Kumar -- Welcome to the Atlassian Community! The built-in JQL features do not support excluding weekends with the date / time functions and features: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/ Please describe the problem you are trying to solve and what you mean by "TAT". Knowing that…

Hi @Spasimira Genova There is an open defect for this symptom happening intermittently. You may vote for / watch it to see any progress: https://jira.atlassian.com/browse/JRACLOUD-81380 Reading through the comments on that defect, you can see the behavior and specific fields not cleared is inconsistent. Kind regards, Bill

Hi @Chris M_ -- Welcome to the Atlassian Community! I note two things for your scenario to help adjust your rule... 1) When you want to link issues in a rule, you need the key to one issue and the other needs to be "in scope" at a point in the rule. And so you could either branch to one issue and the link to the trigger…

Hi @Ramesh S Yes, and...to the suggestions from Marc: While there are changelog fields available to rules when a field-change trigger is used, this will not work correctly for the Sprint field. There are known defects where list fields such as Sprint and Fix Version do not accurately provide the changes to rules, and so…

Hi @Martin Janeček -- Welcome to the Atlassian Community! As others have described, you could use saved filter subscriptions to do this...if you can get your users to subscribe to the filter :^) If you still want to use an automation rule... Your rule is gathering the issues, but not accessing them correctly in the lookup…

Hi @Michael Melton -- Welcome to the Atlassian Community! I am curious about something your rule image appears to show... It shows one branch inside of another, or nested branching. I do not believe that is a feature of Atlassian Automation rules yet. Here is one of the suggestions to add that…

Hi @Rachel Stein -- Welcome to the Atlassian Community! It appears the JQL in your branch is incorrect. Should the field name be enclosed in quotation marks, or instead you could use the epic key, as Sam described. (I suspect you will need the key or to alter your rule to find the epic first, by name, and then use the key…