Bill Sheboy Expert

Hi @Tiemen Blankert First thing, when I test rules like this I use a Scheduled Trigger (with or without JQL) and Created Variables to supply data, only writing results to the audit log rather than making work item changes. This ensures there are no side-effects and often has no "cost" for monthly usage limits. When the…

Hi @Rees, Ian The smart value you are accessing is a list of comments, and the single comment from the trigger may not work consistently due to value confusion inside of the branch. Thus, each subsequent rule execution to the parent will potentially collide with earlier comments. Please use this value to add the new…

Hi @Neeta Dubey Although it is possible to use list iteration and filtering to perform the value mapping and summation you describe in an automation rule, why not just use time-based estimation rather than Story Points? That will save time, confusion, and reduce the chance of errors in moving back-and-forth between the…

Hi @Hari Krishna What is the source for the information in your initial post, as that would not work in an Atlassian Automation rule? https://community.atlassian.com/forums/Jira-questions/Automation-rule-sum-of-original-estimate-in-subtask-to-be-copied/qaa-p/3164084#M1161917 As a reminder, when posting bot / AI-generated…

Thanks for the images, @Jenny Alexandra Canastero Romero Rather than setting the field with a smart value, please try changing the Edit Work Item action using the ... option at the right of the field, and selecting Copy from the Parent.

Hi @Jenny Alexandra Canastero Romero For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any relevant actions /…

Hi @Darryl Lee !! Thanks for your feedback, and...as you may have read in my posts before: I do not believe in best practices, only better or worse ones for a specific team, context, and point in time. That noted, I clearly missed describing "better" testing practices used incrementally for many of the ideas, while others…

Hi @Pauline Heng Thanks for this information, and... You described this: "Team types are designed to ensure that, as we introduce more settings, permissions, and controls in the future, each team will have the right configuration." What can you share about how types will impact team selection in features such as Jira…

That would likely work, although I would use the organization's ID to ensure the JQL works as expected. And...I was recommending to include more information when asking future automation questions. Did I misunderstand as I thought you had already solved this based on your earlier posts?

Hi @Marvin Brand First thing: what problem are you trying to solve? That is, "why put a list of links into that field?" Knowing the "why" may help the community offer better suggestions. Until we know that... The work item linked trigger only fires in the direction of the links (as configured in admin features) regardless…

Hi @Simon Huprich What problem are you trying to solve by adding the delay of 4 seconds? Knowing that may help the community offer better suggestions. Until we know that... You could use the Send Web Request action to call a public REST API endpoint to provide the delay. Remember to select the option in the action to wait…

Hi @Mark Taylor I do not believe there is a public REST API for the Atlas features yet, and so it is not in automation rule actions either. Here is an open suggestion to add support for goals to automation rules: https://jira.atlassian.com/browse/AUTO-1683 Kind regards, Bill

Hi @Eric Silva When a rule branches over more than one thing, it processes in parallel and asynchronously, with no guarantee when the branch will complete, up until the last step of the rule. This means anything which happens inside the branch cannot be accessed afterwards, such as an accumulated, created variable. And, if…

Hi @Hermance NDounga Thanks for the information! Does the migrate feature handle moving a JPD date-format field to a global date-picker one yet, or does that still require intervention such as using an automation rule? Thanks! Kind regards, Bill

Hi @Mélanie Liguet Depending upon how many work items are returned by that endpoint: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-limit-report-get And without actually trying this, I wonder if one could: * call the limit-reporting endpoint in a rule * using list…

Hi @Sarah Cheyne -- Welcome to the Atlassian Community! Yes, and...to the solution you already have worked out with Trudy: a couple of things to consider: a) With so many "done" status values, you may want to use a single lookup and check the statusCategory instead using list-filtering. That will ensure if the status…

Hi @Trudy P Claspill Yes, and...I agree with the idea of using a Scheduled trigger rule later (or using a Delay, Re-fetch, and checking again in the same rule), and... My testing found the satisfaction rating and response date changes will trigger an issue-updated event, but the comment does not appear to trigger any…

Hi @Ryan Hormann I believe that approach is more complicated than we were suggesting...and may be a bit brittle for cases when rules do not rule when expected (e.g., during an Atlassian incident or outage) or when a person intentionally or accidentally tampers with the custom field values. Did you check if you have any…

Hi @Tiemen Blankert I am uncertain what could cause that symptom...other than it is cloud storage and updates may need to propagate through the work items. Have you checked if other automation rules or marketplace apps are making changes to the work items? You can do that by find some example work items with the symptoms…

Without JQL in the trigger, it is unclear to me why that would have produced the duplicate results...unless the nested list processing was the problem (i.e., lookup results and Organizations field). This is an example why posting a complete rule, the action details, and the audit log details help provide context for the…

Thanks for that information, @Jeremy Wood I just re-tested without advanced components, and with an IF / ELSE block, I would expect the variables to work later...after setting them in an earlier block. Would you please post an image where the GroupName variable is created? And, you do not also have a work item field by…

As a temporary workaround to remove some outliers...If you can write a JQL expression to exclude the work items which are missing data, try saving that filter and using it with the Average Age Chart to observe what happens. For example, using the JQL CHANGED operator, one could ignore "Done" work items which never went…

Hi @Ron Sethman -- Welcome to the Atlassian Community! The built-in dashboard gadgets such as the Average Age Chart have very limited configuration options. You may want to ask your Jira Product Admin if you have any marketplace apps / addons which have better reporting to meet your specific scenario, such as removing…

Does the scheduled trigger have JQL? If so, that is the cause of the repeated items.

Without seeing your entire rule, I wonder if the cause is the rule trigger has multiple work items (e.g., scheduled with JQL) and thus the duplication is from the trigger iteration and not the branching over distinct items.

Greetings, community! Is anyone else seeing these symptoms in the last couple of days worsening? * The notification feed (under the bell at the top right) often errors / shows as empty, and the feed does not show results until hours later * When one starts typing a post, and submits, its is timing out due to a page expire…

Well done, and quite curious! When I did an advanced branch over the flattened and distinct Organizations, I was able to get the id directly. I wonder what is difference for our usages. * ... * advanced branch* variable name: varOneOrg * smart value: {{lookupIssues.Organizations.flatten.distinct}}* inside the branch,…

Hi @Ryan Hormann Thanks for clarifying, and one challenge still seems to be the business days check. Without that, a simple query would be this, using the CHANGED operator, for example checking for 5-days-stalled items: project = myProject AND status = "Waiting for User" AND NOT status CHANGED AFTER -5d AND updated < -5d…

Thanks for that update, @Thomas Brennan -- This is good information! I recall related and unexpected limit exceeded errors two times in the past: when JPD went live from free-to-paid product and when the packaging model for automation changed (i.e., the global-rule and limit changes). But neither of those showed as ABORTED…

Thanks for the additional information, @Jimmy Trivedi and welcome to the community! As a follow-up question: your scenario tests the Due Date, and then you seem to be editing it later. What is the purpose of changing the Due Date in such cases? As you have JQL which works for the scenarios, and you want to check when a…