I have the above Due Date Command setup and configured but for some reason it doesn't work and I'm not sure why. I submitted a support ticket to Trello Support about this last week but I never heard back. I have archived cards that are in the "Lead Went Cold" list that have due dates. On the due date, I want Butler to unarchive the card and move it to the list "Archive Lead".
Can any of you spot what I'm doing wrong? Does Butler not work on due dates for archived cards?
@tommytompkins the documentation for the old Butler Bot shows that they removed acting on archived cards by default and put in an "archived card" modifier:
Since the "archived card" modifier isn't present in "NewButler" this suggests to me that Butler will no longer trigger due dates on archived cards at all.
Is there a reason you want the cards to be archived?
I use the Snooze power up to snooze cards in certain lists so that the cards disappear for a week, a month, or more. When I snooze a card I want them to disappear so that I can focus on the cards that really need attention. When a card is snoozed, it’s actually archived then it automatically gets unarchived when the snooze is up. For some cards, I want to set a due date In addition to snooze and have butler automate based on the due date.
Btw - I ran some tests and even with unarchived cards I couldn’t get the due date commands to work. I think there are some serious issues or bugs with the due date commands. I moved those to daily calendar commands to accomplish what I needed. It’s a little messier but it works. If the due date commands worked, it’d be much better.
@tommytompkins what usually throws people when testing Butler due date commands is that they don't work if you only set the due date in a couple of minutes. Try setting the due date in 5 minutes, they're super solid.
To your snooze issue, you could use these 2 commands to move any card you add a Snooze label to that has a due date to the top of a Snooze list, sorting the list by due date, then when it's due move it back to the list from which it originated:
Thanks for the suggestion. That looks like a very doable work around. I have everything working great at the moment with the calendar commands, but curious if your solution might be better. Would it potentially use up less Butler resources / operations?
Just so you know, I did test the due date commands with due dates that were more than 2 days in the future and I still couldn't get them to trigger so not sure about that. I still feel like there's some bugginess there.
Hello Community! My name is Brittany Joiner and I am a Trello enthusiast and Atlassian Community Leader. I'll be sharing with you a series of videos with my top tips on how to best use Trello...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events