Bill Sheboy Expert

Hi @rneill19 You may do that with an advanced branch to iterate over the values in your multiple-select option field. For example, the branch could iterate over {{issue.myCustomField.value}} to access the displayed values from the field. Kind regards, Bill

Hi @Garn What leads you to believe changing the units on a CFD will make it "more accurate"? A CFD helps see flow measures, such as arrival rate, WIP, throughput, starvation, etc. That works because the units are the same, supporting conservation of flow: 1 on the chart equals 1 work item, and whatever enters at the start…

The issue the rule is branching to is PLM-1. Is that an epic issue type? If so, the rule logic which later checks fields like {{issue.epic.summary}} cannot work as an Epic cannot have another Epic as a parent. If this logic should be more generic, due to adding a level to the issue hierarchy, please change those references…

After I re-read the REST API function, I saw it requires finding the date / time range using a UNIX timestamp. Although timestamps can be calculated in a rule, it may be more understandable to others to try approach #1 first, using list filtering. First, the example solution and then the explanation. This rule, triggered…

Well done diagnosing that! That is a curious, and unhelpful error in the log for the required field. When others have encountered that scenario a different error can appear for this in the audit log. My hypothesis is this error depends upon the type of field which was required. I checked the public backlog for any…

Sorry, my mistake. I confused your time tracking question with another one. I will update my original response, and I suggest un-accepting my answer and accepting your own to help other community members in the future. Thanks!

Hi @Nicolas Marchildon -- Welcome to the Atlassian Community! What is your association to the vendor / products from Actioner? Thanks! Kind regards, Bill

Would you please post images of the audit log, showing the rule execution and an image of the Jira issue which the rule has appeared to update? Please include the issue history and the time tracking field in the images as those will show what the rule attempted to change.

Awesome, and well done solving the notification issue!

Hi @Jenny Luther -- Welcome to the Atlassian Community! I do not believe that is possible. There is no public REST API function to get / update the quick filters for the swim lane configuration of a board. Kind regards, Bill

If 10 is highest-priority then you would want to use this for the sort: project = myProjectName ORDER BY yourCustomField DESC You may added more criteria, to sort by progressively more fields, as needed: project = myProjectName ORDER BY yourCustomFieldA DESC, yourCustomFieldB ASC

Thanks for that information, and I should have provided a disclaimer that I am not using Tempo; my suggestions are based on what I know about automation rules. Next, I recommend reviewing the Tempo documentation first to determine if that tool already has this reporting / notification capability. The reason I suggest that…

The ORDER BY for the board filter could be changed to sort as you wish. For example, project = myProjectName ORDER BY yourCustomField ASC Then any changes to the field(s) would be reflected in the order of display. What would you expect the automation rule to do? Is it calculating the value of your "Priority Rating" field?…

Hi @Alexander Neschanjan First thing, I am not using Tempo; my suggestions are based on what I know about automation rules. If there is no direct access to the Tempo time tracking field with the rule's issue edit action, perhaps check the Tempo documentation to learn if there is a REST API function to edit that field. If…

Hi @Mayra Hernandez Are you trying to check the total time spent for a single issue exceeding the 120h threshold, for a group of issues, or something else? Perhaps if you provide a specific example, and explain how your rule is not working as expected, that will help the community to offer suggestions. Thanks! Kind…

Hi @Jeanne-Mari Benn -- Welcome to the Atlassian Community! What would automated prioritization look like to you? How would it work relative to any manual prioritization? The default sort for a backlog / board filter is ORDER BY Rank ASC. When that is used, the manual drag-and-drop to change rank / order words. Any other…

Please post an image showing the audit log details (under Show More) for the rule execution. That may explain which steps are running and the cause of the problem. What are the types of these projects: company-managed, team-managed, or one of each type? Team-managed projects use independent configurations, including status…

Hi @snwatts6 For a question like this, please post an image of your complete automation rules, 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.…

Hi @david_levy Adding to Walter's answer... When you navigate to the Sandbox site's global automation configuration, what do you see for: * the allocation for all of the products in the site, under the usage tab * the global automation log for any rules which have run And, the image you show has the plan as UNKNOWN; is…

Hi @Amruta Harale This is a fairly common scenario, and I believe there are project level templates / examples for it. Have you already started a rule, and are having problems with it? If so, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit…

Hi @彥宏(Luke) 劉 There are two things to consider for the scenario and rule you show: You are trying to access issues in multiple projects, and so the rule scope must be global or multiple-project. What is the scope of your rule, as a project-scope rule would not be able to access issues in multiple projects? The rule you…

Hi @Simon Galiazzo 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.…

I just tested this scenario as a global-scope rule and it worked for me, with a specific project selected and "project from trigger" (which would automatically select the project for the version). Let's try to narrow down some possible impacts... * What is the project type of all projects involved: company-managed,…

FYI for stuff like this, you really do need to experiment. There is a bit of exploring required as not everything for rule behavior is documented to know what will / will not work...particularly when fields could be null. Anyways... Assuming the variable is empty when there are no sprints, and it ALWAYS ends in an…

That format() function should not be needed as the following produces a comma-separated list of keys: {{lookupIssues.key}} You can force that to text with this: {{lookupIssues.key.join(", ")}} Also, try writing the number of items to the log after the lookup to confirm what was found: lookup found issue count:…

Sorry for my mistake, as when I just tested an example rule, I found that the name must be used to set the fix version in the issue create: {{version.name}} Please try that and let me know what you observe. Also...Are you trying to create an issue in the same project where the version is created, or in a different project?…

No worries; we are all learning. A few adjustments to your call to the REST API... For that function, do not pass any data for the Send Web Request action: * the HTTP Method should be Get * the Web Request Body should be Empty Please re-read that how-to article as your header is incorrect: * The key should be:*…

Hi @adrien miniere Thanks for that information; it is interesting that it works now. The REST API for the issue create supports adding one link at the time of issue create, but that did not work in automation rules just a few months ago. Instead rules needed two actions: create issue and then add the link. Looks like…

First, try changing that JQL for the Lookup Issues action inside the branch from this: AND "Epic Link" = "{{issue.Epic Name}}" to this: AND "Epic Link" = {{issue.key}} The reason is after the epic changes to sunset fields like Epic Name, that is not populated / required by default. And so it may be null for many of your…

Thanks; that looks like it is null. Are you trying to create one smart value expression that works for all cases, or are you open to a couple of them? (e.g., use conditional logic to handle the 0 case separately from the others)