Bill Sheboy Expert

There is no smart value named {{latestVersion}}. What are you expecting that value to contain? What value is set to the Fix Versions field in the Edit Issue action? And most importantly...your rule trigger is Sprint Completed. Why not use {{sprint.id}} with the branch JQL to find the issues in the sprint? The Lookup Issues…

Heather, would you please post an image of your current complete rule and of the audit log details showing the execution (with all of the areas at the right side expanded)? That context may help explain what you are observing. Thanks!

As I do not have a Jira Data Center site, I do not know...my suggestions were based on how the if / else block works for Jira Cloud. I was noting the order of the testing based on most-to-least restrictive, ensuring there would be no overlaps in cases. If you have tested all of the cases and it works as expected, you are…

Hi @Sundram Trivedi What do you observe happening that is not working as expected? Please post an image of the audit log details for the rule execution (will all of the area at the right side of the log expanded). Until we see that... For scenarios like this, I recommend posting the complete expression used to form the new…

Well done, and...creating the full logic table helps to use techniques like from Karnaugh Maps to decide what / when to test... Viewing the table shows only the cases where "Child tickets are Done or Complete" do something, and so moving that test first (before the if / else block) helps. Next, whenever the Operations…

Hi @Naomi Mack -- Welcome to the Atlassian Community! If I understand your question, the rule would not use JQL to do that. Instead it would use the minusBusinessDays() function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-minus-unit--- If that does not help, please post images…

Hi @rajvr -- Welcome to the Atlassian Community! You appear to be asking a question about an automation rule. Is that correct? If so, please note context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete…

Hi @Steve Rhodes Have you tried adding a check if the Request Participants field is empty also in the condition: "Request participants" NOT IN ( {{issue.comments.last.author.accountId}} ) OR "Request participants" IS EMPTY Kind regards, Bill

Hi @Allan Conybeare -- Welcome to the Atlassian Community! The JSON syntax you show is incorrect to set the value of a single-select option field: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-select-custom-field Next, the logic you are attempting will require using upper and…

Yes, that updated rule looks correct. Well done! Regarding "Area Crew", with the Data Center version of automation rules, I do not believe if / else blocks can be nested yet. Given that, there are several alternatives... Creating separate rules will potentially create rule maintenance / update problems, as they could get…

Greetings, community! The information about automation rule impacts is incorrect: In my free license test site, automation rule components have already been renamed from "issue" to "work item" terminology, even though neither the documentation nor the smart values (or underlying REST API endpoints) do so. This change…

I recall sometimes web responses in rules do not fully resolve as JSON that can be accessed with dot-notation. Let's validate that using the Log action... Please use Log actions to write each of these to the log after the response is returned, validating if they contain what you expect: The first value:…

Hi, Heather. Rather than suggesting two different approaches, please continue with the thread with Andrea and I will pitch in to help if an alternative is needed.

Hi @Sérgio Baixo Adding to the suggestions from @Gracjan Wesołowski _HeroCoders_ ... Please also show the entire Edit Issue action in your rule. It appears to also be making a change using the advanced edit with JSON feature and perhaps there is a problem with the JSON expression. Kind regards, Bill

Hi @efronza -- Welcome to the Atlassian Community! Adding to John's suggestions... When using the default filter sort of ORDER BY Rank ASC, work items appear on the board in the rank ordering selected from the backlog. There is no automatic option to move them to the top / bottom of a board column when added to the…

Hi @Evert Morren Atlas Admin For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule…

Hi @Katy Rupp -- Welcome to the Atlassian Community! You could add the value after the current value. For example, let's assume you wanted to add the trigger issue's key to the end of a description field being edited. That would look like this: {{issue.description}} {{triggerIssue.key}} If this does not help, please post…

Without knowing the complete steps in your rule and the details of the edit, it will be difficult for the community to offer suggestions. I recommend asking the same questions to your Jira Site Admin to learn how they can help.

Hi @Christopher Vickery The scenario has a different starting point, and so the rule would have a different trigger... You could start with your current rule, copy it, and change the trigger / flow. For example: * trigger: field value changed for Fix Versions * condition: issue type is Epic * steps to identify the added…

To post the images, capture the images and use the "Insert Photos" button when responding in this thread:

Thanks for confirming that. Have you first tried using the Edit Issue action to copy from the parent? If that does not work, please try the advanced edit with JSON I described above. And if that does not help... Please post an image of your complete rule, of the edit issue action, and of the audit log details showing the…

Hi @Ganea_ Merissa -- Welcome to the Atlassian Community! What is the type of your "Community / Entity" field? Is it a selection list, cascading field? If so, the "parent" and "child" values must be selected separately: the parent is {{issue.customfield_10031.value}} the child is {{issue.customfield_10031.child.value}}…

Hi @Heather Ronnebeck Without seeing your entire rule (and audit log details) for context... What is the purpose of the asJsonArray added to the end of the expression? I would expect using just asJsonString would be sufficient to produce the CSV list: fixVersion IN ( {{triggerIssue.fixVersions.name.asJsonString}} ) ...…

Hi @Mike Boutin -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image for continuity, * images of…

Great, and just to confirm: is this question resolved? If so, please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @Yehuda Dembsky The {{branch}} smart value is only available with the branch-related rule triggers. When other triggers are used, workarounds are required, such a calling the build-tool's REST API endpoints using the Send Web Request action to access other information. Kind regards, Bill

The root cause of the original symptom you note is: * Once inside of an iterator, only data from that scope and lower is visible; this is a known, long-standing limitation of rule iterators * And so the trigger issue's summary and URL are not visible Providing the repeated information one time is a better solution for your…

Have you tried the rule change I suggested? If so and it is not working, please post the following for context: * an image of your complete rule in one single image for continuity * images of each step in the rule: trigger, actions, conditions, and branches * an image of the audit log details showing the rule execution,…

Certainly! The "created" scenario will be similar to your current rule: * trigger: issue created * action: re-fetch issue (I recommend always adding this action after the issue created trigger to prevent timing / racetrack errors.) * related issues condition: check if there are linked issues present that is a parent;…

Hi @Myles Boyd The problem is likely from the newline characters in the Description text causing the search to halt. Many of the text functions have problems when there are newlines in the text. The solution is to first replace all of the newlines with spaces: {{issue.description.replace("\n", " ").substringBetween("Serial…