Bill Sheboy Expert

Hi @Rafael Ibanhez For a question like this, context is important for the community to help. Please post an image of the complete rule and audit log details showing the rule execution. Until we see those... You appear to be using the Lookup Issues action (which returns zero-to-many issues) and setting the value into the…

Hi @Luisa Morcillo Rehberger -- Welcome to the Atlassian Community! Rules which access / update issues in other projects need to be multiple-project or global in scope. A single-project scoped rule can only create / clone issues in other projects; it cannot access them otherwise. Your Jira Site Admin will need to update…

Hi @Jade Dang -- Welcome to the Atlassian Community! First things first: if you actually have hundreds of tasks in this situation and want to cascade update them, that is not possible with an automation rule. The reason is such rules are often recursive, triggering themselves for cascading changes. There is a 10 loop limit…

Thanks for that information! Smart values, and their functions, are name, spacing, and case-sensitive. When an unknown one is used, it returns as null. Please try changing the case for the function call for the date increment…

Hi @Brittany Montgomery Context is important for automation rule questions. Please post the following to help the community understand that context and offer suggestions: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions…

Hi @Tina St_ Pierre -- Welcome to the Atlassian Community! You may not want to change the board's filter and ORDER BY clause to solve this as it would prevent things like drag-and-drop ranking of items on the board / backlog. Instead, your options depend upon what type of project you are using: * For a company-managed…

Lookup Issues can gather zero-to-many issues, matching the JQL provided. As your rule image shows, it is trying to set the Fix Version to the key values in the lookup result, which will not work. Please described what you are trying to accomplish, as your rule appears to have two purposes: #1) GIVEN an issue has linked…

HI @Raphaël NORYNBERG For a question like this, please include an image of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer better suggestions. Thanks! Until we see those... The Fix Versions field is a list of values, and so…

Yes, I would recommend that approach for your need: use a separate custom field for the total in the Epic, summed by the rule, and clear the "Story Points" field in the Epic. FYI to save you some investigation: the "simple" setting in delivery progress configuration would not help solve this, as it would only use the…

Hi @Fabrício Ferreira That is not possible with the built-in reports, and here is a very old suggestion to add that capability: https://jira.atlassian.com/browse/JSWCLOUD-5462 As workarounds, you could use JQL to create your own list of issues or investigate marketplace apps for the reporting. Kind regards, Bill

Hi @Carlos Lopez Perez -- Welcome to the Atlassian Community! You could use JQL to search for such issues, and then perhaps save that as a filter, subscribing for weekly updates. For example, this would provide issues updated or created since the start of the week: project = yourProjectName AND updated >= startOfWeek()…

Thank you for explaining the purpose of the rules. With rules like this, I suspect they will encounter one or more, of the automation service limits: https://confluence.atlassian.com/automation/automation-service-limits-993924705.html Synchronizing rules like this generally work okay with automation with just a few fields;…

Thanks, and... The automation audit log is not super helpful regarding conditions, particularly with such a complex rule. And the ability to nest if / else blocks is a very new feature, so perhaps this one is pushing it to the limits. By my count, there are 10 paths through it, and the log you show does not seem to match…

Hi @Pierre Ibrahim First thing, I am using Jira Cloud and not the Data Center version. And thus my suggestions are based on what I know about rules, in general. With that out of the way... I believe your rule structure and errors indicate what is happening: because the rule can be triggered repeated in a short window of…

Hi @Tuur Lievens (TME) -- Welcome to the Atlassian Community! Would you please post your complete rule in a single image, perhaps using a scrolling page capture? That will help see the overall context to help explain what is happening. Until we see that... Perhaps add some additional writes to the audit log to confirm the…

Hi @mohit jangid Please see this article from Atlassian describing an automation rule to do that. For your case, update the JQL used in the Lookup Issues action to meet your needs: https://confluence.atlassian.com/jirakb/automation-to-send-email-only-once-per-assignee-1310985609.html Kind regards, Bill

And also... I just noticed your other question about automating the move of issues from the backlog to the board. That is possible using a Jira Automation rule with the rule action "Move Issue to Board".

Hi @Geoffrey Hicks -- Welcome to the Atlassian Community! You are correct: configuration of the backlog differs for company-managed and team-managed projects. For team-managed, the backlog is enabled as a "feature", and whether or not an issue appears on the board is managed from the backlog view. Please look here to learn…

Hi @Petru Simion _Simitech Ltd__ You have necro-posted similar content to recommend your marketplace product more than a dozen times today, which does not adhere to the community guidelines. Some of your posts are to threads over a decade old. *…

Hi @Dave Coop I have also observed odd behavior with the counts by story point in that "delivery progress" calculation. Some things to check for your case are: * Have any of the issues been added twice (e.g., the Epic and a child of the Epic) in the linked delivery progress issues? Unfortunately, it does not remove issue…

Hi @Yuliia_Borivets__SaaSJet_ Thanks for the summary of methods to track the date-of-change for fields, beyond what is provided by the built-in, JQL supported checks. And, please consider there could be exceptions for all of these methods, as some field changes do not trigger the issue-updated event and / or do not write…

Repeating my earlier hypothesis, does your Scheduled Trigger have a JQL expression? If not, that is the cause of the error.

You are getting closer, although there is no need to iterate over the issues with a branch to find / compare dates. That is where the Lookup Issues action helps. Let's start with some JQL to find the issues needed. Assuming your Idea has a key of JPD1-20 and the linked Epic has a key of SP1-30 -- get Idea from implements…

Hi @ToM For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions / branches, * an image of the audit log details…

I recommend starting with the JQL: find an example Idea which has linked issues, and write JQL to find them. That may be used later in the Lookup Issues action. And try this in steps: first find the issues only linked directly to the Idea. Eventually you can try to expand that to the next level of linking...but please…

When you add the Lookup Issues action to your rule, you will see the location to enter the JQL.

Thanks for that information. To use the {{lookupIssues}} smart value, your rule must first call that action, using JQL. An outline for your rule could be: * trigger: issue transitioned * condition: issue type equals Epic * action: lookup issues, with JQL to get the child issues for the epic* parent = {{triggerIssue.key}} *…

Hi @Steve White -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have a rule that is not working as expected, please post: * an image of the complete rule, and * an image of the audit log details showing the rule execution. Those will provide context for the community to offer…

Hi @Santiago Almeida -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have a rule that is not working as expected, please post: * what version of Jira you are using (i.e., Cloud, Server, or Data Center), * an image of the complete rule, and * an image of the audit log details…

Hi @Nick Haller Your created variable has a name of jiraDate, which is also the name of a function for date formatting in automation rules. To avoid people and rules having confusion, I recommend always prefixing names in Create Variable, Create Lookup Table, and Advanced Branches with some indicator text. For example,…