A please for: Re-occurring tasks + Google Calendar

Get Help
1

Hello,

I just want to ask please, if possible, can you guys look into the following?

I have tried every tool on the planet now - Clickup, notion, Coda, Capacities, Obsidian, and half a million more. I finally discovered Fibery. It is such a fantastic solution/website but there are two problems that I run into on a daily basis, and I am now back again to a place where I feel I have to go search for another solution.

I understand, based on what I read on this forum, that individual users is not exactly Fibery’s bread and butter. And judging by how most of these solutions seems to be increasing prices up to a point where only companies can afford it, I get it, we do not bring in the money.

I also understand that people looking for a Notion solution, or for a Clickup solution, maybe Fibery is not exactly the solution. It could be however. So this is where I want to ask, please, despite some of us not bringing in the cash, is there any way you could please consider just two things for us…

a) Re-occurring tasks. I do not understand how this is not also important for corporate clients, but either way.. it is important for many of us. If I am going to use Fibery as a task manager, it must have this. And yes, I have tried all the formula’s and other hoops one have to jump to to get it to work - it is possible I know, but can you guys please make it easy so that normies can use it too? Please? If one have a date field, the option to have it as a weekly, monthly, yearly reoccurring task would be wonderful.

b) Notifications. Again, I know one can find solutions through Zapier and Make and what ever else. But my plea is if you could please consider a two-way native integration between Google Calendar and Fibery. So one can get notifications of ones tasks.. so that what’s created in Fibery also ends up in Google and visa versa.

I am one of your biggest normie proponeds on places like Reddit. I try to sell Fibery as a solution to everyone and anyone on the Notion and Clickup forums. But these two items.. these two things a certain group of us absolutely need. I feel that at least for reoccurring tasks, this is surely something everyone needs. I need it a million times more than the latest AI features. Can you guys please, big please, consider looking into this?

Thank you in advance.

1 Like
2

Taking Fibery’s fundamentals as context, how do you consider ‘recurring tasks’ should work?

Is it a single Task entity which has multiple dates associated with it (1 Jan 2025, 1 Feb 2025, 1 Mar 2025, etc.)? In other words, a single entity shows on a calendar/timeline in multiple places.

Is it a set of entities, each with a single date field, that are somehow associated with each other? What significance does this association imply? Do changes to one entity in the set get replicated to other entities in the set, or are they functionally independent?

Is it a Task entity which spawns a clone of itself after a certain period of time (and the clone spawns a clone of itself, etc.)? What is the relationship between an entity’s ‘Due date’ and the date at which spawning should occur?

I think different people have different expectations for what ‘recurring’ entities actually means (and this may depend on the tool(s) you are most familiar with using).

3

Hi Chris,

Thank you for your reply. I have seen you respond in a similar way in a previous post - asking how a re-occurring task is to work. To be honest, I am somewhat baffled by this response.

If you open any modern calendar, any calendar, anywhere on earth, when you make an entry, it will ask you, do you want to repeat this entry: daily, weekly, monthly, yearly. I absolutely disagree with you that normal people have different expectations when it comes to repeating dates on a calendar. What different expectation could there be when one talk of dates, all one want is for that entry to appear again in specific intervals. I mean I feel like I am explain the most basic thing - or what am I missing? The most common standard options offered by most calendars are: weekly, monthly, yearly. The more fancy ones will give you the option to select specific days within a week to repeat week after week. If we were talking of anything other than dates, then I would maybe understand why there would be weird and different expectations of how it should work.

If one use something as a project management, task management, or anything related with a calendar solution - then repeating events is surely something that will occur.

If there at least was a Fibery Repeating Tasks Template with all the formulas built in, that gives one the option to select any of the most typical reoccurring options then that too would be wonderful. Nothing fancy, daily, weekly, monthly, yearly repeats - so that if I put a birthday as an event, it will at least automatically create a new Birthday event in a table after this birthday is marked as completed.

4

Yes, but calendar entries are not exactly the same things as tasks, which was the specific need you posted about. And I’m not the only one who thinks that there is no universal definition:
‘There’s probably not a consensus on what anyone “would expect [recurring tasks] to behave in normal project management tools"’

Anyway, my point was that Fibery has some technical foundations to which any solution needs to build upon.

There are things that are simply not possible in Fibery (based on its current foundations).
For example, if I create a recurring event in my Outlook calendar, I can choose to have the recurrence be indefinite (no end date) but it would not be possible in Fibery to have a indefinite number of entities in an ‘event’ database.
And since Fibery does not have array field types, a single entity cannot contain a set of 1-to-∞ date values to represent all the recurrence dates it should be associated with (and even if it could, this would not be the same as having unique entries for each date).
So … :person_shrugging:

But putting all that aside, I can see that you commented on the post that @helloitse made, which covers this case, so I have followed her guidance and made a workspace that implements something close. Perhaps it’s useful, or can at least inspire you to figure out a solution that gets you what you need.

3 Likes