Bill Sheboy Expert

Hi @Mathew Lederman I agree: there are too many diverse (and sometimes contradictory) sources to monitor for updates and issues. One possible approach depends upon how much time you want to invest... For example, you could develop your own schedule to check various sources, and perhaps divide-and-conquer this with your…

Hi @Alexandria (Lexi) Codd For automation rule questions, please also include the audit log details showing the rule execution (with all areas at the right side expanded). That will help compare which steps ran and upon which work items. Until we see that... Please note many work item links types are directional. For…

Hi @Samuel de Oliveira Batista -- Welcome to the Atlassian Community! There is an automation rule action to link two issues: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Link-issues However you do not provide enough details for the community to offer other suggestions. For example: * what…

Yes, that is correct. Please test to learn if that helps the conditions pass when expected.

Hi @Josh Drake Based upon other community questions and the knowledgebase, I believe there are two ways to solve this: * multiple rules* in your current rule, when the work item is created and an indicator (or have data present to know the request type should be set and the issue transitioned in status) * create another…

Using your rule as a starting point, I will add a bolded section for the addition: * trigger: work item transitioned * condition: issue type equals Tarefa * branch: to the Parent* condition: Status does not equal EM DESENVOLVIMENTO * condition: Due Date is empty * action: Lookup Issues, with JQL of* parent = {{issue.key}}…

Hi @Ben Silver As @Shawn Doyle - ReleaseTEAM describes, the problem is the Change Page Owner action cannot "see" the newly created page, and so a branch is needed first. However... A new problem will occur: the branch will happen so quickly the page will not be available yet, preventing assignment of the page owner. I just…

Greetings! Regarding this reference: ...there's not a smart value way to generate from 1 to 50 with commas between Please see this post describing how to do so using the rightPad() function: https://community.atlassian.com/forums/Automation-articles/Branching-over-smart-values-in-Jira-Automation/bc-p/1886284#M531 And when…

Thank you for the additional information. Your rule is missing a step to use the Lookup Issues action with JQL. That must be used before the {{lookupIssues}} smart value may be used in the edit. For example, inside of the branch that might be this: * action: lookup issues, with JQL of* parent = {{issue.key}} As needed,…

Hi @Ty Foster -- Welcome to the Atlassian Community! The rule(s) you show are triggered on Work Item Created, and that trigger (and others) can have intermittent timing problems. The challenge is the rule can start running before all data is available and the work item is in a stable state. As your rule worked in the past,…

Please post the following to provide more context for this symptom: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete rule in a single image file * images of each trigger, action, branch, and condition * an image of the audit log details showing the rule execution (with…

Hi @Tyler Myalls Without seeing the details of your automation rule...if the trigger is Field Value Changed for the Request Participant, you could try using the field change smart value for the added values only: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange-- A couple of…

Hi @revanth.athreya What you describe cannot be done with one rule... Automations rules trigger and run in response to an event. They do not start based on one event (e.g., work item created) and continue to run for days / weeks. Please review the documentation for the Scheduled Trigger and JQL as you could write a JQL…

Hi @Daniel Shukrun Some of the planning (and other fields) are not shown in the Edit Issue action dropdown list. Instead you may try to set them using advanced edit with JSON: https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html I recommend first reading the section on "Supported…

Hi @arndt_haas -- Welcome to the Atlassian Community! Although the built-in work item history shows the before and after for most field changes, it will not show in the change markup format you have described. (i.e., with strikethrough and highlighting) Perhaps investigate the Atlassian marketplace for any apps / addons…

Hi @Rasa These two documentation pages may help with your rule: Finding the smart values (or custom field ID) for a field: https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html Using the bulk-handing, plural {{issues}} smart value in a…

Thanks for that information, and... The log you show does not match the rule images. Please note the differences in the Page branch criteria versus what the log shows. Did you change the branch just for testing it? Regardless of that... I created a new test rule very similar to yours and I got the same result: With a CQL…

Thanks for the rule image as that explains the problem: When a condition is not met, a rule stops processing. When you want multiple different conditions to be checked AND the rule to continue for each, please use the if / else block with the conditions. For example: * trigger: work item transitioned * if / else block with…

Hi @Daniel Shukrun I believe the planning smart values are text and not date (or date / time) types when used in rules. They must be converted with the toDate function before using the diff() function:…

Hi @Nathan Hutchins First, I do not believe there is a REST API endpoint to get all the versions for all of the projects. Instead, you may get all the versions for a single project, and that is the endpoint you appear to be using:…

Thanks for the updated rule image, and that seems to support try adding the orderBy parameter to the Send Web Request actions, and then getting the last one from the list / responses returned. Remember to add the parameters you are using in the same ordering shown in the documentation: * orderBy * query * status

Unless your site was originally converted to Cloud from a Server / Data Center one, I am out of ideas for this one. Please work with your Jira Site Admin to submit a ticket to Atlassian Support as they may see something we are missing: https://support.atlassian.com/contact/#/ When you hear back from them, please post what…

Hi @Vinícius Pereira This is a fairly common scenario to sum a field (or find the maximum value) for child issues of an Epic. The key is using the Lookup Issues Action with JQL to gather the child issues and find the maximum due date from there: {{lookupIssues.duedate.max}} I recommend reviewing the documentation on…

Hi, Heather! Without seeing your current / most recent rule... If you are using the REST API endpoint to get the versions, there is an orderBy parameter which could be used to sort by the releaseDate. With that, the specific one could be grabbed using the .last list function.

Awesome; I am glad to learn that helped! Sadly, that "blue banner" you show above is likely an "Info panel" macro, and the macros cannot be added with plain text edits in rule actions. You could try a more advanced edit using Atlassian Document Format (ADF), and that will require updating the field using the Send Web…

Please try adding "ASC" or "DESC", as needed for your query, because as the documentation notes for ORDER BY when neither is specified: By default, the field's own sorting order will be used. You can override this by specifying ascending order ("asc") or descending order ("desc").

Hi @VVC What you describe is not possible with automation rules using branches as they execute in parallel / asynchronously, and so one could not loop through them in a defined order. There are open suggestions to make the processing configurable, at least for Jira Cloud automation. The only way I know to do this for an…

Hi @Jessica Carl and @John Funk FYI... The Work Item Created trigger (formerly called "issue created") can fire so quickly that some data may not be available to the rule yet. Indeed, the work item may be in an unstable / poorly defined state. This can cause conditions to not match and intermittent / puzzling rule errors.…

Hi @Philip Shramko The Work Item Created trigger (formerly called "issue created") can fire so quickly that some data may not be available to the rule yet. Indeed, the work item may be in an unstable / poorly defined state. This can cause conditions to not match and intermittent / puzzling rule errors. The mitigation is to…

Hi @Sairam Adla -- Welcome to the Atlassian Community! In my experience, the Send Web Request action can have timing / racetrack problems where the URL, request message, etc. might not fully evaluate fast enough when they contain smart values before they are validated and used. I recommend trying this to diagnose and…