You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey All,
wanted to understand what causes Butler to change the due dates against the rule which states that if a card is moved to a particular column, the due date is 2 working days.
Why so many updates of a due date when the card wasn't moving around the board?
The first update [April 19] is correct. The rest is wrong and misleading.
I did a review of all the rules on the board, and they look the same:
"when a card is added to list "XXX", set due date in 2 working days, and sort the list by due date ascending"
-> and that's applied to different list, just with different number of days.
Has anyone faced a similar problem? Super happy to understand what I am doing wrong.
Hi @Luiza Kotys ! Welcome to the community :) All the date change actions look like they were executed at the same time. Do you have another butler rule that triggers off a date change? Maybe test out the "when a card is added to list XXX" rule on a separate test board to narrow down if another rule is interfering with it?
Hi @Hannah Morgan - thank you for your response and suggestion.
The only rule that's in place - for various lists - is the one I mentioned above: "when a card is added to list "XXX", set due date in 2 working days, and sort the list by due date ascending"
It gets worse and worse, honestly. Not sure where to look for the root cause. As you can see below it's not only about future dates, but it switches to the past dates, too?...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Luiza Kotys Did you also check the other commands? Potentially there's a due date command or calendar command running?
You might also want to reach out to Trello support - they may be able to track down what command is causing that behavior.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Hannah Morgan - I did check those. In the "Calendar" section I only have rules regarding reporting, and as for "due date" commands, I use them to ping folks to remind them there's an card waiting. It doesn't seem like they could interfere with due dates in lists...
I'll contact Trello support as well - thank you for the hint and your suggestions :)
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.