Bill Sheboy Expert

Hi @Mikki Bisschoff You could do this with an automation rule. The challenging part is sending the notification 10 days early, and such a rule could be: * use a Scheduled Trigger, * call the REST API endpoint to find / search any relevant upcoming versions with the Send Web Request action, * use conditions to determine any…

Hi @Asier Vadillo The symptom you observed is likely caused by one of the many racetrack timing problems that can happen in rules. Specifically for your case, in the Send Web Request action's Custom Data, the content may be validated before it is fully evaluated to populate the smart values. And, this is why using the…

The project ID (i.e., the numeric value) must be used, not the key (i.e., the alphabetic one). Is your custom field a project picker? If so, please try this: {{issue.customfield_10400.id}} or this {{issue.customfield_10400.value.id}}

Hi @Florian Beqiri For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions /…

Hi @Alexandra Militaru To dynamically select a project for the Create Work Item action, please use the project's numeric ID value rather than the key. Kind regards, Bill

Hi @Natalie Cotela Yes, and...to the suggestions from Valerie: Atlassian supplies built-in templates for this scenario. To use them please try this: * from the rule list * select templates * find this rule, and select it for use: When all child work items are completed → then close parent * modify the rule to add any…

Hi @Thomas Brusati Atlassian supplies template rules you can use as starting points for these scenarios: * from the rule list * select templates * find this one, and select it for use: When all sub-tasks are done → move parent to done You may also copy that rule and edit it for the "In Progress" scenario. Kind regards, Bill

Hi @Neven Plakalovic -- Welcome to the Atlassian Community! This scenario is easier for Jira Cloud with the Lookup Issues action in rules. However, in Jira Server and Data Center, that action does not support most fields yet. Here is the suggestion to add the feature: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877…

Hi @Rudy Holtkamp Thanks for the feedback! When community questions ask how to solve this need, I have sometimes suggested using an external service endpoint, purpose-built for it. My intent for the article was the methods to solve it with the built-in features...such as dynamic list creation and filtering. I updated the…

Hi @Christy Kennedy While the work items in your Lookup Work Items result are in the order the filter returned, a branch processes in parallel and asynchronously. Thus, the logging order is undefined with a JQL branch. You could remove the branch and write the information with a single log write using the lookup results to…

@Sarah Jones are you using Jira Cloud, Server, or Data Center? With Cloud, there is only one "version" of automation...although there are additional features at the highest license levels of Premium and Enterprise.

Hi @Birkan Yildiz _OBSS_ As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording, and not just in your profile name / badge. For more information, please see: Atlassian Partners - Rules of Engagement…

Hi @EPMO -- Welcome to the Atlassian Community! Yes, and...to the suggestions from Valerie: Remember to check the usage by product and timeframe as the limits (and how they are counted) differ by Atlassian product (e.g., Jira, Confluence, JSM, JPD) and license model (e.g., by different license levels and / or by user). I…

Awesome; I am glad to learn we confirmed it was a date after all! It is unfortunate there is limited documentation from Atlassian on which date / time fields are text versus date types when they reach rules. As we found...experimentation is key!

Hi @Eydie Fitzgerald Have you tried updating the Remaining Estimate directly in the Task with a JSON edit? https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Time-tracking-and-logging-work Kind regards, Bill

Hmmm...so either that is text (and will not convert to a date for some reason) or it is a date type. These would confirm it: * If {{issue.customfield_19810.trim}} fails, it is not text, it is a date. And so it should be possible to use it that way elsewhere. * If {{issue.customfield_19810.trim.toDate.jiraDate}} works, it…

Based on all of that, the field did not convert to a date or it was already a date. Please change your log action for: * action: Log, with this expression... customfield_19810 with toDate: {{issue.customfield_19810.toDate}} Into this: * action: Log, with this expression... customfield_19810: {{issue.customfield_19810}}…

Hi @Ryan_Buschmeyer It is the second one you show, {{jsonStringToObject(agentJSON)}} and then reference the attributes needed. I recommend writing the entire thing to the audit log to confirm it contains what you expected. And...as this is an older thread / closed question, I recommend creating a new question, perhaps…

Thanks for those additional checks, @Shahriar This could be a timing problem where the smart value expression is not evaluated fast enough for the Edit Issue fields action to use it. The way to check that is using a Created Variable action to pre-build the JSON for use in the action: * action: create variable* variable…

No problem, @Don Hames Let's assume the smart value could be parsed into JSON, and it had a list with an attribute named "key" with the work item's key. The dynamic JQL might be this: key IN ( {{jsonStringToObject(mySmartValue).key.distinct.join(", ")}} ) That might produce a result like this: key IN ( ABC-123, ABC-456,…

Hi @Sarah Jones First, it appears you are using a bot-generated suggestion for the rule. I recommend caution when doing so as such tools cannot access your Jira site configuration, and thus the "guesses" may be less relevant or accurate. Even the Atlassian-built bot has trouble guessing many scenarios for the same reasons.…

Hi @Priyanka Agrawal Without seeing your entire rule for context...this is not possible as you described it. Rule branches on more that one thing are run in parallel and asynchronously with no guarantee of when the branch will complete up until the last step of the rule. Thus, a variable cannot be created before, updated…

Hi @Don Hames Without seeing your entire rule for context... You could parse the keys out of the JSON, using that to create a dynamic JQL expression, and then branch to the issues for edits. And, if the JSON is only recognized as text, you could use the jsonStringToObject() function first to more easily parse the data to…

If you are using Jira Cloud, have you tried using the Send Web Request action and the Team endpoints to get the list of all teams, and then filter by name to get the one needed? https://developer.atlassian.com/platform/teams/rest/v1/api-group-teams-public-api/#api-public-teams-v1-org-orgid-teams-get

Thanks for that testing, @Shahriar Based on the log entries you see, either those are not the correct smart values for the fields or they are not supported by automation rules. To check if the fields are supported in rules, please use this how-to…

First, please confirm the custom field ID. Earlier you noted it was customfield_13205 and now you show a rule with a different one: customfield_13206. Next, please show an image of your complete rule and an image of the edit issue action for that last custom field. And, earlier I described adding some Log statements to…

Hi @Siva Kedari Veerla Adding to the ideas from @Trudy P Claspill here is the suggestion to add the ability to split any exported rule file so it can be imported under the limits. You may vote for / watch it to see any progress. https://jira.atlassian.com/browse/AUTO-1255 Kind regards, Bill

Thanks for that information, and... Have you confirmed the field you are seeing in the endpoint response is that same field by comparing the custom field ID value? I have noted other questions / posts where people had two different fields with the same name (one company-managed / global scope and another TMP) and were…

Hi @Shane Cyr When I try that for a team-managed project (TMP), custom number field, I get 0, as described by @[deleted] Would you please post an image of that custom field's configuration in the TMP, including any formatting options you are using? (e.g., currency, percentage, different units, etc.) Kind regards, Bill

Would you please post images of your complete rule, the edit action, and the audit log details showing the rule execution? And... * what version of Jira are you using: Cloud, Server, or Data Center? * if using Cloud, what type of project is it: company-managed, team-managed, JPD, JSM, etc.? UPDATE: Please disregard the…