Bill Sheboy Expert

Hi @Aaron Micallef Does your scheduled trigger have any JQL to select issues, perhaps for use later in the rule to create the new tasks? If not, I do not see anything obvious in your rule to cause this. The symptom seems to indicate a timing problem, such as referencing information which is not available. If you look back…

Hi @Chayoung Kim What have you done thus far to solve this? If you have started an automation rule, 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…

I am glad to learn that helped. Did that resolve the question for you? If so, please consider marking this one as "answered" so other community members with a similar need can find solutions faster. Thanks!

Hi @Peter Skokan -- Welcome to the Atlassian Community! The challenge with a expression like this one is your {{^last}}... handling is outside of the point when the expression can detect if there is a value or not for both conditions. It appears the variable part of your planned JSON is swapping the Time and TimeInvoiced…

Hi @Wesley Vestjens Yes, those things are possible. I am assuming "Refined Story Points" is a custom field you have added. And so the first thing to do is to identify either the smart value or custom field id for that one. You may use this how-to article to do…

Hi @[deleted] There are a couple of possible causes for what you are observing... In your expression, you are trying to use the concat() function on a literal values of "P" and that is not possible. The function can only be applied to a smart value. The fix for that is to just remove the concat() completely: { "fields" : {…

Hi @Ryan McGee You could try to put that literal value at the front when setting the Summary field for the subtask create. For example: PEER Review - {{issue.summary}} - ...and so forth Kind regards, Bill

Hi @Emilia KASPRZYK That might be possible...Are these custom fields you have created? If so, please use this how-to article to identify the supported smart values (and custom field ids) for your fields. Smart values are name, spacing, and case-sensitive so using the correct one is key. Essentially the steps are: *…

Based on what you described, it is possible. As your company's Jira site and custom fields are different from others, your solution will be different. What I provided is an example of how to do this and the steps to do so; identifying your field, values, updating the rule, and testing would be done by your team. I…

Hi @Rishi -- Welcome to the Atlassian Community! Yes, there are at least two ways to do this: counter with advanced branch, and a web request. First thing: how is the number of subtasks to create determined? Let's assume you have a custom number field with the value. That could use the rightPad() function to create a…

Hi @Emilia KASPRZYK Have you confirmed it has a value for the issue, with the audit log? What is the type of your custom field, customfield_10230? Please note, some fields which Jira indicates are date (or date/time) fields are actually text when they reach an automation rule. For those cases, toDate must be added for a…

Hi @Kalyan Sattaluri When iterating over a list, you may add additional text before or after the values...or even before / after the iterator itself. Let's assume your list is stored as text in a variable named varMyList, with values of: 50810, 50811. And so the delimiter is ", " (a comma followed by a space). That can be…

Hi @Kalyan Sattaluri Without seeing the specifics of your rule or audit log details... Please review the syntax differences for setting versus adding labels with JSON, write your created variable to the audit log, and then adjust…

I suspect there is either a problem with the rule structure or the that specific regular expression. Please post images of your complete rule, the details of the branch using that regular expression, and the audit log details showing the rule execution. Those will provide some context to help. And also, I wonder if you…

Hi @Narek Nahapetyan -- 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 @attaf sheikh -- Welcome to the Atlassian Community! That is not possible with the built-in JQL features for two reasons: * the date information of sprints cannot be queried * there is no roll-up feature to perform your month-based reporting Possible work-arounds depend upon how often you need this reporting and desire…

Hi @Rita Saad YOUNES Are you trying to perform this calculation in an automation rule? If so... 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…

Hi @Zohaib Lodhi -- Welcome to the Atlassian Community! You do not show the remainder of your rule, the details of the Remaining Estimate edit, or all of audit log details, and so I am guessing a bit here... First, if you view the audit log from the list of all rules, do you see multiple rules running? If so, another rule…

Hi @Anahí Luque Regarding your first question: Within an automation rule with a version-related trigger, only some of the fields of the version are available as smart values. You may access many of the other fields of the version by calling a REST API function with the Send Web Request action. Here are some links…

There is no way I know of around that: there is an automation rule limit of up to 100 issues for lookup issues and other aspects of rules have other limits: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 If you often expect more than 100 issues, you…

Hi @Steven Johnson Adding to Mikael's answer: Here is a how-to article for calling a REST API function from a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 If you perform a web search for your Jira Server REST API you can find the function…

As a tip, using automation rules successfully requires learning and experimentation. Otherwise if one just uses rules created by others it will be difficult to maintain or improve them. If you review the documentation at the links I provided, you will find several ways to check if an issue has a parent, or not. With the…

Thanks for clarifying the scenario. First thing: I recommend confirming the smart value for your field in that expression. Smart values are name, spacing, and case-sensitive, and the often do not match the display name on the issue views. To confirm the smart values for your field, please check this how-to…

Hi @l.kustrzynski In accordance with the community guidelines for marketplace and solution providers, please ensure you disclose in the text of your post your relationship to a vendor when recommending their products. Please see the community guidelines for more information.…

Hi @Geneviève Carton de Wiart Please see this knowledge base article for the various methods of finding a custom field id: https://confluence.atlassian.com/jirakb/how-to-find-any-custom-field-s-ids-744522503.html One of the quickest is just using a REST API function with a browser, as that will also show if the field is…

Hi @Mr Available -- Welcome to the Atlassian Community! You have most of the pieces, but your rule structure is a bit off. Your rule's branch is looking for stories, as if the trigger issue was an epic...which does not seem to be what you want. This rule can be done without a branch, as many of the issue's parent's fields…

Hi @Paul Pasler _Seibert_ 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…

As you are using your custom fields, which are date/time type, you may not want to use businessDays with the diff() function. That would only be whole-days of numbers. There are no other "business" units for that functions, such as hours, minutes, or seconds. And so any diff will be in clock time, 24x7, including weekends…

Hi @Ron Aisen 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 @Relja Mihajlovic -- Welcome to the Atlassian Community! The packaging model and rule execution limits changed at the start of November. Please review this information completely to learn the impact for your usage: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update Answering your specific…