Bill Sheboy Expert

This is interesting (and perhaps a defect): even though the mathematical functions work with numbers and dates, the MIN() function appears to not recognize dates as numbers with this syntax: {{#=}}MIN({{issue.oneDateField}},{{issue.anotherDateField}}){{/}} That appears to be true even when the dates are forced into a list…

Would you please write that smart value expression to the audit log, and then post an image of what it includes after the rule runs?

Hi @Mary Kasinger Adding to Trudy's questions... This question seems to overlap the other one you posted here: https://community.atlassian.com/t5/Jira-Software-questions/How-to-automatically-set-due-date-to-the-first-day-of-next-year/qaq-p/2267048 Kind regards, Bill

Hi @Alon Shoham I see at least two things to improve your rule... The MIN function needs to be enclosed in a mathematical expression, and cannot be used stand-alone as you show. It needs the {{#=}} and {{/}} wrapping. Please look here for examples of…

Hi @Yong Yang Is that your entire rule? FYI it can help for a question like this to post images of your rule and the audit log details for context. If that is your entire rule, please note the Issue Created trigger can fire so fast that the issue data is not available for use in other rule actions. That can lead to…

Hi @Marije Pierson Yes, and...to Mark's answer... Automation rules often require a bit of learning and experimentation. To help get you started on creating your rule, please review this documentation and examples: * https://www.atlassian.com/software/jira/guides/expand-jira/automation *…

Hi @andreea andra -- Welcome to the Atlassian Community! If I understand what you described with this... If I realize during writting the story that I want to delete component B, I want the subtasks which are related to component B to be deleted, or if I realize that I want to add component B back, I want to be created…

I believe that error is from the status name not being wrapped in quotation marks in your related issues condition. Please try this instead there: status = "Dev Task Completed"

Hi @Michael Yes, and...to Nic's answer...You could trigger on any issue transition, followed by an advanced compare condition before proceeding: * first value: {{issue.status.statusCategory.name}} * condition: equals * second value: Done The rule will fire much more often than necessary, and avoids the need to name all the…

Hi @Zaldy Parian Just to confirm...your scheduled trigger does NOT have JQL, correct? If so, it appears you want to send that email to all possible assignees for the issues in the lookup issues result. To do that, please update the email TO with the below expression. {{#lookupIssues}}{{assignee.emailAddress}};{{/}} That…

Thanks for that information. I think this is both a smart value name/case-sensitive and default attribute thing. Please try changing your advanced compare condition to check this: * first value: {{issue.issueType.name}} * condition: equals * second value: Dev Task And...if that does not help, try writing this to the audit…

The Lookup Issues action accepts your JQL and then returns a set of issues, like this: You may then access the fields of the returned issues to create your new issue, as shown below. I recommend specifically selecting your project and issue type using this approach. The complete rule would look like the one below,…

Hi @Phil Bustin Would you please post an image of the audit log details, showing the rule execution? That may provide more context for this symptom. Thanks! Regarding your comment about the "And" in the old screen image (from that post), I believe that is just the evolving UX of the rule editor, over time, changing. Kind…

Hi @kasik0109 I am unclear what you are trying to accomplish: * copy the custom field's value from the linked issue, * sum the custom field value from several issues, or * something else. Would you please clarify your goal? That will help the community to suggest ideas. And also, when a rule does not work as you expect,…

Hi @Ömer - OBSS Once inside a set of curly-brackets you do not need to repeat them. Please try this: {{now.plusHours(webhookResponse.body.table.body.rows.valueColumns.value.get(0).asNumber)}} Kind regards, Bill

Thanks, and that helps. The JQL for that trigger will return *all issues* which have frequency = Weekly. As you are running this rule once a week, the number of issues it finds will increase by one each week. I am guessing you only want to copy the fields from one, example issue instead. Does that sound correct? If so, you…

Great! So is the rule working as expected now?

Hi, Mary. Would you please explain which issues are being duplicated? And, please post an image of the audit log, expanding the details to show for the different rule runs which you believe are causing duplication. Thanks!

Thanks for that information! You may want to suggest to the support team to add that function to the automation documentation for date/time functions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

This is what I described earlier: first create an epic and then reference only that epic using {{createdIssue}} (note this is singular) and not the list of issues. As you seem to be changing the scenario you originally asked (by adding more epics) I ask that you post an image of the complete rule in one continuous image.…

Please post an image of your entire rule, as I believe that will show you are referencing issue fields and not just the created variables or the lookup issues results.

Thank you for that information. It appears you are using Jira Server/Data Center version. Next check with your Jira site admin to learn what addons/apps you have available, as one of those will be needed to send messages directly to MS Teams. For example, if you have the full version of Automation for Jira installed, you…

That is correct. When a JQL statement in the rule editor contains smart values (such as {{varAssignee}} ) it cannot be validated yet. Only when the rule runs can it be evaluated.

Hi @Phil Bustin As that seems like a new use case, I suggest creating a new question post for it, and link back to any relevant ones for context. Otherwise only the people following this current thread will see it to offer suggestions. Kind regards, Bill

As site admin you can navigate to the Global Rules administration, and then edit your rule's Details to change the scope from a single project to global or multi-project..

Hi, Kevin. Sorry, as I did not see in your rule you were creating multiple epics, with associated tasks. If you are trying to do this repeatedly (e.g., add an epic, add tasks, and link to that epic), you will need to repeat the pattern I suggested AND use a different created variable as a precaution. Something like this: *…

I suspect the cause is you are using a Scheduled Trigger with JQL, which then runs for each issue found. The fix is to remove the JQL from the trigger. For example: * trigger: scheduled with no JQL * action: Lookup Issues with JQL for issues created * action: create a variable to save your issues created count * and so on…

Hi! Please try to keep your posts to one thread. That will help others who look at this information later see when there are multiple possible answers to a question. Thanks! Next, I note you are sending to "@{{assignee}}" in the message action for the "Channel or User". Perhaps there is something not working for the…

Hi @Hadar Dinte What have you tried thus far to solve this? Using automation rules often requires learning and experimentation, so the documentation and examples in the template library can help. If you have not started yet, I suggest using the Lookup Issues action with JQL to capture the issues for each of your measures.…

Hi @Ran Wronsky Smart values are name, spacing, and case-sensitive. Have you tried changing to use what the documentation shows for trigger issues: {{triggerIssue}} When a smart value does not match, it gets replaced with null, and so could cause problems in rules. Kind regards, Bill