Add more workflow condition options
V
Victor Carbonneau
The new condition settings in workflows is nice, but I would like to see more options available for us to set as conditional parameters for running a workflow. They should include Custom Field options, Project Level Sections, Date parameters, etc.
Some examples of how this would work:
- When "Status changes to XX" and Condition of "Section is currently AA" Then "update section to BB"
- When "Status changes to XX" and condition of "Due Date is less than BB" then...
- When "Status changes to XX" and condition of "Custom Field contains CC" then...
This would be a benefit to our workflow, organization and reduce the number of clicks that users have to remember to perform for each project by automating simple tasks.
Log In
V
Victor Carbonneau
Hello Eric Typaldos. Thank you for the information and updates. This will all be very helpful to our team.
For dates, I think the description of something more dynamic would fit what we are looking for.
Here are a couple more specific use cases and list views I could see us creating with more details:
- List view looks at the Due Date and breaks it out into sections by month/quarter/year/range so we can group action cards based on deadlines.
- Create a more dynamic "My Actions" list view on the Home app that allows for your to-do list to update more dynamically based on deadlines creating more focus.
I'm happy to share additional information if it helps.
E
Eric Typaldos
Hi Victor Carbonneau thanks for the request here! We've expanded available options on "Conditionals" to include "Action Custom Fields", which I believe is 1/3rd of the request here.
We're reviewing the ability to filter on "Section" in your other post here: https://hiveteams.canny.io/feature-requests/p/add-section-to-workflow-filtering-options
We've held off on adding support for filtering on date-like fields purely because we wanted to evaluate what kinds of equality checks would be desired. On initial pass, we figured that the ability to filter based on "Due date" {equals/not equals/greater than/less than} "some absolute date" wouldn't be very valuable, but rather than the date check would be dynamic, like...
"Due date" {equals/not equals/greater than/less than} "today/next N days/past N days/some relative range".
Can you give some examples of what types of equality checks you'd need to have for date fields so we can validate and consider moving this to under review?