Bill Sheboy Expert

Hi @Courtney Burton -- Welcome to the Atlassian Community! Short answer: that feature no longer works in the Send Slack Message action. Atlassian has not yet updated the rule editor UX or documentation to reflect this. After the Slack REST API changed, automation rules (and other tools) could no longer send direct messages…

Looks like the JQL function worked for you, but to close the loop... You wouldn't need the sprint names, only the board name to find the sprints...and then filter from there. The REST API approach helps when there are no issues assigned to the future sprints yet, AND one still needs the filter updated to specifically…

Hi @Shashank Garg -- Welcome to the Atlassian Community! There is no built-in rule action to do that. Perhaps check if Google has a REST API endpoint to support updating an existing document that could be called using the Send Web Request action. Kind regards, Bill

Hi @Bud Herz Yes, and...to the suggestions from @Trudy P Claspill When you want to include all future sprints, the JQL function Trudy notes will help. When you want a subset of them based on specific criteria, you could use an automation rule to dynamically update the saved filter used by the dashboard, calling the REST…

Hi @Andy Chlup First thing, I am just another Jira customer and have no internal knowledge of the automation engine's implementation. My suggestions are based on my experience and observations using rules. With that out the way... Some data in rules is usually available when the rule starts (e.g., fields in a trigger…

Hi @Allie Deleon -- Welcome to the Atlassian Community! Short answer: the page history does not include information about moves and so this may not be possible. After a quick test, it does not appear that page moves are recorded in the version history available to the REST API endpoint...and so not to rules as a changelog…

My mistake as I forgot this was a multiple-select option field, and so JSON must be used with advanced edit. Please try this, as noted in my first response but now using the lookup results: { "fields": { "customfield_10177": {{lookupIssues.first.customfield_10177.asJsonObjectArray("value")}} } }

Ah, you are trying to relate the newly created issues to each other also. To do that, you could use the plural {{createdIssues}} smart value: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--createdIssues-- Let's assume you are adding two issues, and want to link the second one to the first…

Please read the community guidelines and then update your post accordingly. As you have made multiple posts like this in the last couple of days, please review all of them for proper identification of your relationship to the product / vendor. https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement…

Hi @Maksym Babenko -- Welcome to the Atlassian Community! What is your relationship to the vendor of that product? When recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Partners - Rules of…

Hi @Maksym Babenko_TypeSwitch_ -- Welcome to the Atlassian Community! What is your relationship to the vendor of that product? When recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Partners -…

I understood what you asked, and the solution I described would meet that need. Assuming the use of the Lookup Issues action with this JQL: project = yourProjectKey AND sprint = "sprint" AND sprint IN openSprints() Each issue in the results would contain the matching issues. But they could have been in multiple sprints,…

Hi @Geethanjali Katagani What is the source of the information you posted? When posting content generated by automation / chat bot, community guidelines require disclosing that source in your post. To learn more, please read the community guidelines:…

Hi @dimofeev -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have a rule and it is not working as expected, note 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…

Hi @Samuel Imrich The match() function in rules has trouble with multiple values on a text line and newline characters. To help the function, please try first replacing the newlines with spaces and then splitting the result on spaces into a list of items. This will reduce the scope the match function needs to check:…

Hi @brian.g Please see this article from Atlassian on the incoming webhook change to learn how to do that: https://community.atlassian.com/forums/Automation-articles/Update-on-Incoming-Webhooks-Trigger-for-Atlassian-Automation/ba-p/2921233 If that does not help, please contact BetterStack for more information about their…

Hi @Bud Herz If I understand your question correctly, and you anticipate more than 100 issues in any category, the Lookup Issues action would not work due to its call limits: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues An alternative would be repeated calls to the REST API…

Hi @Aurélie Pilette It appears you want newly created issues in the project to "remember" which sprint was active when they were created. Is that correct? What problem are you trying to solve by doing that? That is, "why do that?" Knowing that may help the community to suggest relevant ideas. Until we know that...there are…

Hi @Selena Llumiquinga Guasumba -- Welcome to the Atlassian Community! You posted this question in the Atlassian Community: https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement To directly contact Atlassian Support (when you have a paid license) please work with your Jira Site Admin to do so…

Hi @Tanveer Zubair What is the scope of your rule in the "Rule details" at the top: single-project, multiple-project, or global? A single-project scope rule can create (or clone) issues into other projects, but it cannot access or modify them. Thus if the rule is single-project the Link Issue action would not work as that…

Would you please show the current, complete rule and of the complete audit log details for the rule execution? And...inline math expressions require the values to be numbers. I wonder if lookupObjects.PO Value is returning a list of values and / or it is a text value. The way to check the second one is to add asNumber…

Probably not from this forum or with that type of question... This is the Atlassian Community, a place where people with similar interests gather to learn and help one another. I suspect it is unlikely a community member would take a phone call to solve a rule issue for another customer's company (except perhaps a vendor…

The "destination issue" is only relevant for the issue linking triggers. For all others, such as Manually Trigger, the rule must go get the issue data. When you want to update the trigger issue from another one, try this: * use the Lookup Issues action with JQL to load the other issue's data * use the smart values…

Once inside a set of double-curly brackets, additional ones are not needed. Perhaps try this expression: {{#if(and(lookupObjects.PO Value.gt(249999.99),lookupObjects.PO Value.lt(499999.99)))}} 499 - 250{{/}}

I recommend incrementally adding rules; that will help see which ones can be combined and how. For example, for the issue created one... * copy your current rule * change the trigger * add the Re-fetch Issue action after the trigger (This helps prevent rule timing problems.) * test! And repeat... The most challenging ones…

The only suggestions I recall in this area were to support "other formats of JSON" in rule actions...although I was unclear what was being asked for in those ;^) Please give the iterator a try and let me know if you run into challenges. Thanks!

Hi @Lauren Santarossa -- Welcome to the Atlassian Community! Here is the suggestion to add the ability to configure Smart Buttons in a template page: https://jira.atlassian.com/browse/CONFCLOUD-80888 I believe the only workaround is to copy a page which has the button configured and then make other changes to the…

Hi @Mathew Lederman Without seeing your entire rule for context... Please try the and() function to combine the logical tests: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#and And also note that function only accepts two parameters; when more clauses are needed, they may be…

Hi @Jack Brickey I hypothesize racetrack errors like this are going to get "worser" before they get "better". Today, the Issue Created trigger (or a webhook capture of that event which triggers an Incoming Webhook trigger) can fire before all of the data is available. This manifests as at least these symptoms I have…

Hi @sgover As written, your rule is stopping as soon as the first condition is not met. For your scenario, there are two solutions: * use the if / else condition block, testing for each value, making the rule around a dozen steps * a better approach is to use a Lookup Table to map the Status's name values to the Percent…