Bill Sheboy Expert

Are you trying to have one Subtask with a Summary of "check data quality - prices" or multiple Subtasks with that Summary (with one for each attempt to perform the check)? When a Subtask moves to the status "ADJUSTMENT NEEDED", what happens to that subtask next: * is it considered "completed" or * does it move back to some…

Hi @Walter Buggenhout ! Yes, and...a caveat for using only one field: I believe both fields are updated when the Parent is changed. For automation rules, I just confirmed the Parent field is not fully integrated for changelog handling. This means the Epic Link must still be used for some scenarios in automation rules when…

First, as you note being the global Jira admin for your company, I strongly encourage you to learn more about writing and maintaining automation rules. As your colleagues use the tool, they will need your support and you will want to ensure they do not cause harm to the site via rules. Perhaps seek additional training from…

Hi @Jira user(public) Based on this post in the developer community, with some input from Atlassian staff, that is not possible: https://community.developer.atlassian.com/t/source-of-update/2395 Although they do suggest a curious workaround by supplementing the data passed by a REST API endpoint using entity properties.…

Hi @Massaut For a summing scenario like this, there are several cases to consider. Please consider and decide which ones you want rules to cover them, such as the following: * When an issue is created and assigned to an epic at the same time * When an issue is updated and assigned to an epic for the first time * When an…

Greetings, and have caution when using card covers on boards with many issues with cover images as there are known performance problems with caching the images: https://jira.atlassian.com/browse/JSWCLOUD-25553 Kind regards, Bill

Hi @Davide Orbitello Yes, and...to Walter's suggestions: Are you trying to find an exact match of the summary of the two subtasks? If so, why are there two subtasks with the same summary as that would imply they are the same work item? Regardless of the answer to that, let's slightly adjust the JQL with the CONTAINS ~…

Hi @sandeepkudale -- Welcome to the Atlassian Community! First thing: this is an older thread, and so I recommend creating a new question. That will ensure the maximum number of people see it to offer suggestions. Back to your question... You have created a rule with a Scheduled Trigger, using JQL which is checking the…

Greetings! Manoj, this was not David's question for which to accept an answer. It is from someone else, posted about a year and a-half ago...and so the answer should not be accepted without their input. (Others in the community farm / troll older questions just to earn "points", apparently asking other community leaders to…

Hi @Quinn Wood -- Welcome to the Atlassian Community! Context is important for automation rule questions. Please post an image of your complete rule, an image of the Send Web Request action, and an image of the audit log details showing your rule execution. And, where are you observing errors: when creating the rule, when…

Hi @Gene Sullivant 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.…

Thank you for the additional information. The rule Lisa showed will update the issues assigned to the version when the version itself is updated, not the issues. And so there are multiple scenarios to handle, and you may decide which scenarios (and rules) are needed. Here are the ones I can think of to start (ignoring edge…

Hi @Karthikeyan Rajendran -- Welcome to the Atlassian Community! That is not possible. Here are a couple of suggestions to add that feature: https://jira.atlassian.com/browse/JSWSERVER-16396 https://jira.atlassian.com/browse/JSWCLOUD-17610 A workaround could be to change the story's Summary to include the due date so it…

Hi @Rayane Pontes Batista You could create an automation rule with a Scheduled Trigger, with JQL to find issues with a Due Date in the past and which are not flagged. Then add an action to set the Flagged field. To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @Cyril Philemon The scenario you describe is similar to one for Jira issues handling, and here is a how-to article to send one email per assignee: https://confluence.atlassian.com/jirakb/automation-to-send-email-only-once-per-assignee-1310985609.html For your purpose, I believe the rule could use a page lookup (rather…

Hi @Urmo With the JQL startOfYear() function, you may increment the value to match your quarters. For example this query would find issues due during the third quarter of this year. Please note well the use of >= and < to be within the range. project = yourProjectName AND duedate >= startOfYear("+6M") AND duedate <…

Hi @Boluwatife Adewole First thing, I am not using Figma and thus my suggestions are based on what I know about automation rules. So please test anything suggested. With that out of the way... I did not find any suggestions in the public backlog to add Figma (or other design tools) information for cloning. And the built-in…

Hi @Sally Sattary When the Sprint Created trigger fires, there are no issues in it yet. And so the branch you show will not find any yet. You describe wanting to add some default issues to the sprint when it is created. Your rule could be changed to the following to accomplish that: * trigger: sprint created * action:…

Are these issues in different projects? If so, the rule will need to have multiple-project scope, which is selected in the rule details at the top. Your Jira Site Admin will need to make that change to the rule in the global rule settings.

Thanks for that additional information, Erika. You are using Tempo Timesheets, and I do not have experience with that product. My understanding is the rule will need to call the Tempo REST API to get the data you want using the Send Web Request action. Please see this documentation page from Tempo for more information on…

First thing, I recommend not using any bots to answer questions for Jira automation rules. Unless you enter all of the context / configuration info for your Jira instance, any suggestions provided may lead you to waste time trying things that could not possibly work for your own Jira site. Instead it is better to learn the…

There is no such action to do exactly your scenario. The key is identifying the "target" issue in "Project B" to update. Instead it could be something like this: * trigger: issue field changes for Release Date * condition: project is your "Project A" * branch: somehow branch to the issue in "Project B" (e.g., with links,…

Hi @Angel How is the "custom notification" URL implemented? Is it from a marketplace addon / application, which perhaps already has the ability to perform such linked actions, or from some other mechanism? Kind regards, Bill

Hi @JD That may be possible when: * your rule has at least multiple-project scope in order to access issues in both projects * the Description field has a format / structure which allows parsing to find and update the information from the other issue The rule would be triggered on a change to your field(s), test if the…

Hi @Valeriia_Havrylenko_SaaSJet 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 Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Jh The log shows the condition was not met as an incorrect smart value was used...to access the parent of the cascade field, just use value: {{issue.customfield10243.value}} The child reference you use is correct: {{issue.customfield10243.child.value}} I recommend using this how-to article as it may help to review the…

Hi @Erika Pranka If I understand your question, you want to identify the user who logged work for an issue using an automation rule. When the rule is triggered on Work Logged, the person doing so would be this smart value: user who logged this work: {{worklog.updateAuthor.displayName}} If instead you have an issue which…

Hi @Hector Eduardo Calzada Tenorio How are you setting the value of "Available_Days_Field"? If you already have an automation rule doing that, you likely have used the date / time diff() function to compute the value: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference---…

Max, where do you see a sprint on that Kanban board's backlog view?

Hi @Julia Golub -- Welcome to the Atlassian Community! For Jira's implementation of a Kanban board, the left-most column is the "not started yet" area, and when the Backlog is also in use, both appear in the Backlog view. Your possible options similar to what you asked are: * when in the backlog view, collapse the Selected…