New Extension type - Checklists

[B_Sp]

@Oshyan all valid points. Let me clarify what I was trying to express earlier - sorry if it wasn’t clear - that I would put this down pretty far on the priority list. Just off the top of my head, I’d rank things like Recurring Entities, Time Tracking, Formal dependency handling, and other potential Extensions way ahead of this one!

I agree 100% that if you could incorporate some @mentoining recognition of blocks and this functionality from your post:

[Approved] Ability to add in-line dates w/notifications (rich text, documents, comments)

I would very much like the ability to add in-line dates with reminders in as many places as possible. The major examples that come to mind are any Rich Text Field, Documents, and in Comments (both Extension-type, i.e. Entity-level comments, and highlight comments). This is a feature that many other systems have, including Notion, Quip, and tools like Roam, and it’s very useful for when you want to be reminded of something specific to a document (or section of a document), or where creating a ful…

you would have a ton of what I am trying to accomplish here. I would love to see that Notion functionality here in Fibery, too.

I really like this suggestion:

@Oshyan

In the meantime you could consider using in-line @mentions for assignment of checklists already. That takes care of done/not done and assignee, then you just need date for a basic feature set.

Indeed, if you could bring this into some way to recognize a block with a combination of:

• the content in the Block itself
• the user who is being @mentioned
• The reminder you are suggesting

And if it is a “checklist” type block, perhaps this could be a specially treated function so it might show up on a future Dashboard.

Until then though, this would certainly be a good solution if we could add in reminders that would roll up into Notifications, perhaps incorporated into Due Dates we have been discussing. And I fully agree with your discussions lately around the need for stronger Notifications. The lack of Notifications and Activity Stream as really held back my use of Fibery, since these are such key needs when a team is using Work Management software.

Finally, I will also go so far as to say that in some cases, for some more complex Acceptance Criteria or QA stuff, I have created a separate type of Entity already in my Fibery Instance that I have as a sub-Type to my generic “Dev Task” in my Software Development workflow. So in this case, yes I agree a “subtask” entity can be more important.

Really hoping over time to see some good flexibility with these Work Management-centric “add-ons”. I really think Fibery can continue to be more useful to teams than AirTable/Notion/Coda with development of these badly needed features that are essential to team function.

Thanks again!