Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Help with moving cards from list to list based on due date

Hi All, 


I have a pretty basic board set up with three lists called "Back Log", "Due in 5 days" and "Due Today".

I have an automation set up in the list "Backlog" that moves cards from that list to the "Due in 5 days" list when the card's due date is due in less than 5 days. 

In the "Due in 5 days" list there is an automation that will move cards from this list to the "due today" list when a card's due date is due in less than 1 day. 

The idea is that cards are only ever being added/created in the "backlog" list and then they get sent down the line to the other lists according due date....pretty straightforward I think. 

The problem I have is that when I create or add a card to the "Backlog" list that has a due date of today, it automatically moves to the "due in 5 days" list then stops moving. It should get to that list then get moved a second time to the "due today list". If I add/create a card in the list "Due in 5 days" with a due date of today, it will correctly move that card right to the "due today" list. Trello is having a trouble moving a card from list to list. 



1 answer

0 votes
Suzie M
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 26, 2023

Hi Brady, welcome to the community!

Just letting you know I've already replied to you on TRELLO-144126, and will be happy to continue investigating this issue there. 

Looking forward to hearing from you.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events