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 familia…

[image] Invitation to users wanting improved workflows News & Announcements We know that the current workflow implementation is simplistic, and given that there are quite a few topics here that relate to workflows, e.g. …it seems like there are plenty users who would l…

[image] B_Sp: Multiple “done” types of status. My main point here is that I’d like to distinguish in Fibery between things that get “done,” but perpetuate in the system. Workflow field allows any number of ‘Finished’ states to be defined.

Ok could you provide more detail Chris? What I was referring to was the ability to have multiple kinds of “done” entities that have different treatment. For example, if I have a set of vendors I work with, say CRM providers. I move to a new one from a previous provider. I’d like to have this one…

What I meant was that there can be more than one state which is ‘Finished’ [firefox_uLbUIx16Yn] and you can choose whether or not finished items show up in search. So potentially, you can use the finished states for things that you are not typically wanting to work with so much in the future. If…

Thanks for the response. Yes I was looking for multiple “done” states that would have different handling. I’ve seen this in other apps, notably Clickup. You are explaining what I already know - and unless I’m missing something, Fibery treats everything that is “done” the same. Granted there can …

I’m still not sure I get the request. Is it that you want to add more categories beyond ‘Not started’, ‘Started’ and ‘Finished’?

No I would like to have different types of “done/closed/finished” items. As I mentioned in my use case, we are tracking all kinds of things in Fibery and some of them would be useful to mark in a non-active state. To continue with my vendor example, this might be “no longer using.” I’d like to tr…

That does sound like you want an extra status group beyond the existing one (Finished). Or I am truly too dumb to get your point :grimacing: [image-3 (1)] vs [image]

Haha, yes that’s right! I realize this is going to be low priority for you guys, but I’m a huge fan of a workflow that can do a lot of various things within an app. The one in a version of TargetProcess I analyzed some years back, that I think @mdubakov may have actually been around to author, was…

What is the functional implication of the additional status category, e.g. of “Closed” vs. “Finished”? What do you do with it that you can’t do by just adding more options to the Finished category: [image] I’m not saying there isn’t a distinction, I’m just not clear on how you’re actually using/a…

Workflow Extension: Require comment on close; Multiple types of "done" status

Ideas & Features

Chr1sG September 7, 2022, 8:17am 2

Topic		Replies	Views
Workflow Extension Enhancements for Advanced Dev Teams Ideas & Features	6	1784	September 7, 2022
Assignee Specific Workflow Ideas & Features	25	1686	October 6, 2022
[DONE] Seeing "Closed" Entities grayed out in Search Dialog Ideas & Features search	19	2547	June 1, 2023
June 26, 2025 / My Work Widget on Home Page Changelog	31	728	July 8, 2025
Feb 22, 2024 / State types, resizable Timeline lanes Changelog	14	673	February 26, 2024

Workflow Extension: Require comment on close; Multiple types of "done" status

Related topics