Bill Sheboy Expert

Hi @Scott Buratt Yes, and...to Trudy's suggestion: I am hypothesizing you asked about this rule due to a migration from a Team-managed to a Company-managed project. In that case, rules can only process up to 100 issues at a time; that is the limit for automation rule processing (for branches, triggers, and lookup issues).…

Yes, and...after you get the people to subscribe to the filter :^)

Awesome! I am glad to learn that helped. Please consider marking this question as answered. That may help others in the community with similar needs find solutions faster. Thanks!

Yes, and... I believe the requestor asked the same question in this other thread, where I also answered: https://community.atlassian.com/t5/Automation-questions/Re-Re-1-Notification-per-assignee-via-Automation-on-Jira/qaq-p/2092384/comment-id/4502#M4502

Hi @vdhanorkar Your use case is different as there could potentially be multiple different assignees. As a result you need a different rule, as what you posted references only the first assignee from the lookup issues result. One possible way to do that is: * trigger: scheduled * action: lookup issues with JQL * condition:…

Hi @A A Ron Geister _Trundl_ and @Alexander Pappert As someone who has personally experienced this for a community account change, my observations were somethings migrated and others did not: * it appears history, badges, watches, groups, and profile details moved * it appears kudos-related stuff all resets to 0...leading…

Hi @Shonda -- Welcome to the Atlassian Community! Yes, and...to Nic's ideas: What problem are you trying to solve by doing that? Knowing that may help the community to offer you suggestions. Thanks! Kind regards, Bill

Hi @Daniela Guimaraes -- Welcome to the Atlassian Community! You could try using an Automation for Jira rule, triggered on issue-commented, and post the same comment in the Slack thread. To get you started on creating your rule, please review this documentation and examples: *…

Hi @Fawzi Alkayall -- Welcome to the Atlassian Community! As Craig noted, that is not possible. In my opinion, Atlassian's interpretation of a "Cumulative Flow Diagram" is not accurate or helpful unless you have a very basic workflow of To-Do > In-Progress > Done. If you have something more advanced please consider…

Smart values are case-sensitive and spacing-sensitive; when you have an incorrect one, it just returns null. To check that, you can use this how-to article. Basically, you are calling the REST API for an example issue with a browser, finding your field, and checking the smart value:…

Awesome; you have definitely found a bug. I recommend working with your site admin to submit the defect here: https://support.atlassian.com/contact/#/ I was able to reproduce this symptom as follows: Steps to reproduce: * create a manually triggered rule, with a single action to add a comment with some text, such as "Here…

I believe that is from the template stuff in the "More options" section. Unless you need the JSON edit, clear everything in that "Additional fields" area, collapse "More options", and then publish/re-test your rule.

Hi @Hadas and @Vikrant Yadav For automation text replacement, you noted the case of "*Expected*" exists and the search/replace makes it "**Expected**" In my experience...I find some things in the Java Pattern specification for regular expressions are not supported in the automation rule implementation. So a work-around for…

Hi @Phil Middlemass -- Welcome to the Atlassian Community! Yes, and...I'd like to see the same thing (formulas) for filters in views in Jira Product Discovery. The only work-around I can think of is adding custom fields solely for the purpose of filtering, and setting the values with automation rules. Kind regards, Bill

Hi @Paisley Greer -- Welcome to the Atlassian Community! Adding to Fabian's answer... It may not be obvious how to enter the smart value for the fields with drop-downs. To do this: * type in (or paste in) the smart value expression * and it will appear below the field * when it does, select it and the expression will be…

I have not tried that, although I recall some posts about making fields that can only be set through automated rather than manual changes. If you do not need to see the field Risk Score, you could either eliminate it (using one rule) or use an entity property to conceal it. Alternatively to keep the Risk Score…

Hi @Lukas You seem to have 2 rules, one which makes field changes that could trigger the other rule. By default, automation prevents that to avoid errors/run-away rules. You can enable this for the second rule by looking in the details at the top and enabling the option "Allow Rule Trigger". Kind regards, Bill

When you create the variable, you can just type in the number value for the Sprint ID. Then later use that variable's name in the issue edit.

Yes, that is correct.

Hi @Charles Cardwell What type of project is this: company-managed or team-managed? Team-managed projects do not use the Epic Name field, and I believe that the field is being deprecated for company-managed projects this year...although it may still work currently. Kind regards, Bill

Hi @Pavel Dvořák I found this suggestion to add the option to sort, and comments in it for adding a "default sort" for issues in an epic: https://jira.atlassian.com/browse/JRACLOUD-78353 However I did not find a specific suggestion to make a default sort, so perhaps add a suggestion for your idea. Thanks! Kind regards, Bill

Hi @Jakub -- Welcome to the Atlassian Community! I do not believe that is possible with out-of-the-box features. There may be something available in the marketplace addons to support this. Kind regards, Bill

Thanks for that information; so the short answer is changing the order is not possible. For team-managed projects, I do not believe it is possible yet to set a board filter. The default is currently ORDER BY Rank ASC so that drag-and-drop prioritization works.

Hi @Philipp Hagen The built-in feature of automation rules could help with that as it has a Sprint Completed trigger. To get you started on creating your rule, please review this documentation and examples: * https://www.atlassian.com/software/jira/guides/expand-jira/automation *…

Let's first confirm: is this a company-managed project or a team-managed project? You can see that information at the bottom of the left-expand area. If this is a company-managed project, you must be a project admin to change the filter. That can be accessed from the top right of the view, under the ... menu > board…

Hi @Dylan Alperin -- Welcome to the Atlassian Community! The option to prevent duplicates detects if the comment text (body) is exactly the same. Does that match your use case? If not, you will need another way to detect duplicates, such as: * check if the previous value of the assignee was empty with an Advanced Compare…

Hi @Neil Kugelman -- Welcome to the Atlassian Community! A Jira board is a view of the issues in the project, selected using a Jira Query Language (JQL) filter. The board also has different Status values mapped to the columns shown on the board. The filter usually has an ORDER BY clause to sort the issues. Issues on the…

Hi @Rna Ali -- Welcome to the Atlassian Community! Are you asking about saved Jira Query Language (JQL) filters? * If so, you may find the ones you have access to see from the top navigation bar with Filters > View All Filters * If you mean something else with your question, please clarify what you are asking. Thank you.…

Hi @Gail Two things to help... If that "Bugs" sprint will always be used this way, and so have the same Sprint ID value, you could use Create Variable to hold the value of the ID. And then to use it in the rule... For the Edit Issue action, you can type smart values into the field. To use them, the steps are not obvious: *…

Agreeing with you: there are lots of opportunities to improve the admin functions in this and the audit logging areas.