# New Extension type - Checklists

**URL:** <https://community.fibery.io/t/new-extension-type-checklists/530>\
**Category:** Ideas & Features\
**Created:** [January 23, 2020, 11:04pm UTC](https://community.fibery.io/t/new-extension-type-checklists/530 "2020-01-23T23:04:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**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 25, 2020, 4:44pm UTC](https://community.fibery.io/t/new-extension-type-checklists/530/4 "2020-08-25T16:44:46Z")

</div>

Hmm, I’m still not clear on why this is better than sub-tasks, or at least enough of an improvement to justify the added UI/UX complexity. Is it just that sub-tasks seems “heavier”?

Right now nothing can “contribute” to done status of another entity, but Automations may allow sub-tasks to affect parent task completion state in the future.

In any case perhaps Fibery team sees the benefit even if I don’t. 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.

I’d love it if Fibery allowed in-line dates with reminders too, like Notion and Quip. That’d solve your date issue then. Speaking of which, I’ve just added a feature request for this: [Ability to add in-line dates w/notifications (rich text, documents, comments)](https://community.fibery.io/t/ability-to-add-in-line-dates-w-notifications-rich-text-documents-comments/917)

Which raises the question: what if you can get 90% of the functionality you’re talking about here (as outlined above), but using features that are separately usable, rather than dedicated checklist functionality? Would that be good enough for your need?

---

_[View the full topic](https://community.fibery.io/t/new-extension-type-checklists/530)._