Bill Sheboy Expert

Hi @Brandi Myers-Shank Adding to Mikael's answer: To whom are you sending this notification? I ask that question because if you are sending this just to yourself, you may want one email that day, versus an email for each issue. Similarly if you are sending emails to assignees, they may want to only see their issues, not…

Hi @Carol Wesolowski First thing, I am not using the Deep Clone addon, and so my suggestion is based on what I know about automation rules. With that disclaimer out of the way... Based on what you show, it appears that addon does what I expect: it uses the REST API to clone the issue, and sub-tasks, one after…

Hi @Dee Minty Adding to Benjamin's answer... For a rule like this, consider adding a condition to check if the parent issue is not already in a Done status in your branch. Given the upcoming changes to rule execution limits, that will reduce the "count" if the transition is not needed. Kind regards, Bill

Hi @Breanna Williams Adding to Michel's answer... How do you know the tickets XYZ and ABC are related? Michel was demonstrating a relationship with issue links. If you have another manner, for example with other issue fields, you could do this with a JQL branch. Kind regards, Bill

Hi @victoria.morrison -- Welcome to the Atlassian Community! I cannot quite see the details in your rule image, but I wonder: are the quotation marks correct in your CQL? Perhaps try this instead, confirming that the quotation marks are not the curled ones: title ~ "Playbook" You could also try using {{page.title}} with an…

Hi @Osama Al-Areky Without seeing the design of the rules, were you intending the actions of one rule to trigger the other, is that an error, or do they happen to have the same trigger? If you did not intend one rule to trigger the other, please check if you have incorrectly enabled the "Allow Rule Trigger" option for one…

Hi @Stanley Duback FYI components in rules do not necessarily happen in the order defined in the rule...for example: Branches which could be on more than one thing are executed in parallel and asynchronously. There is no guarantee of when such branches will complete, up to the last step of the rule. And for the Send Web…

Two things to try... If that field in the response is text, and not structured, after using the split there is no {{body}} attribute: only text. In that case, please replace that {{body}} with {{.}} as that is the generic way of returning whatever value the iterator is returning.…

Thanks for that information. Based on the audit log, the field appears to already be a list in the response. Please try removing the split(",") to observe what happens. And, as you appear to be creating a URL, you may want to add the trim() function if you observe any extra…

Please try creating the JQL first, perhaps using the date functions like startOfWeek(): https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#startOfWeek-- With that you could use a scheduled trigger rule to run weekly. To get you started on creating your rule, please refer to these documentation and…

Yes, that is correct. All that information about link direction is in the smart values for each stored link. When lower down in inward and outward sections, knowing where you are (relative to the starting issue) is key.

Hi @Sean Pendleton Although it is possible to "move" an issue from one project to another with an automation rule, I would discourage doing that due to the possibility of errors. Projects have different configurations, issue types, workflows, etc. This is why Atlassian provided a specific feature to move an issue,…

Hi @Maria Fernanda Costa de Melo What problem are you trying to solve by doing this? Knowing that may help the community to offer better suggestions. Thanks! Until we know that... What do you mean by a "summary of the previous week's activities"? If you mean a list of any issues created or changed, you could create a JQL…

Hi @Vishal Biyani Are you using Jira Cloud or Jira Server / Data Center? I ask because Jira Cloud's Lookup Issues action has supported all issue fields, including original estimate, for several years. However for Jira Server / Data Center, the Lookup Issues action was only recently added, and I believe it does not yet…

Hi @Lali The support team was correct that there is nothing built-in for Jira to sum values across all the issue type levels. Instead automation rules may be used to do this. The original estimate is one of the fields in the {{timetracking}} smart value of issues. You may use the Lookup Issues action to gather your issues…

Would you please show an image of your current, complete rule, in one image? That may provide some context. (When the rule is longer, a screen capture or browser addon for scrolling capture can help to do that.) Thanks!

Hi @Mane Zakaryan 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 for the community to offer ideas.…

Hi @CEDRIC DEVAUX Adding to Mohamed's answer... As you are using a text value (either from the changelog or the variable), it must first be converted to a date type before using it. For example: {{estimation.toDate}} And if that does not work, you may need to parse the field with text functions to get the conversion to…

Hi @Alex Blanes -- Welcome to the Atlassian Community! You do not show your entire board image, but I believe I see there is another column to the right side. If this is a Scrum board, issues are considered completed when they are in the column at the right side of the board. (The status category is not relevant for the…

Hi @Man Dao -- Welcome to the Atlassian Community! I am confused by what you ask: wouldn't a "Dev estimate" come from the developers doing the work? If you mean something else, would you please clarify and provide more details? Thanks! Kind regards, Bill

Hi @Silvia.Tircolea -- Welcome to the Atlassian Community! I believe that depends upon the behavior of the "different programs" you note. For example, if you had an automated testing tool which was integrated with Jira, it might create Jira issues by calling the REST API functions. Please consider checking the…

Hi @Jenni I believe this is not possible at this time. If you search in this community you will find other posts asking this question, and although the URL of an attachment can be provided for download (via automation rules or the REST API) it cannot be displayed in things like emails, messages, etc. I recommend also…

Hi @Kate Cook -- Welcome to the Atlassian Community! Adding to Valerie's answer... Depending upon the specifics of your scenario, this may or may not be possible with automation rules. If you provide a specific example of "before" and "after", the community can offer ideas. Until then... You describe the behavior of a tool…

Hi @sadhana.chittibabu 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 for the community to offer…

Hi @Raymond_Gorbea What problem are you trying to solve by doing this? That is, "why" do this, and "how" would your teams act differently if they had this information now? Knowing that may help the community to suggest solution approaches to what you ask. Thanks! Kind regards, Bill

Hi @Seyyid ÇIRAK -- Welcome to the Atlassian Community! Please try using the "contains regular expression" rather than "contains", and use this as your second value: (x|y|z) Kind regards, Bill

Hi @Daniel Flores -- Welcome to the Atlassian Community! First thing, you note using automation rules to set a default / template for a field. Automation rules run (i.e. trigger) after something has happened, such as issue create. They cannot be used to create a field template. To do that, please change your instance field…

Hi @Professional Service Manager Based upon this automated translation of your question: I'm trying to create an email trigger automation using the custom fields in my task, but I don't know how to fill in this field. {{issue.[Customer Field].name}} I know the field ID, and I've already tested it in different formats…

Hi @Vera Salmina -- Welcome to the Atlassian Community! From what you describe, I wonder if there is another automation rule performing that action. When you look at an example issue showing this symptom, and review the issue's change history, who (or what) does it indicate is changing the linking? And if you look at the…

Hi @Abhay Kulkarni Have you tried updating your JQL, to add the status condition, and remove the condition from the rule? For example: project = yourProjectName AND "Start date[Date]" <= startOfDay(7d) AND status = "Archive" Then the rule will only run when there are issues to process. Kind regards, Bill