Bill Sheboy Expert

Based on the rule you are showing, the JQL is checking "Parent Link" when I believe you want to use "parent" instead. I believe the "Parent Link" field is used with advanced roadmaps when the hierarchy has been…

Hi @Alex Suterlowe -- 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…

Nope, that is still unclear to me. One key thing: if you want to add the comment to the trigger issue that action cannot be inside one of the branches on other issues. What is the purpose of the comment added to the trigger issue (i.e., Story-A)? Is it an indicator that "everything is done for this rule" or something else?

Hi @Ben Ikin First thing, I believe you will still need 2 rules. As you noted, those DevOps triggers for rules often fire for each issue and so the rules cannot be combined. Next, your first rule has access to the {{deployment}} smart value but the second rule does…

Hi @Laura Hanna You want to update the trigger issue with some information from the most-recently created issue, correct? If that is the case, you may remove the branch to the most recently created issue. That will change the scope for what is the "current issue" back to the trigger for your Add Comment action. If you need…

Hi @Aline Veyradier and @Mikael Sandberg The status page appears to be working again now, and no longer redirecting to the statuspage product. https://status.atlassian.com/ Kind regards, Bill

Hi @Brinda Tailor I do not believe that is possible with the out-of-the-box features of JQL. You may find the startOfMonth() or the startOfWeek() and add some days, but there is no function for the "first Tuesday of a Month" with JQL. https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#startOfMonth-- As…

Hi @Shruti Shrivastava Do you mean the Created Variable action in rules? If so, created variables are text type. To use them in a math expression which uses a condition like that they must be converted with asNumber. For example for your case: {{#if(Variable.asNumber.gte(80))}} do something {{/}} FYI: if you were only…

Thanks for that information, David. And thanks for clarifying about the individual measurement part, so I will not comment on that: as the saying goes, "not my circus; not my monkeys" :^) Gathering the list of distinct assignees is the easy part: {{#lookupIssues.assignee.distinct}} * {{displayName}} {{/}} The other part…

Hi @David Alexander -- Welcome to the Atlassian Community! What you are trying seems possible, but I am not quite following the scenario, so some follow-up questions are: * What problem are you trying to solve? * What is the purpose of that story point comparison? * What would the completed layout of your email look like?…

Hi @Balaji K M -- Welcome to the Atlassian Community! Would you please confirm your meaning of "Resolution time (TAT)"? A couple of process flow measures which may be related are: * Lead Time: duration from request creation until completion. This is measured in calendar time. * Cycle Time: duration from two specific points…

Hi @Estelle Decanis The "Validate query" feature is only enabled if the JQL can be determined in the rule builder. Your JQL is based on a smart value, and so cannot be validated until runtime. I suggest trying the JQL stand-alone (in View All Issues) with a known value for the field, confirm it works, and proceed from…

Hi @Loann RAZZANO -- Welcome to the Atlassian Community! Two suggestions to help are: (1) Successfully using automation rules requires learning and experimentation. I recommend trying to create a rule, and if you run into challenges, to post images of your rule, the audit log details, and explain what is not working as you…

Hi @Estelle Decanis For older threads like this, I recommend creating a new question and linking back to the older one. Otherwise only the people following it will see your question to offer suggestions. Thanks! Would you please post an image of your complete automation rule, the details of the condition with your JQL, and…

Hi @Ismail Sanni Automation rules do not support all fields. Worse still, there are multiple things in Jira called "Team". Smart values are name, spacing, and case-sensitive. And often the smart value does not match the displayed field name on the issue views. The how-to article below helps to identify the correct smart…

Thanks for confirming your Jira version. I do not believe this would be possible with an automation rule as it would require nested branching. Please investigate the other options I suggested: marketplace addon or build-your-own app.

Hi @Ihsen Ben Maatoug The smart value for that field is {{issue.fixVersions}} (please note it is plural): https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.fixVersions-- Next, that is the incorrect syntax for the substring…

Hi @Illya Konstantinov -- Welcome to the Atlassian Community! This appears to be another of the changes with the "enhanced board" views. Here is a suggestion to put it back to display the limits whenever they are set. The work-around seems to indicate this is a screen resolution-related behavior. You may vote for / watch…

Hi @Bhagyalekshmi S Please look here to learn about the program: https://community.atlassian.com/t5/Community-Kudos-Feedback/Welcome-to-the-Atlassian-Community-Kudos-program/ba-p/2148250 Kind regards, Bill

Hi @Oded Tali Have you tried using the Two-Dimensional Filter Gadget, with the Epic Link selected as the y-axis and the Issue Type selected as the x-axis? That should work if your selected filter only includes the Bug issue type and those have the Epic Link field filled in. Kind regards, Bill

Hi @Matt Johnson There is an automation rule Move To action for doing that, implemented just a couple of weeks ago: https://jira.atlassian.com/browse/AUTO-605 I just tried it with a team-managed project and it worked. Kind regards, Bill

Hi @Sam Gerzon The out-of-the-box JQL does not support regular expressions. It only has limited wildcard handling and a "fuzzy" match supported by the CONTAINS ~ operator: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CONTAINS---- If you need this type of query often, consider investigating…

Would you please post some images to provide context: * one image of the entire rule, * one image showing the rule action containing that smart value expression, and * one image showing the audit log details with the rule execution. Next, when using smart values a default value can be added when a field is empty, or null,…

Hi, @Anastasiia Tsvetkova I am looking back over your rule, and the information in the JQL Condition does not look valid. It seems to only have a reference to {{lookupIssues.first.fixVersion.releaseDate}} and that by itself is not valid JQL. What was that JQL meant to test? Thanks!

Well done, diagnosing the issue! I should have confirmed the custom field type earlier. As a future tip: smart values are name, spacing, and case-sensitive. And the type impacts the specifics of how to use them in rules. This how-to article can help identify the correct smart values for a field:…

Hi @Shruti Shrivastava That error is showing one or more of the story points are empty (or null). Smart values are name, spacing, and case-sensitive. When an unknown one is used, that evaluates to null and often fails silently. I believe the smart value for the field is "Story points" and not "story points". Please change…

Hi @Benedict Lubik 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 to offer ideas.…

Hi @Poephouder -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? That is, why do this? And, what practices does your team normally use to manage work items? Knowing these things may help the community to offer better suggestions. For example... If we assume there is a symptom of…

Hi @G You do not show the table lookup for your advanced branch variable, and I suspect it looks like this: {{OrganizationWeight.get(Organization)}} That will try to use the id value from the custom field, and not the value. To use the value, try changing your advanced branch smart value to use this:…

I do not believe there is another way to get the board information from an automation rule. As already stated, there are no smart values for boards. Why would the REST API functions not work, as they can easily be called from an automation rule? Next, let's pause for a moment: what problem are you trying to solve? That is,…