POTENTIAL BUG DISCOVERED: Move due date automation

[DiMaggio Tucci]

EXAMPLE CONDITION:

-Today's date is January 27th, 2025

-Card due date is April 1st, 2027

-Automation is run on this card with "Move the due date to the first Monday of the month"

EXPECTED BEHAVIOR: 

Due date will be set to April 5th, 2027

ACTUAL BEHAVIOR:

Due date will be set to January 6th, 2025

WHY THIS BEHAVIOR IS A BUG

-The purpose of the "Move" due date is specifically that it makes the calculation in respect of the existing date on the card. "Set" is used if the calculation should use the current date/time instead. This is literally the stated difference between "set" and "move"

-The ACTUAL BEHAVIOR would be the expected behavior if "set" was used instead. Indeed, "set" was tested as well and behaves this way. "Move" is supposed to behave differently. The available wording is even different, with set showing "this month" and move showing "the month" in the dropdown, IMPLYING that the behavior should be different.

-No other "move" automation behaves this way; they all move the date with respect to the existing time on the card.

[Lara]

Hi there,

Thanks for reaching out!

I haven't been able to replicate the issue. When I set up a test automation, such as:

when a card is added to list "Test", move the due date to the first monday of the month

The due date is moved to the correct day, i.e. Feb 23 due date updated to Feb 3.

Can you please share the full automation rule where this is not working as expected?

I'll keep an eye out for your reply,

Lara
The Trello Team