# "Due Date" type of Date option - perhaps Extension? **URL:** \ **Category:** Ideas & Features\ **Tags:** automations\ **Created:** [May 21, 2020, 1:51am UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712 "2020-05-21T01:51:19Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [May 21, 2020, 1:51am UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/1 "2020-05-21T01:51:19Z")
Hi Guys, As I move forward in Fibery, I am realizing more and more that unlike some of the other “nocode” stuff like Airtable, Notion, Coda, etc., Fibery shines in that it is built for Work Management, unlike those tools. You guys have some features here that are geared towards that, **such as Workflows**. In those other tools, there is no such concept. But this is a big benefit with Fibery as Workflow is such an essential piece of Work Management I have found that I can see a need again and again for another essential part of Work Management - the concept of a **due date**. Currently you have to use filters and colors to show an entity is overdue. I think if you guys could build in a little more native handling of a “due date”, there would be great use here. This could firstly bring simple viewing across all areas of Fibery overdue items, very important. Down the road with dependencies and other features connected with planning, due dates would be very useful. Hope that’s helpful guys and curious to get your thoughts on this! ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [August 24, 2020, 7:44pm UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/2 "2020-08-24T19:44:11Z")
I think another critical part of “due date”-type functionality would be notifications. Currently notifications are quite limited, no date-based ones as far as I’m aware. Certainly due dates should tie in to notifications, then. In fact I would think that would be one of the core aspects of it. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [August 25, 2020, 4:50am UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/3 "2020-08-25T04:50:48Z")
This is great @Oshyan and thank you for the comments lately! This is part of exactly what I was thinking with this “built out” concept of a Due Date inside Fibery. I think one of the greatest things @mdubakov and co. are on to is the approach of having “extensions” (which I often think of actually as “apps”) you can add in to the general structure, which is otherwise more or less an open canvas. You can add as you please, but don’t need to. It is very powerful _not_ to be forced into having a Workflow. I have been using Entities as Docs, and I don’t have a workflow on them most of the time as that’s not needed for this type of Entity. But in a tool like ClickUp or Wrike, you have to have these pieces, and it gets awkward. This is where Fibery differentiates from the likes of Coda, Airtable, and Notion. In those tools you simply have a “date” field, or a “person” field, but in neither case can you expect certain typical behavior for Work Management tools like notifications as you point out. By building functionality around the existing Extension library, Fibery is solving this. If you want a plain “date” column for some reason, and don’t want to associate it with Due Dates, you can have that. If we had a “Due Date” extension though, like we have Assignments, you could choose what suits you best. @helloitse it occurs to me that this is a subject that would interest you, so would love to get your take as well! Thanks again! ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 30, 2020, 11:43am UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/4 "2020-10-30T11:43:08Z")
We have this in plans for sure ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [November 7, 2020, 7:25am UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/5 "2020-11-07T07:25:51Z")
This is great to hear, thanks for the update! ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [December 20, 2020, 11:02pm UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/6 "2020-12-20T23:02:15Z")
This continues to be a pain point as my team gets bigger in Fibery, would love to know if you guys have any guidance on when this might come around? I’m not sure how many users are trying to do hard core Task/Project Mgmt with Fibery, in which case you really need a concept of “overdue” and some notification capability around that. Right now all I can do is color Overdue stuff differently on a board (but with the limited “line” which I think my team easily ignores, which highlights the need for this [feature of Colored Cards](https://community.fibery.io/t/aproved-color-coding-of-entire-card-entity-not-just-bar-of-color/654) so the impact of a “red” overdue entity is as big as possible! Grateful for any info on when you guys would implement something like this - very happy it’s approved so at least I can hope it’s coming sooner or later! Thanks. ---
**Author:** ![Aj1215](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aj1215/32/3860_2.png) [@Aj1215](https://community.fibery.io/u/Aj1215)\ **Post date:** [July 16, 2021, 5:27pm UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/7 "2021-07-16T17:27:32Z")
Is this still a possibility/on the roadmap? ---
**Author:** ![v3j](https://avatars.discourse-cdn.com/v4/letter/v/f07891/32.png) [@v3j](https://community.fibery.io/u/v3j)\ **Post date:** [July 17, 2021, 8:37am UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/8 "2021-07-17T08:37:05Z")
Hi, I’m a novice Fibery user but just wanted to share an attempted workaround using the recently released Rules feature: 1. Create a “Days Overdue” formula field (Today - Due Date). 2. Create a label field “Overdue?” You can make the Overdue option red (other options can be “On Time”, and “Due Today”). 3. Create a rule so that whenever “Days Overdue” changes (which happens every day because Today is dynamic) AND due date is before today, then the label field “Overdue?” value becomes “Overdue”. Create equivalent rules for “On Time” and “Due Today” Here are screenshots of how I implemented this – **Rules:** ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/afc2451bb7d3058bd2b68764702b461b8eadc523.png) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a85dd8175c8be0c90d3f58e43227f389496ba098.png) **Table View:** ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/06ee744b275771a4e0ece689db5a696acd9a7779.png) **Board View:** ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d78f50eb98b6408da0cc4461e41711f47e26fa8c.png) You may also add a View Filter to hide “Done” items. Also, I wonder if you can add the “Send Email Notifications” action to this rule when it gets released: [https://fibery.io/blog/chronicles-34/](https://fibery.io/blog/chronicles-34/) * * * Please let me know if I overlooked anything~ ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [August 5, 2021, 9:39pm UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/9 "2021-08-05T21:39:09Z")
OK, so now that we have Notifications through Automations, and we can create calculated value fields to trigger such notifications, how much are we missing from dedicated functionality for this? @mdubakov on a strategic level is this kind of specialized date-related functionality something you have interest in implementing (even if not short-term)? Or are you more intending to meet such needs with the combination of more flexible features like Formula Field + Automation + Notifications? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 5, 2021, 10:11pm UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/10 "2021-08-05T22:11:51Z")
> [@Oshyan](#): > > how much are we missing from dedicated functionality for this? I think any reasonably desirable date-driven notification can be achieved with the functionality that is now available 🥳 I can imagine that some users may want notification some days before the due date, others when the date has passed, etc. so I suspect that any native due date functionality would end up needing to be configurable, at which point, it’s probably almost as easy to configure using automation (provided users can be helped to figure out how 🙂 ) Maybe there is a future for ‘functional templates’ (not templates for types/relations but templates for combinations of fields/formulas/notifications) that serve a specific purpose like this, but which can be added to any type… The [stuff I did in relation to task dependency](https://community.fibery.io/t/project-task-dependencies/1798) would be another example, maybe… ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [August 5, 2021, 10:30pm UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/11 "2021-08-05T22:30:09Z")
Yeah, I was kind of thinking the same thing, and that maybe this could be Closed. I just want to make sure I’m not forgetting anything important, heh. I agree that some kind of “templates” (or “saved config”?) for Automations that can be reapplied/reconfigured in different Types would be helpful. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 5, 2021, 10:50pm UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/12 "2021-08-05T22:50:53Z")
Nicely done > [@v3j](#): > > I wonder if you can add the “Send Email Notifications” action to this rule when it gets released: [#34. Thinking about the Next Big Thing in Fibery in June 2021](https://fibery.io/blog/chronicles-34/) > > Please let me know if I overlooked anything~ Notifications in automation is [available now](https://community.fibery.io/t/changelog-august-5-export-document-or-entity-to-markdown-notify-people-action/1884) 👌 I will just add that it would also be possible to get a daily reminder of overdue items by creating a rule that triggers each time the ‘Days overdue’ number field changes (and is a positive number). Some people might get a bit sick of that though 😉 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 6, 2021, 7:02am UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/13 "2021-08-06T07:02:14Z")
So far notifications are global, but I believe people will want to have they own private notifications, so not sure this should be considered done. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 6, 2021, 7:13am UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/14 "2021-08-06T07:13:52Z")
But it’s possible using automations to send a notification to only the assignee(s) for example, isn’t it? ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [August 6, 2021, 1:55pm UTC](https://community.fibery.io/t/due-date-type-of-date-option-perhaps-extension/712/15 "2021-08-06T13:55:22Z")
Oh, that’s definitely true then! I haven’t tested it quite yet. 😃