# Next iteration of Comments - Commenting when Resolving & assigning as tasks/reminders

**URL:** <https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527>\
**Category:** Ideas & Features\
**Tags:** comments\
**Created:** [January 23, 2020, 6:28am UTC](https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527 "2020-01-23T06:28:34Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**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:** [July 21, 2020, 7:00am UTC](https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527/3 "2020-07-21T07:00:05Z")

</div>

Yes great points!

That is why I think one specific way this can be handled is when resolving a comment, simply prompt for another “closing” comment, so it’s possible to see what was done to resolve the conversations. TargetProcess in fact has a great feature where you can configure workflow transitions to require a comment, that would be terrific to see in Fibery!

This is also what I had in mind with this suggestion:

> [@Workflow Extension: Require comment on close; Multiple types of "done" status](https://community.fibery.io/t/workflow-extension-require-comment-on-close-multiple-types-of-done-status/849):
>
> Hi guys, I wanted to suggest two additions to Workflow that would really help me out. Again would love to get feedback from the “regulars” of @Jean, @helloitse, @chris.burchartz, @ChrisSparkT, and anybody I forgot (no offense intended!) Require comment on “close” status. Many of us are familiar with issue tracking tools like Jira, and this is a very useful feature. With this, you can make sure that closed entities that are being used for process management like Bug Tracking, Feature compl…

With a feature like this, you could even use entities as “mini conversations” like in the Twist example I showed above. If you required a comment when moving to “closed” state, you can then be sure that those that are resolved have traceability as to what was done.

---

_[View the full topic](https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527)._
