Bill Sheboy Expert

Hi @Sanjay Dangi -- 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…

An automation rule could run on a schedule, creating issues with fields set in the future, such as setting the Due Date several months in advance.

Ah...there is no Lookup Issues action, and so there will be no data for that second write to the audit log. Please try this for that rule: * trigger: scheduled, with no JQL * action: lookup issues, with the JQL just removed from the trigger * action: log your total sum Sum:…

Here is another good one in that area: after the packaging changes for automation, they modified what counts toward monthly usage. https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update

Hi @Amanda Caton As this is an older thread, it is often better to create a new question and link back to the older ones. That will ensure more people see it and offer suggestions; otherwise only those following the older threads (or who are mentioned) will see it. Back to your questions... Yes, I have seen…

Hmmm...some additional things to check: If you write the {{initiator.accountId}} value to the audit log, does it contain the value you expect? Who is set as the actor for this rule? I found this defect in the public backlog, which seems to indicate some Confluence automation triggers do not detect the initiator correctly.…

With that additional information, perhaps ScriptRunner will be better. Automation rules can process up to 150 issues / things in a branch (or 50 objects for assets), and so an advanced branch could not span 200 components: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

Understood, and so that expression does need the math expression to support the division. When I asked for an image of the complete rule, I wanted to see all of the rule steps in one image. That will show the order of actions relative to where those writes to the log are happening.

There are several ways to do that check, and two of them are: {{#lookupIssues}}{{#if(components.name.size.eq(0))}}{{key}}; {{/}}{{/}} or {{#lookupIssues}}{{#if(components.name.isEmpty())}}{{key}}; {{/}}{{/}}

Hi @Ashok Bala -- Welcome to the Atlassian Community! That does not appear to be a built-in or user-added custom field. Is that field from a marketplace addon? If so, please contact the vendor's support for the product to learn how to access the field. Until you hear back from the vendor... Sometimes custom fields from…

Hi @El H -- 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 context for…

Hi @Suzanne Beauchamp The drag-and-drop feature to change issue ranking only works when the board's filter is sorted by Rank. That is, it ends with only this: ORDER BY Rank ASC Any other ordering disables ranking. Please check your board filter to learn the issue ordering. Kind regards, Bill

Context is important for automation rules. Please post an image of the complete rule which contains those writes to the audit log. Those last two entries you show cannot be inside of the lookup issues iterator because they span the entire lookup. If they are, I would expect them to return nothing. Also, for this one: Sum:…

Hi @Bent Möller -- Welcome to the Atlassian Community! Branches in automation rules can iterate over issues or arbitrary things with an advanced branch (e.g., some list of text values). However they cannot iterate over the set of Components defined in a project as there is nothing built-in to get them. So, some…

Awesome; I am glad to learn that helped! I have learned many things about automation rules by experimentation and reading posts in the community. I recommend watching the automation product area for new articles and discussions: https://community.atlassian.com/t5/Atlassian-Automation/ct-p/automation That is where details…

Hi @Max_Clark Smart values for fields are name, spacing, and case-sensitive, and they sometimes do not match the displayed name on the issue views. When an incorrect smart value is used, it collapses to null, and often fails silently with no rule errors. I recommend confirming you have the correct smart values for your…

Thanks for clarifying, and one final question: Are all of these issues in one project, or is the project "Strategic Initiatives" a separate one from where the target issues for this rule exist? That is important because if the projects are separate, the rule scope will need to be multiple-project (or global) and your Jira…

Hi padmalatha79@gmail.com 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 context for the community…

As John notes, the branching may be the cause of what you are observing: Branches which could be on more than one thing run in parallel and asynchronously; there is no guarantee of when the branch will finish, up until the last step of the rule. For the rule you show, this means all of the branch could be running at the…

First thing, some tips when creating / testing automation rules: * Try only writing to the audit log and not updating issues, sending emails, etc. Writing to the log will not count toward usage. Once your rule behaves as expected, modify it to make edits, send messages, etc. * Review the automation limits and packaging…

Update...this one was bugging me, so I kept looking at it to find an approach that works for Jira Cloud. If it works for Data Center, awesome...although I expect the regular expression may need tuning. Let's assume we have the maximum version date in a created variable, named varMaxReleaseDate. We then create a dynamic,…

Short answer: I am stumped on this one, and I recommend working with your site admin to ping Atlassian Support to learn what they suggest, at this link https://support.atlassian.com/contact/#/ More information... As I noted earlier, I am using Jira Cloud, and so there are likely differences with the behaviors you see in…

I am confused as what that rule is trying to do. For example, that created variable will produce a text string that looks like below, and then try to link that to another issue: SEP, SEP, SEP = "Strategic Initiatives" Would you please explain / confirm what problem this rule is trying to solve? It seems what you initially…

Your lookup has no results and that is why there is no value and the expression leads to an error. A work-around would be to add a default value of 0: {{#=}}ROUND(0{{aggregatetimespent}} / 3600, 2){{/}} But I am puzzled: what is the structure of your expression that it iterated over the lookup when there were no issues?…

Hi @Lindsay Sullivan In my experience...Components are one of those smart values which behave like a list and an array in rules, depending upon the context. To do what you ask, please try this: {{#lookupIssues}}{{#if(components.name.match("(blue comp)").size.gt(0))}}{{key}}; {{/}}{{/}} How this works: * Iterate over the…

Thanks for the write-up and tips, @Rachel Wright Another one to check for this scenario is automation rules, by exporting the full rule set as JSON and searching for references to those fields (both as smart values and custom field ids). Unfortunately, rules do not always fail when a field is missing; instead the unknown…

Hello, community! As noted in the other answers for this question, summing custom fields with Jira Cloud may use the Lookup Issues action: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues However for Jira Server and Data Center, the initial version of Lookup Issues does not support…

Yes, and... Going too far the other direction could be problematic as well. When one needs to find the company's official "Keyword, Acronym, and Acrostic Generator v3.4.1" to know what a project is about, that seems like a smell of other root causes.

Hello @JD.Lobue Yes, and...to this suggestion: If you use, or have ever used in the past, any team-managed projects in your Jira site: the status changed operators for JQL may not work as expected. Here is the defect for that symptom: https://jira.atlassian.com/browse/JRACLOUD-78387 The work-around is to use the id values…

Hi @Brandon Leong -- Welcome to the Atlassian Community! Based upon what you are showing, I can think of two ways to do this: Better way for rule performance: use one call to Lookup Issues to gather all the relevant issues, and use smart value, list filtering and math functions to report what is…