New Recurring Tasks Feature Bug?

[Ruby Chocolate]

I was putting the new and very useful recurring task feature through its paces, when I ran into behaviour that I don't think is intended.

I want a task to repeat on the last day of each month. Not the last specific weekday (Monday, Tuesday, etc) in a month. The last one.

So I set it to the 31st of March, set it to repeat "Monthly on the 31st," as was the option provided to me, and when I marked the task as done, it jumped to the 31st of May, rather than the 30th of April, skipping two entire months in the process.

I don't think this is especially useful to anybody as it is currently implemented, and in this case should attempt to find the latest day of the next month. "Monthly" is pretty clear in what it means.

[Ruby Chocolate · Accepted solution]

I recorded the behaviour, as seen below, however I decided to experiment further and found that it was literally only that card that exhibited the behaviour.

Creating a new identical card seems to have fixed the issue, however I also disabled an automation beforehand, which moved a task marked complete to the top of the "Completed" list. Only disabling the automation did not fix the issue, but it works now that I made an exception for the list itself, as shown below (the "not in list" qualifier was not in the original automation).

Could it have interacted badly with the recurring card the first time, in such a way that it caused the bug?

Recording is below.

[Cody]

Thank you for the recording! And I'm glad to hear that creating a new card solved the issue, that's definitely strange. I tried replicating with the same rule (both before and after your edit), but still haven't been able to.

That's good in my opinion! But still leaves a bit of a mystery. You're right that it was a bug, but right now we don't have strong leads to the source. I think perhaps if this comes up again, let us know. Particularly if you notice a sequence of actions that reliably replicates the problem. 

[Ruby Chocolate]

It seems like, as I discussed in my last reply, this is the way to reproduce it, which I've managed to do.

1. Create an automation rule "when the card is marked as complete in a card, move the card to the top of list "Completed"

2. Create a card with a due date on the 31st of any month, repeating monthly on the 31st

3. Mark as complete

It should create a list "Completed" (I'm not sure if this is required but it's how I reproduced it), place the card in it, and the card's repeating due date will now skip any months that have fewer than 31 days.

[Cody]

Thank you, that's helpful as well, though I still haven't been able to replicate on my side so I suspect there may be something else on your paritcular board at play.

If this continues to be an ongoing blocker for you, please don't hesitate to open a support ticket through support.atlassian.com where our support engineers can help investigate further in more detail. 

For now, since adding that condition to your rule solved this issue on your board, I think that may be our best workaround, if that seems like a reasonable solution for you!

[Ruby Chocolate]

This seems to work fine now, and I know what to look out for if it happens again. Thanks for the help!

[Cody]

Hmm, that's not the behavior I'm seeing, so I'm wondering if you could provide a bit more detail. I'm hopeful there might be some nuance here to get it working as you expect, or if I can replicate that bug, I'll be glad to report it.

I tested with March 31, and May 31 due dates. I set it to recur monthly on the 31st, then marked it complete, and the due date moved to either April 30, or June 30 respectively.

My card was due at 9am, and my notification reminder was set to At the time the card is due. Were either of those different for you?