Bill Sheboy Expert

First thing: given some of the possible rule collisions and uncertainty in the rules shown, I recommend pausing to meet with your Jira Site Admin, explain the initial need, and ask for their help. Until that happens... I am still unclear on what the "40" represents and what problem the rule is trying to solve. That is,…

That is curious! I recall some related, recent defects for project name and key changes in the public backlog with team-managed projects. At this point, I recommend asking your Jira Site Admin to submit a ticket to Atlassian Support to take a look. You appear to be on a paid license and so the admin can do that here:…

Thanks for that information. And for the one-time update to add the label, please try the branching with CQL as Aron suggested: * trigger: scheduled * branch (on related entities): enter your CQL expression to find the pages* title ~ "app name" AND type="page" AND label NOT IN (name-of-app) * action: add the label You…

Thank you for that information; setting those dates to help with timelines / roadmaps is a common need. Please post the images I noted as they will provide context for the community to offer suggestions.

Hi @Ahmud Auleear Thanks for your follow-up notes. For automation rules, this change essentially means any "Short Text" fields become "Single-line, Rich Text" ones, and that dramatically alters rule condition checks, message handling, field updates, etc. (as I described earlier). The change could thus cause rules to fail…

FYI -- I just found another documentation page for the new features, well-hidden under "key concepts" section :^) https://support.atlassian.com/cloud-automation/docs/configure-automation-rule-groups/

Hi @Julie Mason -- Welcome to the Atlassian Community! One way to do that is to search the exported JSON for all the rules: * ask your Jira Site Admin to export all of the rules from the global rule list * identify the ID value for the Project Role (or the name) * load the JSON in an editor (preferably one that can format…

Hi @Lex Baldridge Yes, and...to Trudy's suggestions: The Start Date field is date only and Created is date / time, so please use a format to match: {{issue.created.jiraDate}} And...as there are known timing problems with the Work Item Created trigger that could cause the condition to fail incorrectly, I recommend adding a…

That JQL function is from an addon / app, and thus I do not know if it works inside of automation rules for Jira Data Center. As an alternative, you may use built-in JQL features. Assuming the trigger issue is a subtask, that would be this to find the sibling subtasks with the same parent for the lookup: parent =…

Yes, that is what I suggested, and...it requires adding a Re-fetch Work Item Data after the edit so the condition gets the updated information.

Do you mean you are using this product: https://marketplace.atlassian.com/apps/1215277/smart-checklist-for-jira-free?hosting=cloud&tab=support If that vendor is the app you are using, please see the examples in their documentation to learn how to parse / split the values for checking:…

Would you please post images of your updated, complete rule and the audit log details showing the execution? Thanks!

Hi @Jamshaid Are you trying to merge the logic of the rules into one single rule, and / or... Are you trying to use three rules to span all of the possible 40 projects, or... Something else? And, what are the types of your projects: company-managed, team-managed, JPD, etc.? That will impact what can be done and how any…

Hi @melanie_boehmer I do not believe the Scheduled trigger for Confluence rules references any pages, and so the rule condition would find nothing. When do you want to run this rule, such as when a page is created or edited? Kind regards, Bill

Hi @Sophia Isabella -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * for Cloud, 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 *…

Hi @pawarsachin84 What is the source of your information? There is no "branch: lookup user" and the User Condition cannot access a smart value, such as from the changelog. Kind regards, Bill

Hi @Gal Fatal There are currently only two ways to do what you ask: * User Condition and a Custom Field* with the changelog entry, save the previous value in a single-select, user custom field * use a Re-fetch the Work Item Data action to reload the update * use a User Condition to test the custom field value is in your…

Hi @Benjamin Črnjak There is currently almost no documentation on these new features for Premium and Enterprise license levels, including this page and article: * https://support.atlassian.com/cloud-automation/docs/advanced-automation-components/ *…

Without knowing how the status change is happening, I am guessing what to suggest next. That is why I asked that question earlier. Again for checking a Rank change, please try writing the entire {{changelog}} smart value to the log and that will show what changes, and may be checked. Although that may not help your case as…

Hi @Rovmenpaul -- Welcome to the Atlassian Community! 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 rule details…

The JQL for your Lookup Work Items action is incorrect and does not match the earlier suggestion. Please use this and then re-test: key = {{issue.parent.key}} And, that list of other cases were not questions: they are other possible cases to cover if you want them with additional rules. Given the number of rules you may…

For more context, please show: * an image of your complete rule in one continuous image for continuity * an image of the rule action and smart value expression that is not working as expected * an image of the audit log details for the rule execution, with all the areas at the right side expanded Thanks!

First, lists do not use an array syntax such as you show with: issue.checklists["Severity 1 / Critical"] They have a get() function, but that will not help unless the checklists field is a list and you know the number index to access:…

Hi @PLaksh11 Yes, and...to the suggestions from @John Funk We need to see the details of your rule and option selections to provide specific suggestions. Until we see those, if your different option values indeed follow a pattern as you describe, please see this article for how to remove values from on list using the…

Hi @Puneet Gupta As others have suggested, temporarily changing the trigger from Manual to Scheduled might help, with these constraints: * Your current rule cannot have any user inputs in the Manual trigger * What your rule does / changes in work items can be identified using a JQL expression* For example, let's assume…

Greetings, Community Managers! This is a duplicate post of the same article posted yesterday here: https://community.atlassian.com/forums/Automation-articles/Unlock-Advanced-Workflow-Orchestration-With-These-New/ba-p/3057396 Please remove this article as it will dilute the focus and feedback from community members. Thank…

Hi @marty_chang -- Welcome to the Atlassian Community! Have you tried using the first agent, and storing the results from the response smart value as plain text with Create Variable (or as an object using Create Lookup Table), then using a second agent, and finally combining / using your results together in the comment?…

Hi @Manjinder Kumar -- Welcome to the Atlassian Community! What have you tried 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 * for Cloud, what type of…

Yes, and...the first I learned about it was when I saw new defects in the public backlog for the features: https://jira.atlassian.com/issues/?jql=project%20%3D%20AUTO%20AND%20component%20%3D%20%22Advanced%20Component%22

Hi @Deivid Araujo Those are new features for Premium and Enterprise license levels, announced in this article a couple of days ago: https://community.atlassian.com/forums/Automation-articles/Unlock-Advanced-Workflow-Orchestration-With-These-New/ba-p/3057396 Hopefully they will soon add more information to the documentation…