Bill Sheboy Expert

Awesome; I am glad to learn that helped!

When using JSON to update a date field for a rule, the value must be text in the jiraDate format. Please try this for the JSON expression: { "fields": { "customfield_13205": "{{issue.customfield_19810.toDate.plusBusinessDays(3).jiraDate}}" } }…

Thanks for that information, @Jason Bush It shows the rule is missing the Lookup Work Items action. Please change your rule to add that before the message is sent: * action: version released * action: lookup work items, with this JQL fixVersion IN ( {{version.id}} ) * action: send Slack message

Please add some Log actions to the rule to confirm what is in the smart values for the fields before changing them. For example: * action: Log, with this expression... Target Discovery End Date = {{issue.customfield_19809}} Next, what I believe is happening is you are changing one field, then trying to use the updated…

Hi @Jason Bush First thing: in general, I recommend not using bots / AI-tools to answer Jira automation questions. Such tools do not have access to your specific site instance, and thus do not have context for your Jira version, configurations, spaces, etc. To that point, for a question like this, context is important for…

Thanks, @Monique vdB !! I did see that for the latest slow down...and where it shows in the history when hovering over the various dates in the past:

Hi @Shahriar When the advanced planning / roadmap fields (e.g., Target start) are supplied to automation rules, I believe they are plain text. They must be converted with the toDate function for use with the date / time functions: {{issue.customfield_13205.toDate.plusBusinessDays(3)}} Kind regards, Bill

Hi @arielei Thanks for confirming the observed configuration behavior, although I wonder... Earlier in the year, Atlassian announced the sunset of the default / plain text renderer, and follow-up posts implied this made all short text fields into one-line rich text. Thus, I would expect that link markup to work. Atlassian…

Hi @Michael Olabintan I suspect this may be an encoding problem rather than a message length one. Please try adding the jsonEncode or asJsonString functions to any smart values which could have markup: summary, description, etc. *…

Your criteria for how you want to set the custom field will decide that... In the rule I suggested, I added a condition to check if the custom field is empty before proceeding. My assumption was you want to set the field once, even if a work item has re-work and goes backwards in flow. If that assumption is valid, the…

Hi @mborinstein For your first question, the rule I suggested could be used to replace your existing one to set the field. For your second question about the "Ready for Release" and "Done" statuses, I expect those are different categories. You could use a different rule for that which just checks the destination status to…

Hi @mborinstein There are at least two ways to help with this scenario: 1) Update the workflow so items must go through the "In Progress" status first. This would act as a reminder when someone tries to move straight to "In Review". 2) However...if they forgot, as you describe, #1 will not help. Assuming both the "In…

My bad; I should have put that in there with the first post! Here is the full doc for JSON edits in rules: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ And, you likely will need the custom field ID for your Team field, which you can find using this…

Hi @Scott Derderian I believe an advanced edit with JSON is needed to set the Team field in a rule. Have you tried that yet? Kind regards, Bill

Hi @mborinstein Please try using the WAS IN and DURING operators for that JQL query: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-IN Kind regards, Bill

Hi @Pedro Paulo de Freitas Junior Without seeing your entire rule and audit log details for context... Please try these two changes: * The match() function can have trouble with line breaks and other formatting in comments. I recommend replacing those and removing duplicates with distinct (to remove any markup problems).…

Hi @Serhii Okhotnik -- Welcome to the Atlassian Community! Yes, and...to what @Marc -Devoteam- suggested: The {{index}} smart value is a property only available when iterating a list, and it cannot be used in more complicated syntax, such as a conditional expression. (Indeed, only recently has Atlassian added the ability…

Hi @Kathy Burgess What have you tried thus far to solve this need? If you have a rule that is not working as expected, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * an image of your complete automation rule in a single image…

Hi @AppFlow Yes, and...to the information from @Dan Breyen In the Developer Community RFC for the new search, I recall Atlassian noted the returned changelog count was limited, independently of the maxResults selected for the work item search itself. They stated to get more changelog entries, the separate changelog get…

Thanks, @daniel.jones -- Sorry, I should have read the other posts to catch up! Once you extract the TAD subtask's issue key, I would expect a branch to that with JQL will work as long as the subtask issue is not also passed in the trigger. And, as branches cannot contain an IF / ELSE block for the conditions on the PR…

Whatever comes into the trigger / rule, I was only noting the limitations of branching and the issues. What do you want to do with the issues coming into the trigger: update them or just "read" them, such as for reporting elsewhere? Perhaps if you explain what problem your rule is solving (i.e., why do this) that context…

Hi @Brock Jolet Short answer: in my opinion, the Atlassian team would need to decide to support better rule management, documentation, and "snippet" reuse before this improves for customers at all license levels. Your solution of "snippets" by using the Send Web Request action to "call" an Incoming Webhook trigger rule…

This is the trigger option I noted based on your image: Issues provided in the webhook HTTP post body https://confluence.atlassian.com/automation/jira-automation-triggers-993924804.html#Jiraautomationtriggers-incomingwebhookIncomingwebhook * If you are not using that option, the rule image you posted does not match...and…

Thanks for your diagnostic checks as the rule actor was my next suggestion :^) When the rule runs with that JQL, currentUser() would probably try to use Automation for Jira, and that does not match your scenario. Let's use the initiator in the JQL as that is the person who created the work item: AND assignee =…

Thanks for those images, @Cooper as they show several things to improve in the rule. Please fully read my response before trying any of the parts of it. First thing: there is no previous function for fields / smart values. Whatever source suggested using that feature (e.g., an AI tool), I recommend not using it in the…

The image you show in this post linked below indicates the trigger uses "Gather issues from request": https://community.atlassian.com/forums/Jira-questions/JQL-Branch-not-working-what-is-the-quot-Issue-quot/qaa-p/3144769#M1157184

Thank you for those images, @Eydie Fitzgerald In the branch on JQL, is this option selected below the JQL: Only include work items that have changed since the last time this rule executed If so, that is the problem why the rule cannot consistently find it. Please deselect that option and re-test.

Hi @daniel.jones The rule uses the Incoming Webhook trigger, gathering issues from the request. This means the trigger has issues, and... A branch on JQL automagically excludes trigger issues from the JQL to prevent errors, such as runaway looping. That is, behind the scenes, it adds this to the end of the JQL expression:…

Hi @Sérgio da Silva With an automation rule's Clone Work Item action, you may create it directly in the another space (formerly called "project"). Have you tried that approach? Kind regards, Bill

Let's align on some context...please post images of: * your current, complete rule in one single image for continuity * the action where the variable is created * the action where the edit with the variable happens * the most recent audit log details showing the rule execution One more thing to consider: Due Dates are just…