Bill Sheboy Expert

Well done; I am glad to learn that helped!

Hi @Lucas Fyffe The replaceAll() function uses a regular expression for matching and the replace() function uses plain text. Perhaps try using just the replace() function to update the field. Or, please see the documentation for using replaceAll() with that…

Or...if this is the same user for all cases, you can do this to find their account id value one time: * perform a JQL search for issues with* assignee = type in the user's name * Jira will convert that to the account id, and then copy that value to use in your rule

Hi @Isabella Musial I do not know that answer. You may want to try posting a new question, and perhaps link back to this one if needed. Otherwise only the people following this old thread will see it to offer suggestions. Kind regards, Bill

Thanks, @Mikael Sandberg as I missed the part about the form usage :^)

Hi @Jeet Damania -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Hi @Alyn Watkins -- Welcome to the Atlassian Community! Before trying what you ask, I suggest meeting with your team's scrum master or agile coach to describe the problem you are trying to solve, and to learn some alternative approaches. That may help the team be more effective using Scrum, sprints, and story points, in…

Hi @karthur -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context…

Hi @Daniel Tomberlin As you note, you are using a checklist addon, probably from the Atlassian Marketplace: https://marketplace.atlassian.com/ Please check the documentation page for your specific addon to learn its limits. Kind regards, Bill

Hi @Harsh Please try using the user name, as shown here for Server / Data Center versions: https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html Perhaps also check the edit metadata to learn if the REST API supports removing users with rules. That is also described in that post. Kind…

Hi Mariano.Santoiano@teladochealth.com The way your rule is constructed, it will try to send an email for each issue provided by the trigger. And so I hypothesize that one, or more, of the issues have a Reporter / user that has either been deleted or deactivated in your Jira instance. You could test that by running the JQL…

What I do not know is does startOfMonth() use date/time or just date. I suspect it is date/time, and so you could try this: created < startOfMonth(-1m) That should remove 1 minute, and so move into the prior day. If that does not work, start walking back until 1 November drops off.

Hi @krunoslav_majer First, for an older thread like this, I recommend creating a new question and linking back to the older one. That will ensure the most number of people see it to help. Otherwise only the people following the old threads see them. Thanks! Without seeing the details of your rule and a sample of your text…

Hi @Dominick Marino There are several ways to do this, depending upon your rule structure. * You could set a field, add a label, etc. to indicate the branch has been created. And the rule could test for the absence of this indicator before proceeding. * You could use the Send Web Request action to call a REST API function…

Hi @Emily Perridge Thanks for the details in your question, and well done on methodically working through the cases! Problems in automation rules are often about context, so please consider also posting images of the complete rule and audit log details showing the rule execution. Without seeing those... isEmpty() is a…

I just noticed you posted an image of the edit, selecting the field from the drop-down list...and that this is a cascading, selection field. That is not supported by automation rules yet, as described in this defect: https://jira.atlassian.com/browse/AUTO-258 The work-around is to use advanced edit with JSON rather than…

Something is different, either in how you are building the queries or in your issue data changing. Please try this: * Create your basic search, and test it to return what you want * Then select "Switch to JQL" on the right-side of the page * Compare that generated JQL to what you were using as stand-alone JQL to observe…

Mart, what is the type of your custom field: single-select, multiple-select, etc.? The type of field impacts which syntax to use for the JSON edit.

Yes, that is correct a condition will be needed to handle the case of adding a reviewer. If the person is assigned to the issue, that could be checked with a related issues condition (and JQL) or using Lookup Issues to look for matches. * trigger: some trigger you are using...such as a change to the field * condition:…

I am glad to learn that helped. Please consider marking this question as "answered", as that will help others in the community with similar needs find solutions faster. Thanks!

Hi @Tharunkumar -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Hi @Pallavi Murthy -- Welcome to the Atlassian Community! If you had Jira site admin access (or could work with your site admin to help), you could create an automation rule spanning the two projects to do this. The reason this requires at least site admin access is this will be a multi-project rule. Without site admin…

Let's assume you have a single issue, and your multiple-select user field, additional reviewer. To drive the advanced branch, try using: * smart value: {{issue.yourFieldName}} * name: varReviewer Then inside of the branch, you may reference the fields as needed from the branch: {{varReviewer.emailAddress}}…

Hi @David Cleveland -- Welcome to the Atlassian Community! Did you notice your basic search is checking all projects and the View All Issues (advanced JQL) is searching for specific ones? Did you notice your basic search is including the last day of October and your advanced JQL is using created < endOfMonth(-1) and not <=…

Hi @Thai -- Welcome to the Atlassian Community! When you are on the Create Issue view, select the ... menu at the top right, Show Fields, and then deselect the ones you want to hide. Kind regards, Bill

Repeating my earlier question... Are these projects company-managed or team-managed, or one of each type? (You may find that information at the bottom-left side of the expanding area when you view a project.) I do not understand your explanation about what did not work as expected. To help understand what the rule changed…

Would you please post an image of your Create Variable action? Based on what your log is showing, that can be the only place remaining to explain this behavior. When I tested with exactly the same version name and smart value expression, this worked for me with Jira Cloud's version of automation rules. I saw you also…

Hi @Jenifer Kuntz I believe that JQL is getting the superset of what you want: any issues linked to the target issue and which have any links of that type to any issue (not just the target one). If you specifically want the issues of that type, linked to the target issue, please try this syntax: issue IN…

Hi @Tom Yan -- Welcome to the Atlassian Community! There are some extra spaces in your smart value expressions, so please try removing those. And if that does not work...I have seen this symptom in other posts, where a date field in rules is somehow returned as text. Please try adding toDate for a conversion before trying…

Hi @Leonardo Zevallos Guzman When you describe "it doesn't work for me", what do you observe happening? What changes are made to that field by the rule? Are these projects company-managed or team-managed, or one of each type? (You may find that information at the bottom-left side of the expanding area when you view a…