I would like to create a new automation to compare the value of 2 columns and the condition is met to change the status. Currently only can compare to a fix value or number.
Example:
When “items” equals “items completed”
change status to “completed”
Could you please let me know if this is possible?
Thank you
Victor,
For the two columns that you’re comparing, first make sure the column-types are supported as “Triggers”. If they’re not supported as triggers, provide some more detail of what you’re wanting to accomplish and maybe we can help find a built-in solution.
Then you’ll need to create two automations - one for each item to react to the other - for each condition.
The end result will be something to this effect:
When Status_Column_1 changes to Something …
and only if …
Status_Column_2 is Something,
Change Status_Column_3 to Something.
Then your next automation needs to trigger when Status_Column_2 changes to the correct value.
Rinse & repeat for every condition.
Let me know if this helped 
Good luck!
Hi Calum,
Thank you for your reply, however the value of “Something” is not a fixed number, depends on the task.
For example:
Task 1 > Subitem with following Columns: “Items to Complete” 60 - “Items Completed” 0
Task 2 > Subitem with following Columns: “Items to Complete” 95 - “Items Completed” 25
Only when “Items to Complete” equals “Items Completed” change status to “Completed”
Hope this make sense and I can find a solution since this is the starting point to trigger and move items across different boards.
Thank you.
Victor,
Hey Victor,
That makes sense. That’s a super common use case, but there isn’t a built-in feature that will change a column based on a numbers calculation. You could possibly try using a Formula column, but it can’t be used to update another column or as a Trigger in automations.
For your exact desired behavior, you’ll need an app or integration like these: General Caster, Autoboost, or Formula in Automation Recipes.
However, with a minor change to your design I think we can find a solution without having to use an integration or app:
-
With your intended logic, the “Items to Complete” column really means the “Total Items to Complete” versus a running number of the current items that need to be completed.
So, change the name of that column to “Total Items to Complete” and add a new Numbers column for “Current Items to Complete”. -
Then you’ll need an automation that decrements the “Current Item to Complete” column at the same time you’re incrementing the “Items Completed” column.
-
Last thing to do is create an automation that triggers when either of those column changes and says as long as the “Current Items to Complete” column is equal to 0, change the Status column to "Completed.
One caveat is if your “Total Items to Complete” column is ever updated or increased. In that case, you’ll just want to make sure and also increase the “Current Items to Complete” column by the same amount.
Let me know if that helped,
Best of luck to you!
Hi Calum,
Thank you for your reply. I understand your logic, but I think I have the same issue since the “increase” or “decrease” value must be a fix number, can’t be “decrease by value of Items Completed value”. Can decrease 1,2,… 25 or any number.
I think it is quite straight forward logic that should be built-in feature already.
Any other option that may I use?
Thank you
Victor,
Hey Victor,
I agree, it is straightforward to calculate a value based on two unrelated columns and change another column to the calculated value, or another value based on the calculation. However, there’s a lot of nuance under-the-hood that does not make it straightforward to develop. I can imagine, that’s why it’s not a built-in feature yet.
For this situation though, if we have a counter that keeps track of a number of things it should count every individual thing, not groups of them.
For your scenario, your counter needs to be updated every time an item gets added to the “to be completed” queue.
If you give some more information on the high-level of what your workflow is trying to accomplish, and some details of how you’re trying to accomplish it, then I can try to be of more help.
Best of luck to you Victor!
Hey Calum,
Thank you for your reply.
Actually, the functionality it is very simple. I just want to track the progress of the items completed within a packaging machine process.
“Items to complete” is 80 (or any other value). “Completed Items” is 0 at the beginning, and can be increased by any number lower or equal than “Items to complete”.
Once both attributes are equal, the Status should change to “Completed” and trigger some other actions. I think is quite straight forward, I am surprise this can not be done as standard functionality. For now, we’ll proceed manually but I am quite disappointed to see all the basic technical limitations.
Thank you
Regards
Victor,
Hi Victor,
I appreciate your persistence in seeking a solution. Your desired outcome IS achievable, though it might require a different approach than you initially anticipated.
Let’s revisit the recommendation I made earlier.
Consider focusing on getting one field to reach zero as the trigger for your automation. This approach involves a shift in perspective - instead of directly comparing two fields, we aim for a specific condition (a field reaching zero) to activate the desired status change. This method aligns with your requirement where the status changes to “Completed” once the remaining tasks drop to zero (or once the completed tasks and the total number of tasks are equal).
The concept is akin to operating a vehicle: when you press the gas pedal, you don’t consider the complex mechanics of fuel combustion and energy conversion. Your primary concern is moving the vehicle forward. Similarly, when engineering workflows on Monday or any other platform, it’s not always about the direct route or the obvious solution. Sometimes, you need to think outside the box and adapt your strategies to align with the tool’s capabilities to achieve your desired behaviors. Often, the key to effective automation lies in finding inventive ways to work with existing functionalities, rather than expecting the tool to match our initial vision perfectly.
I hope this perspective helps you in configuring the automation as needed. Remember, the goal is to find a workable solution within the constraints of the platform. If you have any more questions or need further clarification, please don’t hesitate to ask.
Best of luck to you Victor!