Bill Sheboy Expert

Hi @fatma_lejmi When you note the rule has permission to work on multiple projects, what do you mean? Are you using any security schemes for your projects, as that could lead to the symptom you see, as described in this defect: https://jira.atlassian.com/browse/AUTO-404 And, the audit log is showing an error which does not…

Hi @Soluciones TIC I do not believe that is supported with the built-in date/time handling. And I did a quick test to see if automation's format() function could handle the locale parameter with Local.getDefault() and that returned null. Checking the public Jira and Automation backlogs, I could not find an open suggestion…

Yes, you are quite close with your second expression. Here is an example to filter the advanced branch to only cover the active sprint(s) for the current issue. The text version of that is: {{#issue.sprint}}{{#if(equals(state,"active"))}}{{.}}{{/}}{{/}}

Hi @Kelly Arrey I believe Phil wanted to use an if/else structure inside of the branch, not outside of it. I believe there was a "hack" where these could be created outside of the branch and then drag-and-dropped inside. That unplanned/unpredictable behavior appears to have been removed. Kind regards, Bill

Well done! The variation I was suggesting was to prune the list of sprints (using list filtering) so the advance branches only walk what you want: active or future sprints.

Hi @Alexandre Godin I recommend using the how-to article linked below to learn if your new fields are supported in automation rules. Basically you find an example issue with your field, call the REST API from a browser tab, and then look for your field. If you can see it, the field is supported by automation rules, and you…

Hi @Benjamin Ravalijaona First thing, I am not using that addon app, and... I recommend looking at that vendor's documentation and/or contacting them with this question: https://marketplace.atlassian.com/apps/1226612/qase-for-jira-test-management?tab=support&hosting=cloud. After taking a quick look at their information, it…

Hi @Kevin Drescher This symptom is caused by branch scoping: you are branching to the created epic so you can add the child Tasks, and later outside of the branch the newly created Tasks are not "visible" as created. One possible fix for this is to remove the first branch, like below. * trigger: scheduled * action: create…

Hi @Ander Yes, and...to Jack's answer: If you add a default value of 0 for that lookup issue size, it will always be a number. Otherwise it would be null (an empty value) when there are no issues. So an improvement could be: Version {{version.name}} released with {{lookupIssues.size|0}} issue(s). Kind regards, Bill

Hi @JG Meillaud _ To do this with an automation rule, and have the results reportable later, you will need a custom field and a rule. You will need to decide what data you want to save for the sprint, such as the name, id, etc. or perhaps a mashup of the sprint attributes. How to... * add a custom field, such as Fixed In…

Hi @Aurélie Pilette The WAS operator is independent of your Sprint check in that query. If you are checking a specific sprint, perhaps try WAS with DURING the timeframe of the sprint, as described here:…

Hi @Xuwei -- Welcome to the Atlassian Community! What version of Jira is your team using: Cloud or Server/Data Center? And what do you mean by "...but the mails cannot be found as quickly as possible"? * Do you mean the team is not reading the emails, * the emails are not sent quickly enough, or * something else? Depending…

Hi @Lidia Venturi -- Welcome to the Atlassian Community! Would you please post images of your complete rule (including details where the Slack message is sent) and of the audit log details showing the rule's successful and failure execution? Those may provide some context for the community to offer suggestions. Thanks!…

Hi @Sebastian Marquez Telis What have you tried thus far to solve this need? If you have a rule and are encountering challenges, please post images of your rule and the audit log details, and describe what is not working. That will provide the community context to offer suggestions. If you are just getting started, please…

Hi @Suma Kustagi -- Welcome to the Atlassian Community! You can do this with out-of-the-box features, using a JQL statement such as this one: project = myProjectName AND NOT status CHANGED AFTER -5d AND statusCategory = "In Progress" ORDER BY key ASC That would list the in-progress issues in your project which have not…

Hi @Justine If you are okay maintaining the rule, I believe you can do this with one single rule. It just needs to be updated when people change shifts. For example: * trigger: issue created * action: re-fetch issue * if/else condition* advanced compare condition: to determine if {{issue.create}} is in your "first" shift…

Hi @June Would you please clarify which rule execution limits are you reaching/exceeding? I hypothesize that you have rules making issue assignments happening with global / multi-project scope rules, and so are running into the monthly execution limit. If that is the case, you could quickly address this by copying the…

Hi @Phil Bustin This is the second question I have recently seen with this need (if/else in a branch) and I thought this was possible, and it is not currently. The UX of the rule designer appears to have recently changed to make it more clear when if/else can be used. For the use case you are showing, a couple of possible…

If you mean you cannot verify the JQL when editing the rule, that is correct. It can only resolve at run-time. If you mean something else, would you please show images of the Advanced Branch definition and the Lookup Issues action inside the branch?

Gotcha; there was a "feature" which allowed creating if/else outside of a branch, and then dragging that inside, but I believe that may have been fixed. The other work-around is to put the if/else conditions first, using smart value, list filtering to find matching sprints for the state. Then have a branch inside of each…

Hi @David Leal What does your testing show for the results of the above rule? I am asking because I hypothesize some unpredictable results... Branches on one-and-only-one thing (e.g., Current Issue, or Parent (Epic), etc.) get run in-line, and so the rule proceeds on the order of the steps you define, as if there was no…

Awesome! I am glad to learn that helped. Please consider marking this question as "answered"; that will help others in the community find solutions to similar questions faster. Thanks!

Do you mean entity properties, such as for issues: https://developer.atlassian.com/cloud/jira/platform/jira-entity-properties/ If so, I do not know how to do that with JSON from a rule, and there are no examples of this on the advanced edit documentation for rules. A work-around would be to call the REST API after the…

Thanks for that information! Let's try this... * Use the entire Approvers field in the advanced branch smart value {{issue.Approvers}} as that will provide the entire user object to the branch iterations (as described in this article) * Then in your sub-task create you may reference the variable's fields, as needed:*…

First thing, I am using Jira Cloud. And so I cannot test this... For Server/Data Center, I believe the equivalent is to use the bulk-processing option with either the scheduled trigger or branches, as described here: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html With that…

When you define the branch (or a created variable) you just supply the name, such as varAssignee And when you use it, treat it as a smart value expression with {{varAssignee}} And so your JQL for the Lookup Issues action inside the branch would be this: project = "EN" AND status IN ("Done","completed", "Released to Design…

Thanks for that information. I confirmed your result that Components, and in fact, many of the fields do not appear in that More dropdown...even when you search for them. I found several related defects in the public backlog but only found a related one for Jira Server/Data Center. And the documentation does not say what…

Hi @Michail Kotantakis Please post an image showing the details of your advanced branch, showing the smart value expression to set the {{ApproversList}} variable. That may provide some context for why the iteration is not working for multiple approvers. Until that is posted, I see another problem with the rule... Branches…

Hi @Philippe Vlaemminck The challenge you describe is the result of storing multiple pieces of information in a single field: a project classification and a project name. Perhaps consider using the project category feature, to classify the projects, and then JQL could help search on the…

Hi @usman_malik Are you using a Team-Managed or a Company-Managed project? You can see this at the bottom of the left-expanse area of the page. If you are using Team-Managed, Components are not yet supported. Here is the suggestion to add that, however Atlassian indicated in May 2021 they did not plan to work on this in…