Thanks and I meant to respond earlier!
Sorry to repeat myself but my best answer is what you see in the Clickup explanation of their various “closed” statuses that I listed above. Yes, I realize some of this would involve hard-coding by Fibery which I’m not sure is viable right now depending on how much work the team wanted to put into the workflow extension. I made this request back when Fibery was new and it appeared at the time that extensions might become a core set of Fibery that got build outs, but that hasn’t happened. Not sure even if the notion of the “extension” is well known right now in the community…same with “collections” which once upon a time was how you referred to the area in an entity where relations showed up.
The main reason I jumped back in here is because of @ChrisG reviving this post with the comment 18 days ago. Since I’d still enjoy seeing this feature, I responded not quite understanding what Chris meant. I would like to add in the spirit of the original post, that right now with discussion of required fields over here:
than having the ability to require a comment on close seems like something that would also be closer to reality than when I originally posted the request. Again, at the time, my thinking as you could add on an “extension” that would force a comment when closing an entity - which in turn would need to integrate with some recognition of workflow moving to the one of the “closed” statuses.
And thanks for the vote over in When clicking reference from a thread reply, open reply (currently doesn’t happen), another quality of life fix that would be great to see!