Bill Sheboy Expert

Hi @Aaron Gibralter If you look at the items returned by this filter, you may find some interesting ones related to team features to vote for:…

Hi @dean.hodge After you have added the gadget and selected the filter, I believe that you can rename it to what you wish. Others agree with you that the default should be the filter name, as you can see in this suggestion/defect: https://jira.atlassian.com/browse/JRACLOUD-43937 Best regards, Bill

Bruce, I am glad that worked for you! I already submitted the ticket for Cloud for both, so you can submit the one for {{now}} for server. It appears that the size() problem is only for Cloud. Specifically for the {{now}} issue, I tested several other smart values within the scope of the iterator, and it appears that only…

The only work-around I found for open/active day count for the Scheduled Trigger's list is to: * Make a minor edit to each returned issue. For example, add a space after the description field with the edit action. * Change your calculation to use updated rather than now: {{created.diff(updated).days}} The context within…

Thanks, @Bruce MacNeil I am still experimenting with this (although in Cloud) and I believe that we have discovered two valuable things about the Scheduled Trigger, both worthy of submitting defects to support... 1) Try this in a log entry: The number of issues is: {{issues.size}} This returns 0 or 1, and in fact does not…

Hi @Lukas Kasten Epic Link does not work as a field change trigger for cloud automation yet (AUT-1264), so I am surprised to hear it is now implemented for Server. If you have a documentation source that says it should work, I recommend asking your site admin to submit that as a support ticket to Atlassian:…

Bruce, would you please post an image of your complete rule? That may help reveal where the issue is occurring. And, I suspect that because server and data center do not have LookupIssues or Create Variable, you may need to get creative to accumulate string values from a list (to build your email markup), perhaps using…

Hi @Curt Holley Have you considered using a branch with some JQL to access the epics? Perhaps pasting an image of the rule you have thus far, and note specifically what is not working, will help the community provide ideas. Thanks! Best regards, Bill

Thanks, @Brant Schroeder I did not know the BY clause would work with status CHANGED. __Bill

Removing my answer, as Brant's is correct.

Hi @Nita Brumbaugh You are correct: it is not yet possible to send a file attached to an issue or comment to an email recipient using automation rules. You can only send a link to the Jira stored copy. Here is the item to add the feature in the CodeBarrel (now part of Atlassian) backlog:…

Hi @jorgen.eriksen -- Welcome to the Atlassian Community! First thing: good idea switching on a sprint boundary as that will make tracking the impact of the change easier for the team. Making this change will not destroy your history; it will essentially reset it as the team re-learns their capacity, velocity, sizing, etc.…

Hi @Levon Saldamli Would you please describe what problem you are trying to solve? I am unclear what "sort issues into different backlogs" would mean. Thanks, and best regards, Bill

Yes, and... you may then use bulk-edit to move those issues to the new project. Best regards, Bill

Hi @Joanne Griffin -- Welcome to the Atlassian Community! This appears to be a known defect/behavior, and you can view the open defect here and mark that it also impacts your team: https://jira.atlassian.com/browse/JSWCLOUD-20936 Best regards, Bill

Thanks for clarifying. If you already have an add-on gadget for time reporting, you may want to investigate if it already has the capability to select projects by lead.

HI @Andrew Dunne You can use components to represent teams/squads and use separate boards for each within one project (backlog)... for Classic projects. You cannot do this with NextGen as that feature is modeled around the simplicity of stand-alone, autonomous teams with one project-one board. As you note, doing this for…

Hi @ASelenium You posted this question in the automation area, so you may want to also add it to the Cloud area to get a larger audience looking at it. Best regards, Bill

@Ivan Teong thanks for your response and additional thoughts. It is good to hear some of the thinking behind the decisions being made for NextGen. Often for Jira features, some of the choices seem unclear in the "what problem is being solved"/value-add area. :^) Which is why customers may be frustrated by going to the…

Hi @María Elena de León You cannot do a search (JQL) for this, but you can browse all the projects in JIRA, including the assigned leads: Projects > View All Projects Best regards, Bill

Hi @Ben Golder Have you considered inserting a Log action after the trigger and before the condition to log the value of the checklist values? That will help you diagnose if something in the values has changed, and so the condition is not being met. Best regards, Bill

Greg, sorry that I missed you were on server version. I wouldn't hold out for the server version getting that soon. Atlassian is stopping sales of that product soon (Feb 2021) and will sunset after that (Feb 2024): https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html __Bill

Hi @Bruce MacNeil -- Welcome to the Atlassian Community! You are getting that error because you are using the math operations {{#=}} with multiple smart values, but not doing math with the issue values. If you want to just do that for one issue, drop the {{#=}} and the {{/}} If you are doing that for a list of issues, such…

Hi @Guilhem Dupuy Please try to select the create button, and then look for the import issues option. Best regards, Bill

Thanks; do you mean you can see the steps after cloning in the old view but not in the new one? If so, I recommend submitting a support ticket for that because everyone is switching over to the new view, regardless of preferences, in March 2021. https://support.atlassian.com/cloud/

Hi! I have not used those products, so I do not know how they would or would not help. Rolling up (or synchronizing) status is a fairly common scenario for automation, so you can do it without other add-ons. Please see the examples and walkthroughs here:…

Hi @Ivan Teong Thanks for centralizing many of the concepts for NextGen board usage, and explaining why performance management via settings is needed for this newer product from Atlassian. Please also consider looking at some of the NextGen versus Classic project differences, and where performance may suggest switching…

Hi @Michael Crincoli One method is to never delete issues from Jira Cloud, especially given there is no "undo", and recovery from a backup is a bit of an involved process. Instead consider adding a boolean custom field to indicate "Abandoned". Then update your filters to ignore abandoned issues, keeping backlogs, boards,…

Hi @Melissa Horvath To help the community offer suggestions, would you please post an image of your rule, and note what is not working? Thanks! Best regards, Bill

Hi @Anders Baisgaard Your example with "Why" finds nothing matching exactly that: "Why". Instead you need to match on any leading or trailing characters (from your example), such as the expression ".*Why.*" Then use the split() function on the resulting group to get what you want to focus upon. (Or skip the match and go…