More automation conditions
planned
Mattias Björkholm
More automation conditions would be great. It's very limiting to only have a condition based on which kanban status a card has.
Some suggestions on conditionals: if card has tag X, if card title contains X, if due date is within X period, if card has members XYZ, if card has field with value X.
Comment which conditionals you would like to see!
Dovidas Baranauskas
Merged in a post:
Automation conditions based on what a field IS
Amelie Beaulne
I want to be able to set conditions that look at what a field is set at instead of a "field change".
For instance, a combination of these conditions would trigger an action:
- When a card is added to this board
AND
- The member field is set at "person A"
Maurice Kroes
There's a big topic similar to this request here which may help to create visibility: https://favro.canny.io/feature-requests/p/more-automation-conditions
Dovidas Baranauskas
Dovidas Baranauskas
Jordan Arnold you can do that already with the current automations:
Is that what you are looking for?
Jordan Arnold
Dovidas Baranauskas: that’s half of what I want, thank you!
I’m not sure if it also works the other way: when a card changes status and it already has this tag. Like, for example, if it’s already a Bug and it gets put into Review, it will automatically move it to Accepted
Dovidas Baranauskas
Jordan Arnold: That is currently not possible. That would be a feature suggestion. Will merge your post with the suggestion.
A
Adam Boyne
At the minute it's basically pointless having a second conditional, could this just be all of the conditional options from the first instance?
J
Juliane Bogenschütz
"If user X is unassigned"
R
Ryan
Any updates on this?
Dovidas Baranauskas
Merged in a post:
Add Status Automation based on which tag is applied
J
Jeremy Terry
I'd like to create an automation where if a card has a certain tag applied at time of creation, it would not be allowed to have a new particular status applied at a later point. We use one kanban board to track the status of a device through the manufacturing process. Each device has a card created for it. The tags assigned to each card show which device type it is. Some devices do not go through every status, so they should not be allowed to have that status applied.
Dovidas Baranauskas
Merged in a post:
Automations on Favro should allow more flexibility of conditions
J
Jay Halderman
Automations currently do not have enough flexibility to be very useful for the way we use Favro.
We have set up a collection containing a backlog in sheet view, and a Kanban board. We set up automation to update the status of a card in the backlog when it is added to, or moved along the columns on the Kanban board. Below are example images of the boards and the automations.
Figure 1, 2, & 3
This set up does not work for a collection with multiple backlogs and one Kanban, because there doesn't seem to be an option to set up conditions to distinguish the backlog that a card comes from. So, when a card moves between columns, the automation won't know which specific backlog to update the status.
When we try to define more conditions, it only allows one “When card is in status” condition, and this extra condition often does not work because Favro does not support multiple status conditions.
Figure 4
Maurice Kroes
If card has tag X or other field condition that would make the system a lot more powerful and flexible!
Load More
→