Bill Sheboy Expert

Hi @Patrick Schmidt First thing, the {{issues}} smart value (note the plural) is only defined / supported for Jira Server and Data Center versions, not for Jira Cloud. I would not rely upon that smart value for Jira Cloud. Next, you note that a numeric custom field is not available in the results of Lookup Issues. Smart…

Hi @Yana V. I recommend an adjustment to your rule to do that with the lookup issues action: * trigger: issue transitioned * condition: checking the initiator * action: lookup issues with JQL to find your source issue, such as with* key = yourSourceIssueKey * action: add comment, referencing the data from the lookup*…

Hi @Teng Bin Koay -- Welcome to the Atlassian Community! Adding to Ollie's answer... Automation for Jira is included with Jira Cloud. To learn more about creating automation rules, please look here: https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/ Also, the specific user who performed some…

Hi @Noa Tsruya -- Welcome to the Atlassian Community! Adding to Clark's answer... I'm a big fan of using tools like Miro (or whiteboards and paper) for this type of conversation prior to putting ideas into a tool like Jira. If you already have your items in Jira, have you tried using the features of Atlassian's Jira…

Hi @Eric Brown First things first: I do not believe your scenario can be solved with an automation rule only. Instead you may need to write an external service with another programming language, given your issue dates, to find the sprint, and then call that service from the rule. ---------------------------- More on your…

Hi @Tania Schmittou and all the answerers! Apologies in advance for the long explanation below :^) This is a tricky scenario due to how branches work. Your rule is written to create a version, assign issues to it with a branch, and then release the version. However... Branches which could be on more than one thing are…

Hi @Drew McLean Adding to Trudy's answer... For your scenario of wanting to count various things in the child issues, based on some criteria, it may be possible to do this with one single lookup issues call, smart value list filtering, and math functions. The advantage of this approach is it may be faster than calling…

I think I see where the extra comma-spaces are from: the {{^last}} check is outside of the condition test. Let's try moving that inside to see the impact: {{#issue.comments}} {{#if(equals(body.match(".*(React).*"),"React"))}}{{body}}{{^last}}, {{/}}{{/}} {{/}} If that does not work, the other alternative is to remove the…

Hi @Andrew Wursta -- Welcome to the Atlassian Community! Beyond the scope of the other answers provided, I wonder... What problem are you trying to solve? That is, "why do this?" For example, are there specific questions you want to answer, research, etc. which are addressed by seeing the prior comments and change history…

Hi @Urmo For automation rules, the smart value {{initiator}} is the user who perform the action that triggered the rule. For example, if I transition an issue on the board, my user information would be in {{initiator}} if the rule is triggered on Issue Transitioned. Please look here to learn…

Did you try that how-to article with an example epic to see if the smart values are available to rules?

Hi, Ben...happy new year! If you review that audit log, you will see a typo when you write {{varMessage}} as there is a square bracket in there. Please correct that and then re-test. Thanks!

Awesome! I am glad to learn that helped.

Hi @Rohit Yadav -- 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…

Hi @Laura Hanna Adding to the answers already provided... Not all fields are supported by automation rules. To learn if a field has a smart value (or custom field id) supported by rules, please use this how-to article. The essential steps are: * identify an issue which has your field(s) * call a REST API function with a…

Hi @Melissa C Are you using Jira Server or Data Center version? The different versions have different ways to gather issue data for use in an automation rule, such as with the two tables in your email. With both Jira Server and Data Center, these options are available: * Use a branch on JQL with the bulk-handling option,…

Greetings, and happy new year! Are there any updates on improving this navigation banner's impact? Thanks!

Hi @Jonathan Smith Adding to Jack's answer... The packaging model for rules changed in October 2023. What this means is all rule executions do not count against the limits (only certain rule actions do so) and the limit counts are by the Atlassian products used (not by rule scope). Please review this information carefully…

Hi @Cash Coyne Context is important for automation rule questions. 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…

Hi @Thomas Domask -- Welcome to the Atlassian Community! The chart image you are showing is from a marketplace addon / app, and is not from a built-in report. I recommend working with your Jira Site Admin to identify the vendor, and contact their support team via the Atlassian Marketplace and their support page:…

Hi @Sasha The Issue Created trigger is for new issues. Please try using the Issue Moved trigger instead. For your scenario, the rule would be defined in you Project 2. https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Issue-moved Kind regards, Bill

Hi @Guruvachan Jain What problem are you trying to solve by doing this? Knowing that may help the community to offer suggestions. Until we know that... There are no public REST API functions for automation rules yet, and only the rule status of failed can send an alert via email. A possible work-around would be to…

Hi @Sofia Reid -- Welcome to the Atlassian Community! What is your Jira Cloud license level and which Atlassian products are you using? Please confirm these with your Jira admin, and then check your automation's global usage data to see the impact of your rule(s). The answers are important because in October 2023 the…

Hi @Frank Adding to Mikael's answer... When working with a multiple select user field, your rule may use the list iterator functions to add those mentions. For example: {{#issue.yourUserField.accountId}}[~accountId:{{.}}]{{^last}}, {{/}}{{/}} To see other examples of list iterators, please look here:…

Hi @Brian Gorman 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 @Paulo Amaral Short answer: there is no synchronous processing, loop structure for automation rules at this time. And even if there was, smart value, list iterator scoping may prevent accessing the data you need to preform the search / replace operations. Longer answer: Context is important for automation rules. Would…

Hi @Isabella Musial First thing, I am using Jira Cloud and not Server version, and so cannot confirm my suggestions...with that out of the way. I do not believe dynamic fields are supported by automation rules, such as for built-in features and from marketplace apps. Those are often calculated just-in-time using code and…

Using an advanced branch, the rule should be able to iterate over just the keys found; then within the branch any actions will act on the trigger issue. And so to add the links to the trigger issue you could either add a second advanced branch after the first one...or link the issues at the same time you make the edits to…

Without seeing your complete rule and audit log, I am guessing a bit here... Looking at the expression you show, the expression for each field's iterator (e.g., for customfield_11071) is followed by a trailing comma. { "fields": { "customfield_11248": [ {{#issue.customfield_11071}}{"value":"{{value}}"}{{^last}},{{/}}{{/}},…

Hi @Shruti Shrivastava First thing, I am using Jira Cloud, free edition, and so cannot test what I suggest with Jira Server. Next, are you certain the smart value velocityStateEntries is populated / available to the automation rule? You can confirm that by writing the value to the audit log and then testing. Next,…