Bill Sheboy Expert

Hi @Shelly Knobbe What have you tried thus far to solve this need? If you have started a rule and have run into problems, 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…

Hi @Jamal Salameh -- Welcome to the Atlassian Community! If I understand your question correctly, that will not work as you describe: an automation rule runs and completes the steps. It does not perform some actions and then wait for something else to happen, such as the user commenting on an issue, responding to an email,…

Hi @Maximilian Floß Perhaps try using conditional logic for each field: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ For example, {{#if(not(exists(issue.customfield_10853)))}}none{{/}}{{issue.customfield_10853}} This would check if the value does-not-exist, returning "none" for…

You would not need an automation rule: instead write JQL which returns issues due soon and use that with your board configuration: * ... at the top-right of the board * Configure board * Card colors * select queries * add your JQL and select a color

Hi @Josh -- Welcome to the Atlassian Community! The replace() function is a plain text search / replace and the replaceAll() is the one which uses a regular expression, so please try replaceAll(). If you instead want to extract the values, try using the match() function with a regular expression. Also please note, the…

Hi @Edward Moxley Adding to Laurie's answer, here are the supported attributes for the user smart values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/ Kind regards, Bill

Hi @Alec Dewell -- Welcome to the Atlassian Community! Please try using the JQL operator WAS IN with DURING for that: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-IN Or the CHANGED TO operator to detect when the change…

Hi @Christian and @Trudy P Claspill The approach I outlined in my earlier post would work for this, finding the issues to link-to and then using the smart values as the key to add a single link per issue created. For example: {{lookupIssues.first.key}} The challenge is if you need to link to more than one issue to each…

I do not believe there is a way to leverage the built-in notification for a user access requests to then create a Jira issue. You may want to investigate the Atlassian Marketplace to determine if there are addons to help with this type of user management. Another possible approach to handle the removed users is to set up a…

Hi @Chasovskikh Kirill Please adjust the JQL for your Lookup Issues action to narrow to "today", as Maria suggested, or... Try adding smart value, list filtering for the full lookup results: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 Kind regards, Bill

Awesome; I am glad to learn that helped! And...please take a look at the combined-examples for list functions. They show some features for list handling not noted anywhere else in the documentation. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#Combined-function-examples

Hi @bartlomiej.jochym Adding to Walter's answer and your question... If you are using a company-managed board for your Jira project, you could also use card colors, based on the same JQL. This will increase visibility of the items if your team has a daily standup or for anyone viewing the board. Unfortunately, this feature…

Hi @Boyd Hong Variables are stored as text. To later use that as a date or date / time, it must be converted using the toDate function. https://support.atlassian.com/cloud-automation/docs/examples-of-using-smart-values-with-dates/#Converting-text-to-dates The format() function formats a field as text, not to a date / time…

Hi @Nikola Perisic What is your relationship to the vendor of the product you are recommending? When recommending a product, please ensure you disclose you relationship to them in the text of your post, as described here:…

What is the markup used to make a bullet item for the Teams message? Let's assume it is an asterisk * for now, and so the bullet list would be this: {{#lookupIssues.summary.distinct}} * {{.}} {{/}} How this works: * the distinct function on the lookup issues, summary fields produces a list * we use an iterator with the #…

Hi @Lily Bender -- Welcome to the Atlassian Community! Adding to the answers provided...I recommend looking at this free training from Atlassian on using JQL. It will cover introductory concepts and how to answer business questions with JQL:…

Hi @Luke For automation rules, branches cannot be nested...and branches which could be on more than one thing are run in parallel and asynchronously...with no guarantee of when the branch will complete, up to the last step of the rule. (This is apparently by design to improve rule performance.) In your scenario, this means…

Please show images of: * action details to create your variable * audit log details showing the rule run writing out that variable

Thanks for that additional information. The issue change history contains most of the changes over time, but using that would not match your scenario. To have a people-friendly digest for those without Jira access, you may want to investigate a marketplace addon / app specifically for this purpose, and then send the report…

Hi @Alan Rodrigo -- Welcome to the Atlassian Community! Even though you heard, "they are asking me...", I recommend asking what problem they are trying to solve by doing this. That may help to solve that problem rather than create a new one for synchronizing the summary and assignee as they change over time :^) Until you…

Hi @Osama Al-Areky Rather than using the Create Issue action, have you tried using the Create Subtask action? That will use the current issue's context (that is, the branched-to issue) as the parent. Kind regards, Bill

Hi @cynthia.toro -- Welcome to the Atlassian Community! For Jira Scrum boards, issues must be in the far right board column to be considered completed. Kind regards, Bill

Hi @Lilian Gounden Adding to Craig's answer... You could use either Lookup Tables or a series of conditions to determine your assignment based on the other fields. I recommend trying the Lookup Tables, and to learn more about that approach, please look here:…

Hi @Kim Ranch Olsen -- Welcome to the Atlassian Community! First thing, thank you for posting the details up front for your question...that helps to narrow things down. The only thing missing is an image of the audit log details, showing that error in the context of which rule steps happened. Your rule is using a scheduled…

Hi @Ylli Dervishi First thing: automatically adding issues to a sprint could cause unintended consequences and problems for a Scrum team. I instead recommend the team make a deliberate decision to add / remove issues for the Sprint, and then doing so manually with Jira. Back to your question... The sprint attributes (such…

Hi @marion.hillion What is not working as expected when you use the rule? You appear to be using a team-managed project. Would you please confirm that? Would you please show an image of the audit log details from the execution of your rule, and some additional images of the rule: * the details of the create variable action…

Hi @Almighty Drake In the images you show for the import Map Fields, there is a checkbox for each field you want to import: Map field value. Did you check the boxes for the fields you want to import, including the Summary field? Kind regards, Bill

Hi @Victor -- Welcome to the Atlassian Community! Is your "Sprint #" a calculated field based on the "Date" or is it a lookup, as you described when doing this in a spreadsheet with VLookup? If it is a calculation, you could try math and text functions to do this. If it is a lookup, please try using the Lookup Tables…

Hi @agente For a dynamic JSON generation error, I recommend writing that entire expression to the audit log, as that will show where the error is in the JSON. I suspect the problem is the conditional comma delimiter with {{^last}}; it is inside of the active conditional, and so may not be resolving as expected. Kind…

Hi @Christian -- Welcome to the Atlassian Community! You are correct: there are no nested branches for automation rules at this time. Which is a good thing (at this time) because branches which could be on more than one thing are run in parallel and asynchronously, with no guarantee of when the branch will complete, up to…