Bill Sheboy Expert

Hi @Paka -- Welcome to the Atlassian Community! Please review the with... functions for date / time as you appear to be using an unsupported one: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-with-attribute--- There are several ways to do what you ask, including this one:…

Hi @emmanuel mancuso You appear to be using Jira Server / Data Center. Is that correct? If so, the Lookup Issues action for those versions of automation do not contain custom fields yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 As you want to update a field based on the sum of fields, the REST API must be used…

Hi @Irene Viljoen and @Trudy P Claspill I believe this is the open defect for that symptom: https://jira.atlassian.com/browse/JRACLOUD-73409 Kind regards, Bill

Hi @Keith Tasker That appears to not be working as documented for rules, and I did not find any open defects in the public backlog for this symptom. I recommend working with your Jira Site Admin to contact Atlassian Support: https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn…

FYI, another way to do this is with a conditional expression: {{if(now.format("E").match("(Tue|Wed|Thu)").length().gt(0), now.withNextDayOfWeek("FRI").jiraDate, now.withNextDayOfWeek("TUE").jiraDate)}} If we know today's day-of-week is Tuesday, we know we want the next Friday. Same thing with Wednesday and Thursday. All…

That one also appears part of the evolving UX changes, and there are many community posts discussing it...including when it can get "stuck" on the backlog views. I believe it has been appearing / disappearing in the design for at least 4 years. The box appears "floating" over other fields whenever the comment history is…

Please show images for both of the complete Edit Issue actions. Again, I recommend combining these into one action. Until we see those, here are some follow-up questions: * Are those fields which failed custom fields that can be set manually by a person for issues, such as the trigger issue? * How is the issue transitioned…

If the lookup returns multiple issues, you may need to do this in pieces, or adjust the expression: * extract the last commented date from all the issues * decide / use one of them to perform that diff(now).hours

In my experience, the only way to know if something works with automation's implementation of regular expressions is experimentation and testing. So try it, and if it works, great! There are several community posts observing expressions which work in other regex parsers and do not work in rules, such as some of the on/off…

Thanks for that information, and assuming you are using Jira Cloud... Your rule is branching, looking up issues, and editing an issue three times, so that amount of run time is not unexpected. The rule is making at least 6 calls to the database after the rule starts. To reduce the duration the rule needs to perform fewer…

Please enter an exact issue key for that to work in the REST API call, such as: TNCRM-1234

To bulk-add the Slack user ID values to the Jira users (as entity properties), you may use this article from an Atlassian team member. It requires some technical / developer skills to get it to work and diagnose problems.…

Thanks for the follow-ups, and this does appear to be a defect (or a limitation in the REST API endpoint). After a quick check of the public backlog, I did not find that symptom. Another possible check: write the complete dynamic JSON to the audit log and then examine it for errors. Also we can try a different workaround:…

I just tried it with a Page Condition, checking the Title, and it correctly detected the condition for both the desired and a different page. If your rule is not working as expected, please post the following for context: * an image of your complete rule in one single image for continuity * the audit log details showing…

Hi @Gayathri B Perhaps posting more context will help diagnose this symptom. Please post the following: * An image of your complete rule, in one single image file for continuity * An image of the audit log showing the history of executions and their duration times * An image of the most recent execution (which was…

Hi @Trudy P Claspill Just a quick FYI / reminder for the date format() characters: "Y" is the week-based-year and "y" is the year-of-era, and so using "YYYY" could be a different value than a person expected during the first / last weeks of the calendar year. For example, on 29 Dec 2025 the "YYYY" would be 2026 and "yyyy"…

Hi @Myles Boyd Please try using one of the with... functions, such as * withDayOfWeek() * withDayOfWeekName() * withDayOfWeekShortName() https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-with-attribute--- Kind regards, Bill

Hi @Francisco Navarro You posted this question in the Jira community, and the email template you show has no information about Jira issues (or other entities). Did you post this in the correct location? If you did post it in the correct location, what have you tried thus far to solve this need? If you have started an…

Hi @Kerrie There are many posts in the community about that "feature" since it was introduced. It is called smart replies, and your Jira Site Admin can disable it for everyone in the system settings: https://support.atlassian.com/jira-software-cloud/docs/use-smart-replies-in-issue-comments/ Kind regards, Bill

Hi @Vasilis Kokotakis I recommend asking this question in the developer community to learn if such guidance exists: https://community.developer.atlassian.com/ Kind regards, Bill

Hi @Jolien Ryckaert -- Welcome to the Atlassian Community! Adding to Sebastian's suggestion: You would need a second rule to remove the label later...either when the current sprint completes or when the new one starts. To get you started on creating your rules, please refer to these documentation and example sources: *…

Hi @Tomislav Tobijas I found this one in the backlog, created back in 2006! https://jira.atlassian.com/browse/JRACLOUD-10156 Kind regards, Bill

Hi @Sherwin Soriano That is not currently possible with built-in features. And...there is an old suggestion for configuring the child issues' list and it is finally being worked on by Atlassian! Please watch it here to see progress: https://jira.atlassian.com/browse/JRACLOUD-70206 Kind regards, Bill

Hi @john.monteith When a rule action edits an issue, that updates the data stored in the cloud, but does not update the in-memory data for the issue in the rule. This is by design when there are cases to observe the original data. When you want the issue updates to be available, add the Re-fetch Issue action after an…

Hi @Daniel Welzel -- Welcome to the Atlassian Community! There are several errors in that JSON, including the list handling. Before we get to those, let's confirm your scenario. Do you want to replace the Parent issue's Components or add additional values to them? Let's assume you want to replace the values. Lookup Issues…

Hi @Mathew Lederman FYI -- here is the documentation for smart value lists, including information about selecting relative (e.g., first and last functions) and specific items (e.g., with get() and getFromEnd() functions) https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/ Kind regards, Bill

Hi @Matt Miller Short answer: I recommend not trying any complicated regular expressions with automation rules as there is no documentation on what is (or is not) actually supported. Perhaps try the simplest thing that could possibly work, adding edge cases only when needed, and testing fully. For example you could try…

Hi @Una Horne Your syntax is not correct for using the min function... The min function may be used with the long, format of a math expression or with a list of values (either numbers or dates / times). One way to solve what you asked is to create a list of dates to use the min function:…

Hi @Deborah Wong -- Welcome to the Atlassian Community! You are correct that this expression is the cause of what you are observing: createdDate >= startOfMonth() Instead you would use {{now}} and the startOfMonth() and endOfMonth() functions, formatting the results to work with JQL. For example: createdDate >=…

Thanks for trying those actions. Let's try to eliminate a few other possible causes. Using this how-to article to identify smart values / custom fields supported by rules, use an example issue to check if your fields are available: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ If the…