Bill Sheboy Expert

Hi @John Tucci For a question like this, please post an image of your complete automation rule(s), 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.…

Thanks for that information, Deb. Perhaps try the three automation rules I described, where the third one can send the notifications of add / remove scope.

Hi @Lee Street The answer depends upon what type of project you are using and what you mean by "cycle time". For company-managed projects, there is a built-in, Atlassian interpretation of a control chart which can show Lead Time and "cycle time" for the selected status values, and other criteria. In my opinion, that chart…

Hi @Deb Keene What problem are you solving with notification of changes to the Sprint field? That is, "why" do this? Until we know that... The first two things on your list are already on the sprint report for company-managed projects as scope changes: issues added to or removed from an in-progress…

Hi @alex_h -- Welcome to the Atlassian Community! First, a couple of suggestions around what you are trying to do... Please consider the idea of "estimate size; derive duration" (originally from Mike Cohn, I recall.) Capturing the sizing forecast may help to create a delivery plan for a duration forecast. And so preserving…

Hi @vincenzo.spatafora For this scenario, you could branch on JQL to the specific issue, using the key, rather than branching on all of the subtasks. Kind regards, Bill

Awesome; I am glad to learn that helped! For learning, I recommend lots of experimentation in test projects...writing things to the audit log, and reading community posts. Those help fill in the gaps from the documentation.

Hi @Gisela Lassahn Please try using the Issue Linked trigger and testing these smart values with Issue Field and Advanced Compare conditions: {{destinationIssue}}} {{linkType}} https://confluence.atlassian.com/automation/jira-automation-triggers-993924804.html#Jiraautomationtriggers-issuelinkedIssuelinked Kind regards, Bill

Hi @Julian Gonser -- Welcome to the Atlassian Community! I am glad to learn Stephen's suggestion helped. And, you described this in your question: I have already read various online tutorials and also the official documentation of Jira. Unfortunately, these documents always have an older version than our Jira. Which…

Hi @Gisela Lassahn If I understand your question, the JQL statement you show is not valid. JQL statements have this syntax: some_issue_field OPERATOR some_value For example: project IN (ABC, DEF) Instead you are trying this: some_value OPERATOR some_other_value For example: ABC IN (DEF) And so there are no issue fields…

Hi @Jacob Kock Plinius You may do this copy in one rule, with two branches: one to the parent issue followed by one to the sibling subtasks (using JQL to find subtasks which have the same parent as the trigger issue). I encourage you to try to create the rule; that will help confirm it does what you need and improve your…

Almost...there is no need for the quotation marks around the name or the extra curly brackets. {{assignTable.get(fullName)}}

You can see the open items and try adding a suggestion here: https://jira.atlassian.com/secure/Dashboard.jspa I am on a free license, and so cannot create new suggestions or I would add it :^) To submit it as a defect, work with your Jira Site Admin to submit a support ticket here: https://support.atlassian.com/contact/#/

Yes, this is a GDPR change impact. For Jira Cloud, I believe the current options are: * long list of if / else conditions, limited to the maximum rule length of 65 components * lookup table, limited to 200 entries for a table * using the Send Web Request action, call the REST API user search to get the user's account ID…

Hi @Couthaïer FARFRA 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…

If the Tasks are in fact children of the Epic, that rule should work. Have you confirmed the Tasks have the same Epic as their parent? If it does not work for a specific Task, please post: * an image of your complete automation rule (in one image) and * an image of the audit log details showing the rule execution. Those…

Hi @Bruno Xavier That error message is telling you the rule uses actions / conditions to access issues, but none are available. This is a common error message when using the Scheduled Trigger without any JQL to feed it issues. Do you have defined criteria (e.g., a JQL statement) to find the issues you want to process each…

Hi @Lucas Ferreira Unless something was fixed recently, that may not be possible from an automation rule in Jira Cloud without some workarounds...I spent a bit of time on this more than a year ago and here is what I learned: There are known defects where the changelog for list fields like Sprint, Fix Version, etc. are not…

Hi @Ben Hart Are you trying to assign the issue using the user name with a Jira Cloud automation rule? If so, that is not possible: the rule will need to use the account ID value for the user. To get the account ID from the user name, the rule would need to call the REST API user search function using the Send Web Request…

A person's Jira user account must have at least project admin permissions to create / manage automation rules. With that, they may navigate from the left-panel > project settings > automation If you do not see that option, you are not a project admin. Please ask your project admin for help. When creating a rule, there is a…

When using the clone issue action in a rule, you may select specific fields to set rather than be copied. Leaving the field empty will clear it.

Hi @Bud Herz I tried that and replicated your results for a company-managed project. What appears to be happening is the built-in CFD's Refine Report options for Swim lanes filtering matches any saved queries for the board's swim-lanes-by-queries, regardless of the current swim lane option selected for the board. I did not…

Hi @Vineela Durbha Adding to Kalyan's suggestions... Would you please post an image of your complete automation rule and an image of the Clone Issue action? Those will provide context to compare what you are describing to what was suggested. Thanks! Kind regards, Bill

Certainly; it is essentially what I described: * trigger: sprint started * branch: to issues in sprint* edit issue: selecting the Labels field, the option for ADD / REMOVE on the right side, and entering your value to remove

Hi @Rees, Ian My understanding is by default, automation rules with an issue in the trigger then remove that issue in any branching. That is, the rule engine explicitly adds this to your JQL behind the scenes. This is likely to prevent looping errors. AND key != {{triggerIssue.key}} One way to observe this is to…

Hi @Lucas Ferreira I suggest ignoring the label for issues removed from the active sprint...until a new sprint starts. That will enable the team to review what happened during the sprint in your retrospective, and more easily see potential improvement opportunities. Then create a new automation rule, triggered on Sprint…

Please post an image of your complete rule and audit log details showing the rule execution. Those will provide context to help with suggestions. Thanks! Until we see that... The scheduled trigger is the easy part: just pick your frequency. But, you do not describe for which issues you want to add subtasks. If the issues…

Hi @Manoj Kumar Gangwar That is not the correct syntax for accessing a list of values with smart values in Atlassian automation rules. Please look here to learn more in the automation documentation: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#list.get-index- Kind regards, Bill

Hi @Iana You may split the description into a list using the newline character, and then use the get() function to access the values. The first item in the list has an index of 0, and so this would work: {{issue.description.split("\n").get(0)}} To learn more about these functions, please look here: *…

Hi @Mohit Jain This question seems closely related to, or a duplicate of, you other question: https://community.atlassian.com/t5/Jira-questions/Jira-automation-rule-to-consolidate-comments-from-task-to-epic/qaq-p/2686900 If that is the case, please close one of them to focus the community's suggestions. Thank you! Kind…