Bill Sheboy Expert

Hi @Kuma -- Welcome to the Atlassian Community! As you are on a paid Jira license, I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support to take a look: https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn to benefit the community. In the interim,…

Hi @Idriss -- Welcome to the Atlassian Community! When did the symptoms appear? There has been a related, active incident since early today. Perhaps check if that is the cause: Issues with data pipelines for customers using GitHub for Jira Connector. https://jira-software.status.atlassian.com/incidents/p72dgjs4w0rh…

Hi @Tiia Ojanaho -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * an image of the rule details at the top of the rule * images of any relevant actions /…

Hi @David Spohr -- Welcome to the Atlassian Community! 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…

Hi @Tyler Cassar For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution * explain…

Hi @kaavya.ramaswamy -- Welcome to the Atlassian Community! You have the correct rule trigger as you likely want this to happen as soon as the last work item transitions to done: GIVEN a version has one or more assigned work items AND all but one work item are Done WHEN the last work item transitions to Done THEN release…

Hi @Mitesh Shah Without first seeing the rule's audit log details, I see two things to correct in your rule: (1) The Issue Created trigger can start a rule so quickly that some data may not be ready for the rule to use. To fix this, please add the Re-fetch Issue action immediately after the trigger. This will slow the rule…

Hi @Captain Kirby -- Welcome to the Atlassian Community! There is an open defect for this symptom, which you may vote for / watch to see progress: https://jira.atlassian.com/browse/JRACLOUD-93602 There is a workaround noted, but it requires calling the REST API endpoint. That could be done with a standalone API tool, a…

Hi @Angel The data from the webhookData is likely text, and must be converted with toDate before using with date / time functions: https://support.atlassian.com/cloud-automation/docs/examples-of-using-smart-values-with-dates/#Converting-text-to-dates And after conversion, I suggest using the built-in conversion functions…

FYI for a workaround when preserving the data typing is desired (for Jira Cloud rules)... Rather than using Create Variable, use Create Lookup Table as the team got it to preserve the typing and structure of the source. For example, this is helpful in situations where one wants things like multiple Lookup Issues results: *…

Hi @Nathan Charles Unsworth I reproduced that symptom for inactive pages which have no parent page / content, and... * When a Jira automation rule encounters a smart value with no value (or which does not exist), it replaces the value with null, often showing no errors (unless the logic depends upon it). * But when…

Hi @Richard_Crowley Are you a project admin? You will need that permission level (or higher) to create rules.

First thing: I recommend not using any bot / AI tool to answer automation questions...even the built-in one from Atlassian. The reason is each Jira Site has different configuration settings (e.g., Jira version, installed apps, installed products, projects, custom fields, work item types, workflows, etc.) and the bot cannot…

Thanks for that additional information! First, I note your JQL condition is using single-rather than double-quotes. I recommend changing those to avoid problems; I believe JQL is documented only supporting double-quotes. Next, if I understand your scenario correctly, the "attributes" each contain: * a "name" which is a…

Hi @Stefan Froehlich Without seeing the specifics of your rule and audit log details... First, into which project are you creating the new issue: the same as the trigger issue's form or a different project? If you are creating it a different project, the rule will need at least multiple-project scope to add the link after…

Hi @Jack Brickey Created variables are text (regardless of the source type). And so when the condition comparisons are done on text, that uses alphanumeric comparison. If you want to compare them as dates, first use toDate to convert them, and then use appropriate date / time functions or conditions: *…

Hi @Dilip What is the source of your information regarding rule triggers as they do count toward the 65 component limit? A rule's trigger is a type of component, and so it also counts. You may create a test rule to verify this information. Kind regards, Bill

Hi @Sudhanshu Agnihotri -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an…

Hi @wojtek_pawlak First, when you note "the automation stopped working", what did you observe in the audit log for those cases? Yes, and...I agree with @Tomislav Tobijas that for "weird symptom" automation errors, try disabling the rule and re-creating it from scratch. I recall there are some open defects related to value…

Hi @Rosalind Barker -- Welcome to the Atlassian Community! Short answer: the "trick" is to store your regular expression in a variable and then use that variable in the match() call. For more information... There can be timing and evaluation order problems with the match function, leading it to parse incorrectly. And so…

Hi @joe bednarz For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single…

Hi @Nathan Charles Unsworth I recall a similar question last week (or the one before), and experimentation showed... * the Confluence automation branching did not permit selecting the most recently created page, * branch on CQL to the new page does not work for a just-created page, and * the Publish New Page action only…

Hi @Dan Knapton As this is a very old thread, please create a new question to ensure the maximum number of people see it to offer suggestions. Thanks! Until we see your new question...some of the changelog and fieldChange smart values available inside of rules are plain text while others are structured objects. Kind…

Hi @Brock Jolet Short answer: yes, you are correct they count. Here are some related suggestions to follow: https://jira.atlassian.com/browse/AUTO-1706 https://jira.atlassian.com/browse/AUTO-1778 Just like a branch counts as one-for-count, the if / else block structure counts as one plus one for each condition... but their…

Hi @Cláudia Silva As the pull request smart values are only available with the PR-related triggers, I believe you will need to do this in three (or more) rules: * with the Pull Request created trigger, save the created date in a custom field which can later be searched with JQL * with the Scheduled trigger with JQL, find…

Hi @Rachel Alexander -- Welcome to the Atlassian Community! For automation rule questions, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit…

The values for your Lookup Table are incorrect: they cannot dynamically lookup work items (formerly called "issues") for a user when the table is created. Instead... To get the work items assigned to the person who triggered the rule, first use the Lookup Issues action with JQL. For example: * trigger: value changes for…

Hi @srikanth_rao How are you "linking" the work items? If you are using the built-in parent / child relationships with the Parent field, please use that instead for the trigger: * trigger: Field Value Changed, selecting Parent, possibly selecting "value added" for the change type * condition to check the Parent value *…

Hi @Stephanie Donnelly Have you compared your products, license level, and user count to determine if a specific product's rules are the cause? For more information, please look here: https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits Kind regards, Bill

Hi @Hari Babu What have you tried thus far to meet this need? If you have an automation rule which is not working as expected, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this:…