Bill Sheboy Expert

Hi @David Berclaz _Apwide_ That email notes reaching the monthly usage limit, and so that is likely the count of rule executions which count. Not all rule actions count, and so first review this information: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update…

Thanks for your responses, @Sophia Do Regarding my last question: I understand improvements for JPD automation are continuing. Instead I was asking if the JPD fields will be added for this help panel from the global admin, rule editor. That is the location where multiple-project scoped rules would be defined to span JPD…

Sorry, for my mistake: you are using Jira Data Center, and the lookup issues action does not yet contain the sprint field (which I find surprising). Here is the suggestion to add the other fields to lookup issues: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 The only fields currently supported are shown…

You may use the capitalize() function, adding it to the end of the expression: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#capitalize--

I updated the suggested solution so there is no trailing space after the last word parsed from the field.

Using a date or date / time field type for the custom field eliminates the need for conversion with toDate() as that is used to convert text-representations to those types. That function helps when using text variables for dates (or date / times) and when the value comes from another source, such as typed in by a person or…

Your expression is missing the pound signs before lookupIssues and before the if() expression. Please review my earlier post, add the missing characters, and then re-test. Thanks!

Hi @brian odriguez -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have a rule that is not working as expected, please post an image of your complete rule, an image of the audit log details, and describe what does not work as expected. That will provide context for the…

Hi @ayoung There is no built-in "Pascal Case" function for rules. As a workaround you could: * lowercase the input * split on spaces * recombine the values, after first uppercasing the first letter of each word, such as with…

Hi @Rosana Casilli The rule could use the date / time function format() to get the hour from the created date / time, and then use rule conditions on the result. Please look here to find additional options for that function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format---…

Hi @Jó Sales de Medeiros Júnior -- Welcome to the Atlassian Community! Some of the helpful documentation on list iteration, such as for Lookup Issues, is not all in one place. If you look at the bottom of the section on lists, there are many helpful…

Hi @Massimiliano Stretti 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…

Hi @Sami Ullah If your email addresses are in the format of firstName.lastName@domain then you could split on the period and take the first entry: {{issue.reporter.emailAddress.split(".").get(0)}} Please look here to learn more about those rule features: *…

Hi @Stacey Telford Generally for a scenario like this, one either changes the rule trigger to scheduled (or creates another rule) to make the "catch things up" changes. The key is: can you write a JQL statement to identify older issues that need the change in order to create a stopping condition (i.e., all caught up)? *…

Hi @Sophia Do Thank you for this information. Some quick questions about this feature: * What is the display order of the smart values, such as within {{issue}}, as it does not appear to be alphabetic? * Will all of the supported smart values be included later, as it seems only some of them are listed? To find others which…

UPDATE as of 2024-May: the solution with the Lookup Issues action will not work with Jira Data Center as the Sprint field is not supported in the results yet: link to suggestion to add the field. Please see the bottom of this thread for other solution approaches. Hi @Amy Sliwinski You are using Jira Data Center, correct?…

@Slava Gefen -- The only open suggestion I found is this one: https://jira.atlassian.com/browse/AUTO-490 Reading the details, the intent appears to be access data from other scopes once inside the iterator. From other communications and community posts, my understanding is the Atlassian team has tried several times to…

Hi @Walter Lamm If I am following your scenario, you are trying to create just-in-time, dynamically executed JSON, not just dynamically defined JSON. The distinction I am making is: * dynamically defined: build dynamic JSON, looking up any values at the time the JSON is created, creating a static text string * dynamically…

Hi @Ricardo Martinez Please review the other posts in this thread, particularly if you have ever (or currently do) have any team-managed projects in your site. The WAS operator does not work consistently if there are / were team-managed projects, even when the workaround of using the status id values in the JQL is used.…

Hi @Slava Gefen The more general, automation limitation is: once inside of an iterator, only data from that scope and lower is visible. And so nothing from outside (or higher in scope) can be accessed. For your scenario, I believe there may be only a few options possible rather than using a Lookup Table: * brute force* Use…

Thank you for the follow-up, Narsha.

What type of project is this: company-managed or team-managed? You may find that information at the lower-left of the page expanding area. And if this is team-managed, did you add this custom field yourself to the project?

Well, done! I have two suggested improvements to your rule: * Is it ever possible that an issue could transition from To Do to In Progress multiple times? If so, add a related issues condition earlier in the rule to ensure the subtasks do not already exist. * After each Send Web Request action, check the results with a…

Thanks for that information, Ray. There are known problems having now first in a diff() expression, although there does not seem to be consistency of the symptoms (according to community posts). Additionally, there is a known problem where it diff() does not work accurately inside of an iterator / loop. You note "Need By…

Hi @Affirah Jan -- Welcome to the Atlassian Community! First thing, this is a very old thread, and so I recommend creating a new question with a link back to older threads. That will ensure the maximum number of people see your question to offer suggestions. Thanks! Back to your question... My original suggestion for a…

Thanks for that information, John. To summarize, it appears the purpose of your rule set is: detect when an issue has been in the same status for more than 4 working days (i.e., Monday - Friday), in order to add an indictor label. With text fields to represent the dates, they will need to be converted with toDate before…

If the issue field's smart value is Date Needed By, and it is a date field, this would do it: {{issue.Date Needed By.withYear(now.format("YYYY").asNumber)}} If you need that in jiraDate, text format, please add that to the end: {{issue.Date Needed By.withYear(now.format("YYYY").asNumber).jiraDate}}

Hi @Jonathan Chatfield You describe your automation rules do not have the Lookup Issues action; thus I am guessing you have Jira Server, correct? If so... First thing, please write some JQL which returns the child (and grandchild) issues for an epic, without returning the epic itself. Then your rule could use the Send Web…

Hi @VVC and @Kalyan Sattaluri Rather than building the date up as text, have you considered using the withYear() function to change the year to what is needed: https://confluence.atlassian.com/automation/jira-smart-values-date-and-time-993924864.html#Jirasmartvaluesdateandtime-withYearwithYear The value from the current…

Hi @Lauren Folk -- Welcome to the Atlassian Community! For an automation question like this, context is important... Please post an image of your complete automation rule, images of any relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Those will provide context for…