Recurring cards

[Cante]

It should be possible to define a recurrence interval.
For example: weekly repeat on monday at 20:00

[juliusknorr]

How would you expect those cards to be handled? Should they just reset the due date once the last due date has passed and the notification about the overdue card has been send to the user?

[Cante]

This is true. You can close the ticket.

[jakobroehrl]

Other Apps solve this so:
When a recurrent task/card is archived/set to done it will pop up again in the future with a new due date

[juliusknorr]

Might be something once we have #534

[horvan]

Would like to se this Feature, soon. Especially since dashboard shows cards they are a cool alternative to a full calendar. So should it be hard to archive cards and reopen them again if they have a recurrent option?

Plus 1 for this. I like the Idea.

[eX00r]

Describe the solution you'd like
It would be great to have the possibility to select "recurring" when creating the card in Deck. If "recurring" is selected, the user specifies the interval and defines an end date or a number of occurences after which not further repetition is to be scheduled. The user can then also select in which list the recurrences should appear. After creating the card, Deck creates the first occurence in the List where the "add card" button was clicked and also creates all following occrences in the list selected for recurrences (ie on hold).

[l-mb]

Indeed, I'd love the ability to mark a card as done, and for it to then automatically reappear with the new due date as per the recurring interval. Possibly with the option of being put to the end of the list, or even to another list.
So there'd always just be "one" card in the deck, not multiple.

Right now, we can't even have recurring tasks, and so have to manage that manually or externally.

This would greatly help with workflow management.

Thanks for the consideration!

[eX00r]

Any news on this?

[DDriggs00]

This would be a great feature.

[DriedPlumber]

I just noticed that I would like too to have a feature for "recurring" Deck cards...
I have just created a card to pay bills and I realize that I will have to do it every month...
Thx

[daniel-sousa-me]

Other Apps solve

Right now, we can't even have recurring tasks, and so have to manage that manually or externally.

What other apps or tools can help with this?

[meichthys]

For reference, the issue with recurring tasks is here: nextcloud/tasks#34
The only nextcloud alternative is to try to use calendar events which do support recurrence, but this is not ideal.

[Extarys]

@meichthys I currently use a specific calendar for recurrence, and add emoji at the start of the event's name to see what's what at a glance, but it's a mess. I have 10+ events per day sometimes. (add the regular calendar events and you get eyestrain)

[viktorix]

Just wanted to add a bit more information as I would love to see this feature. For personal stuff, I've used Nifty project management app. Here's their UI to create a recurring card:

When a card is completed, a new task is created in the column where original recurring card was created. So if I create a recurring card in column "To Do", and then it is completed in the column "Done", the new card will be created in "To Do" column.

[helheimcloud]

@viktorix Additionally, it would be nice if you could have a setting "Show card X days before due date". It would not make sense to have the task pop up again just after closing it. This would then be a nice minimalistic "Preventive Maintaince Task Scheduling" System.

I hope this will be added soon. I really want to use Deck instead of an external tool. People are requesting it since 2018 anyway :D

[marcoambrosini]

Related nextcloud/tasks#2318

[hansimausisteffiwurstbrot]

Related nextcloud/tasks#2318

Kind of, but about another app.. :)

[DinoBellini]

It should be possible to define a recurrence interval. For example: weekly repeat on monday at 20:00

example: every 6 month first monday; every week on friday, first and third monday of month.....

[distresscode]

any progress on this?

[juliusknorr]

@nimishavijay Are you already working on something there for design specs or does it make sense to have some kind of kick-off meeting? So far we don't have any clear requirement definition.

[juliusknorr]

For inspiration https://support.atlassian.com/trello/docs/using-the-card-repeater-power-up/

Two ways of handling recurrence:

• Use the same card and just set the due date again (like caldav tasks do it)
• Clone the card to a new one with the recurrence (how trello does it)

We should get an overview on how others handle it, what the most common path is.

Further discussion points:

• If we just set the date, how does the card change columns: Smart column for done state, start column?
• Clone card could already cover the use case of creating new cards, reminders might be fine to just cover by setting the due date again

[nimishavijay]

So taking a look at Trello and Asana, the card is cloned to a new one. Which makes sense in most use cases of this feature (Eg. a recurring card for a weekly meeting where the description is the agenda, and cloning the card would help to prevent loss of the previous week's agendas and action items).

The main difference between Asana and Trello is that in Trello the repeating and due date are separate, setting a card as repeating does not affect its due date, the card is literally cloned. In Asana, the setting a repeat means that the card is cloned with a new due date for every card.

Like many of the above comments it would be great to set the due date as a part of the recurrence, it could be cumbersome to have a card pop up automatically but you have to calculate and set the due date, especially when you're out of the original context.

UI

The calendar is a good reference for the UI itself.

• Below the row with the due date, there could be a "🔁 does not repeat" and a "+" button, clicking on which opens the recurrence selector.
• The recurrence selector design could be similar to the (intended) design in Calendar Recurrence selection is small and fiddley calendar#4618 (comment) with the "End repeat" as a nice-to-have
  • One important change is a little subline in the dialog with a short explanation about the recurrence. "When a card is marked as done, another one will be created with the set due date" or something similar
  • There should also be an dropdown to set the column that it repeats in. The default value is the column the card is in currently, but if the card is moved to a different board and modified then it should be clear which column the card will repeat in.
• When a card is recurring, the chip with the due date can have a 🔁 symbol next to the clock symbol
• Icon: Material Symbols repeat icon

Behaviour

• if recurrence is set on a card that already has a due date, the recurrence starts after the due date (eg. due date is 15.10 (Tuesday) and recurrence is weekly on Monday => first due date is 15.10 (tuesday), then 21.10 (Monday), 28.10 (Monday), etc)
• once recurrence is set for card A,
  • due date is changed => change only due date od
  • card A is marked as done => card B with new due date occurs in the original column where the recurrence was set
  • card A is deleted => modal with message "Deleting a card also stops it from repeating. To keep repeating the card, archive it instead" with options to archive, delete, and cancel

Let me know what you think!

[craftypenguins-chris]

This behaviour has been implemented in other platforms in a less-than-ideal way.

In MS Planner, for example, marking a recurring task as done with creating a new task becomes quite cumbersome. This is especially true with large teams pulling the tasks from the on deck in true KanBan style.

I propose an alternate logic for this, which Nextcloud codebase may or may not be suitable for. If not, this may need to be a separate app altogether:

Recurring tasks would be treated like a set, grouped so that the UX for managing them has the functions needed to control all tasks in the set.

What would be great would be to have a generation trigger option which specifies when the user would like the next task created. For example, if we have a task that is monthly. That task could be set to regenerate on the 1st day of the month. A weekly task can specify which day of the week to trigger the next set. Then, a checkbox to decide generation based on the previous task being completed (for example).

Another advantage to managing the recurring tasks as a set is that you can manipulate the group, i.e., pause the set or delete all tasks up to a certain date.

Happy to invest some time into this as we are considering this product for our internal business use case and moving away from M365. Also, open to alternative thoughts on how to accomplish the above. As a user of Planner and other task tools, I can tell you this is a bother for most everyone.