Bill Sheboy Expert

Hi @Laura Morgan No, that is not possible at this time for a team-managed project. Here is the suggestion to add that capability, which you may vote for / watch to see progress. However based on the comments to that from Atlassian in August 2022 it does not appear to be a focus area for them.…

Hi @Wouter Spaans (Planning) The smart values you want to use for this are: {{issue.sprint.startDate}} and {{issue.sprint.endDate}} Please consider when you want this to happen, such as at the start of the sprint, or some other event. That will determine the trigger for your rule. And...as an issue can be in multiple…

Hi @Lucas Anschuetz -- Welcome to the Atlassian Community! As the documentation states, with my emphasis, the "underlying implementation is based on Java's Pattern class and uses Matcher.find() to find matches." However, it does not state what is (and is not) supported by that implementation.…

It seems the challenge is still the need for nested branching (with version values and linked issues) which is not possible in rules. A possible work-around would be to do this in two rules, where one triggers the other: * First rule, triggered when the issue transitions to done, creates the versions in the other…

Yes, and...As JPD projects seem based upon team-managed projects, and those use those pesky "People" fields that have lots of rule problems, it may not yet be possible to do those notifications.

Hi @Ashish Sathyan I recommend you create a new question, and perhaps link back to this thread. That will ensure greater visibility to the community to help. When you create your question, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit…

Hi @David Friedrich As the supporting JQL would check if the issue was actually in a completed status, using the Status Category Changed Date should not be a problem...because... In my experience, having statuses with categories not matching their board layout can be problematic, for maintenance complexity, user confusion…

First thing, that description seems to indicate a sprint planning issue: bringing work into the sprint which cannot complete, due to team capacity and the handoffs of work by skill areas. Normally this can happen when unexpected work arrives to disrupt the sprint plan, and can be mitigated by creating smaller work items so…

Hi @Mindjito I recommend performing an internet search for "regular expression to find email address in text", and then try using any suggested results. And, as the regular expression and match() function behavior for rules are not fully described, I recommend testing for a variety of scenarios in your…

Hi @Fernand Ly Adding to Jack's answer, it is difficult to know the cause of looping for your rules unless you describe the scenario fully (i.e., the problem you are trying to solve), show the complete rules' images / structure, and the rule details for options. Until we know that information... Reading the documentation…

Hi @Kadhem MEJRI Can you write a JQL statement that will determine when your 3 conditions are met? If so, your rule could be triggered on an issue transition to Done, and then perform the check. For example, * trigger: issue transitioned to Done * condition: issue type is subtask * then check for your condition in a couple…

Hi @Vinutha GR Adding to the answer from @Fazila Ashraf Your rule has both a typo in the field name and the incorrect syntax to add a label with JSON. Please look here to learn how to add a label with JSON: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Labels Kind regards, Bill

Hi @Alae Riahi Are you trying to sync (i.e., copy) the newly created issues to the parent, or add the values which currently exist in the parent? I will assume you mean "sync", and so have you tried to use the "Copy from Parent" option at the right side of the field, under the ... and SET options? One more thing: the Issue…

Hi @Nicole Brückner What do you mean by "still open"? Do you mean "not done"? If so, an alternative method to what you show is to use smart value, list filtering with your math expression. For example, {{#=}}0{{#issue.subtasks}}{{#if(not(equals(status.name,"Done")))}}+{{Story points|0}}{{/}}{{/}}{{/}} How this works: * The…

Hi @Abby Foggin -- Welcome to the Atlassian Community! You may create a simple filter, only referencing those specific users of note, and then creating a board from that. For example: assignee IN ("Alice", "Bob", "Grace") ORDER BY Rank ASC For such a board, remember to always treat it as read-only, where any issue updates…

Hi @Tim Feeley -- Welcome to the Atlassian Community! Yes, that inconsistency in rules using arrays versus lists is challenging. Often the work-around is to strip off the square brackets with text functions, and then use split() and trim() to convert into a list. You do not show the details of your advanced branch values,…

Hi @TP The documentation for the Create Variable action describes it is always a string (i.e., text data type). You may find that information here: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-variable And that documentation is noted in the rule builder when using the action. Kind…

Hi @Ivan Andrieiev Please check the scheduled trigger's frequency for your rule. It is likely set differently than you planned. If that does not help, 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,…

You will need a branch for each one. When the rule uses this structure, each branch runs the code inside independently. As you are checking different custom fields to assign the issue, they need to be separated. Please note: there is a maximum of 65 steps (i.e., components) in a rule. If your case will require more than 21…

Hi @Vinutha GR You are correct that JQL cannot compare fields in a query. (It is an issue query language and not a SQL.) Your possible work-arounds for solving this depend upon how often you need it and your willingness to buy addons / do additional work: * need this one time* Using a JQL search for completed issues,…

There are couple of ways to handle that: * if your cases are related and mutually exclusive (e.g., "yes" or "no") then use an if / else condition structure * if your cases are independent (e.g. when "blue" do this, next when "apple" do that), use branching For example of case #1: * if / else condition:* condition: if Field…

Awesome; I am glad to learn that helped! The new UX is rolling out for the rule builder, and so I wonder if it "glitched" and wasn't visible for a bit. There is more dynamic content happening in the builder now, so I could see it changing the list of things, even though I have not observed that yet.

Hi @Kayleen Cucugliello You seem to have a good outline to create your automation rule. I recommend building it, testing, and if you run into challenges, post images of your rule and audit log details, describing what is not working as you expect, and the community can help. To get you started on creating your rule, please…

Hi @Jahnavi Pathak -- Welcome to the Atlassian Community! Adding to Jack's answer: You could also see this information using the built-in control chart. This report has some limitations, and I recommend trying it to see if it meets your needs.…

Interesting as I would have thought that smart value would be empty with that trigger! It appears you are using an advanced branch over {{destinationIssue}}. Please instead try selecting a branch type of: Branch rule / related issues > Destination Issue Even though the rule editor seems to indicate it only works for "Issue…

Hi @Darryl Lee and @Alexis I have been following this thread as the use case seems interesting and helpful, if it turns out to be possible :^) Darryl, on your note about "alas, this does not work", I could guess 2 possible causes: * Please note the automation rule, regular expression implementation is documented as "based…

Based on what you described, there is no way to do exactly that with the Server or Data Center versions. You could get the results of multiple queries but you cannot collate them. You could get some results and list them individually as groupings. (The reason collating is not possible is automation rule list iterators…

Hi @Toby -- Welcome to the Atlassian Community! Would you please post an image of the audit log details, showing an example when the rule does not work as expected? Until we see that... Consider that once the link is deleted, my understanding is the smart value {{destinationIssue}} no longer has meaning. Instead you could…

Hi @Valdrin Marmullakaj The JQL for your Lookup Issues action is intended to return any prior issues using your Summary format / naming convention: project = "MISLA" AND summary ~ "Produce Episode" ORDER BY summary DESC That will return any issues which contain both the words "produce" and "episode", regardless of location…

Hi @Damian de Vries First thing, I am not using the assets features of Jira, and so my suggestions are based on what I know of automation rules. With that out of the way... From what you describe, you paste information into the Description field of a Jira issue, using that to then create assets. Now you want to paste in…