Hello, we have a custom field named "Go-Live" which is the launch date. I've added 9 automation rules based on this go-live date to create items in a checklist. The items within the checklist are in chronological order (i.e. Task 1 is due 14 days before go-live, Task 2 is due 13 days before go-live etc).
However, when this checklist populates, the tasks are not in chronological order and I'm unable to find a rule to help me do this. Please see sample automation rule below:
when custom field "Go-Live Freelance" is set by anyone, add item "Task 1" to checklist "Freelance Checklist", and set the item due on the date in custom field "Go-Live Freelance" minus 14 days
I've repeated this automation rule for all the items in the checklist with different dates.
In the below screenshot, you can see Oct 26 as the go-live date that was selected but all the tasks underneath aren't in order according to the dates.
Does anyone know of a rule that could help solve this?
The way I have observed Butler works is that it guarantees that the operations are executed but it does not always do it in the sequence as they are in the script. If you iterate a checklist items then it will hold the sequence or if you have something that use a httpresponse, it will wait from the return from the 3rd party services.
You have couple of workaround (1) manually move the items (2) deploy code to it to sort (3) deploy code to it to add dates in "as shown" sequence....etc.
Here's an example where checklist item and linked cards are with days increment/ decrement or a series of dates (done post video)
Your post prompted me to enhanced a module that I had to sort by due date on checklist item.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much! Does this mean I would add an additional action to each automation rule with the below criteria? I'm not very familiar with code unfortunately so I'm not sure if I'm doing this correctly.
I replaced "checklist_name" with the name of my checklist and replaced "sort" with due
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The module is called via the http request. Depending on your actual setup, yes it can be called within a command or as a card button.
The module is part of a service i provide as part of my freelance work. The details are documented on the public board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is how it looks like using a card button...card id, checklist name and sort option are hardcoded but you can use card variables {} and {{%..}} for more flexible deployment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your answers! I'm unable to use the module for this use case unfortunately but I appreciate your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.