Bill Sheboy Expert

Based on your answers, the rule could use first approach I described with branching. For example: * trigger: field value changes * branch: on current issue* condition: the field contains "value A" * action: send the email to A's recipient * ...repeat for all of the possible values As I noted earlier, this would send an…

Hi @VVC First, here are some questions to clarify the scenario you are trying to implement: How many different email body contents are there: one to send to everyone or a different one for each recipient? When do you want to send the emails? That is, every time the field changes send an email to each selected recipient, or…

Hi @[deleted] As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Partners - Rules of Engagement…

No; please do not enable that option for all rules: "Check to allow other rule actions to trigger this rule...". By default, rules do not trigger other rules. This prevents accidental rule triggering and run-away looping / recursion. Only enable that option when you have clearly identified when a rule should be triggered…

Hi @Madhavi -- Welcome to the Atlassian Community! There are no built-in dashboard gadgets to show what you ask. Please investigate the Atlassian Marketplace for addon gadgets / apps which may help. https://marketplace.atlassian.com/ Kind regards, Bill

Hi @Artur Lemieszek -- Welcome to the Atlassian Community! I hypothesize what happens is the Scheduled trigger processes the issues found with the JQL in parallel (for improved rule performance) and this creates a "racetrack condition" where it is unknown how many issues will be found assigned as the rule proceeds.…

Hi @Ayoosh Gupta -- Welcome to the Atlassian Community! Adding to the suggestions from @Rebekka Heilmann _viadee_ ... The Approvers field is a list of values, and so a rule would need to iterate over the values to add each one using the mention syntax. For example: {{#issue.approvers}}[~accountid:{{accountId}}]{{^last}},…

Hi @Michael Landry Do you want to copy the forms from the trigger issue? If so, please change your Copy Forms action to select that option. Inside of the branch on all created issues, the "Current Issue" refers to the branched-to issue (the new one) and not the trigger one. Kind regards, Bill

Hi @Simon Chan Thank you for this information. After reviewing the documentation page you linked to, I wonder... 1) Can this feature be disabled at a site, project, and / or rule level? 2) Which rule actions will be candidates for retry attempts: all of them or specific ones? 3) The 7-day retry window seems quite long for…

First to clarify some Jira terminology, JQL (Jira Query Language) is used to search for issues and smart values are attributes of issues (and functions) used in automation rules. You seem to be confusing those terms. Next, the smart value expression you show with the convertToTimeZone() function only changes the time zone;…

I recommend first disabling the rule and investigating why the value is not storing in the Sub-task. Once that is corrected, you may return to working on the rule. Perhaps start with the issue history in the Sub-task to learn if something is clearing the field after it is set.

Hi @Vishal Gogari First, when posting automation rule questions, please also include images of the relevant actions (e.g., Edit Issue Fields) and of the audit log details showing the rule execution (with all of the areas at the right side arrows > expanded for execution). Next, you state this: Problem comes when the…

First thing, sorry I was not more clear on how to store the data. Here is the technique with a Lookup Table storing the Lookup Issues results as objects, so they can be iterated later. * action: Lookup Issues, with JQL to gather some issues * action: Create Lookup Table* name: varFirstLookupResults* key: first * value:…

Hi @Matthew -- Welcome to the Atlassian Community! Adding to the suggestions from @Tomislav Tobijas ... You could use smart value, list filtering and a math expression, or try a match() function to count the items with size. For example to count the ones ending in -M with a regular expression and match():…

Hi @Tami Dubi 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, and * an image of the audit log details showing the rule execution. Until…

Hi @Erwin Saegesser You could add conditions to your rule to check for the exceptions: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/ If that does not help, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed,…

Hi @kawsar seifudin -- Welcome to the Atlassian Community! This community is a place for people with similar interests to learn, collaborate, and support one another. To learn more, try browsing / reading the different areas, post some ideas, and see this post from Atlassian:…

My apologies if I was unclear: please also post the audit log details with the areas expanded. The recent changes to the audit log make it difficult to see what happened unless all of the areas for a log entry are expanded with the arrows > at the right side.

For that first rule execution, please expand the details on the right side with the two > areas, and then repost the image. Until we see that... The log seems to indicate either the branch found no issues or the condition was not met.

Hi @Trudy P Claspill The end of the user input smart value is missing the closing double-curly brackets. Kind regards, Bill

Hi @AJohnston I hypothesize the id values you are seeing are the internal ones representing the values. Please try using that JSON function to get the value attribute, and then replace "value" with "id" as the attribute for JSON update: {{lookupObjects.Service ID.asJsonObjectArray("value").replace("value", "id")}} If that…

That is interesting as "fields" should not be needed when the correct smart value (or custom field ID for some cases) is used. FYI -- I recommend not using automation answers suggested by chat bots as it may lead to wasting a lot of time. Such guessing tools cannot access your Jira site (even the one provided by Atlassian)…

Hi @Colton_Kosicek Here is a how-to article for calling the REST API with a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 And here is the endpoint to archive the…

Thanks for that information, and... As the log shows the source issue AR-92 is not a Bug and so the rule stopped. This is because the rule likely has single-project scope and the rule executed from an unexpected link direction. You probably were expecting FS-8656 (the Bug) to be the trigger issue. Issue Linked (and their…

Thanks for the additional information, and... Please change the branch to "most recently created issue" to access the new one. Otherwise your rule is linking the trigger issue to itself and re-assigning it to the Design Assignee. After that change and re-testing, let us know what you observe. Thanks!

Greetings! Branches cannot be nested (to add the watcher to the created subtask), and... Because branches execute in parallel and asynchronously, the watcher cannot be added with a final branch in the rule to do so. There are two possible solutions: * using the Send Web Request action inside the branch, call the REST API…

Please post images of the updated rule and of the audit log details showing the execution. For the log, remember to expand all of the areas at the right side to show the details.

Sorry, I am out of ideas on this one as I do not use JSM enough to know why that would confuse the rule's action selection. Did you try making the rule multiple-project in scope and using the built-in types? From that scope, all of the actions should be visible. If they are not, I recommend working with your Jira Site…

Hi @Elmer A That error indicates there is no issue available at that point in the rule for the branch. The reason is the trigger is on a Version and the Lookup Issues provides data and not issues. When you want to iterate over the issues in the Version, use that branch type: Issues Fixed In Version. However you seem to…

Hi @Vries, E. de (Elske) -- Welcome to the Atlassian Community! Are you using a marketplace addon / app for checklists or the built-in checklist field? If you are using a marketplace one, each is different in how they are implemented. I recommend checking the vendor's documentation for how to copy the checklist field.…