What's the best and simplest way for non-admin users to create recurring tasks in Fibery?

[Renato_Carvalho]

Hello Fibery community,

I’m looking for the most straightforward and efficient way for users without administrative privileges to create and manage recurring tasks.

I’ve seen that there are automation configurations for repetitive tasks, but they seem to require technical setups that might be challenging for regular users.

Ideally, I’d like a solution where users could easily set recurrences such as daily, weekly, monthly, or yearly in an intuitive way.

[Chr1sG]

It somewhat depends on how you define ‘recurring tasks’ and what your expectations are:

Creating recurring tasks

It depends what you mean by ‘Recurring task’. Is it a series of Task entities, created all at once, each with a different date value, representing the desired intervals? Is it a series of Task entities that get created, one at a time, on a predefined schedule? Is it a single Task entity whose date is updated everytime the date is reached/exceeded? You need to understand what you want to do with your tasks (and when) before deciding which of these (or some other solution) is most appropriate? …

[Renato_Carvalho]

I know it depends.

But I mean recurring tasks the way anyone would expect to behave in normal project management / Task Management tools.

[Chr1sG]

@Renato_Carvalho

the way anyone would expect to behave in normal project management / Task Management tools

Forgive my ignorance, but I don’t know what is ‘normal’ so perhaps you can clarify.

[grex22]

I’m sure others will have better ideas, but I would start by creating a “Recurrence” number field in my tasks, as well as a “Recurrence Period” field, and a “Re-Open Date” field.

So your task could optionally have as an example, a:
Recurrence Period: Month
Recurrence: 3

For a task that is meant to recur every 3 months. The period could be “year”, “day”, “week”, etc.

Then, and this is where AI might help, but I would create a formula that runs every day – It would scan for Tasks with Recurrence Fields filled, and would see if the proper amount of time had passed for the recurrence.

If so, you could either Re-Open the task, create a clone of the task, or some other such thing.

This could get quite complex depending on the logic you want to support. I could also see it being as simple as a single field that represents the number of days between reoccurences, which would cover simple scenarios pretty easily.

To @Chr1sG 's point, depending on how you want the logic to support (allow for “Recur the first of every X months”, every “X years”, clone the existing task vs re-opening the old one, etc) the setup would probably change quite a bit. There’s probably not a consensus on what anyone “would expect [recurring tasks] to behave in normal project management tools”