# Workflow Extension Enhancements for Advanced Dev Teams **URL:** \ **Category:** Ideas & Features\ **Created:** [December 24, 2020, 7:13am UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266 "2020-12-24T07:13:27Z")\ **Posts on this page:** 7\ **Page:** 1
**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:** [December 24, 2020, 7:13am UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/1 "2020-12-24T07:13:27Z")
Hi guys, I really like the fact that in this early phase of Fibery, we already have a concept of “Workflow”, thanks to the extension, that has some nice handling that you don’t see in other Nocode, where generally you have to use a single-select Property in a Field to get Workflow. In Fibery we have an element of Conditional Formatting already built in if you think about it with “done” items both “graying out” on boards, and showing as “strikethrough” when referenced - terrific work with those both guys my team lives by those features of Workflow! Since we already have Workflow started with this specialized Extension, I’m hoping we can see this evolve with some more additions in the extension that would help Advanced Dev Teams in particular, here are some from this list: - More complex transitions. This is a key feature of Jira, and I believe TargetProcess, which are dedicated apps for development. So you can design which State can be chosen from a given state, multiple paths, etc. It looks like this in Jira: ![](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/aaa0eb03b96f176dfdece7679050ffe9a1b12c3b.png) - Workflow Buttons for quick transitions. Sometimes when working quickly it is very nice to have the ability to just “push a button” to move to the next State, or back into a previous State. Jira also has this , and it’s very useful: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/447e232d1b5bcb40e37a141a6d365962a30db26d.png) There are also some good posts around the community with some suggestions here: > [@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… > [@Create related issue on workflow transition](https://community.fibery.io/t/create-related-issue-on-workflow-transition/243): > > It would be great to have a possibility to create subtask/related issue on workflow transition. It would be possible to implement interaction between different departments on workflow lvl then. Regards, Simon Finally, @mdubakov described some great capability for Kanban that I hope will come soon, it’s laid out here: > [@Kanban board details - WIP Limits](https://community.fibery.io/t/kanban-board-details/328/7): > > @B_Sp Yeah, when we will create proper Kanban App in Fibery this should be done. In general Kanban MVP will require the following things: Cycle/Lead Time calculation Reports (CFD, CT distribution, CT change over time) Groups of States on a board WIP limits This type of sophisticated Workflow I suppose could be integrated into the Workflow Extension, or it would just be great to see that feature on matter where it resides. Thanks! ---
**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Post date:** [July 8, 2021, 1:02am UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/2 "2021-07-08T01:02:27Z")
I think this proposal is quite important for users with more complex workflows so I thought it is worth a bump for others to consider (unfortunately I’ve ran out of votes). I also wanted to add something this is related and hopefully a bit easier to implement. If we think it deserves its own separate thread, I’m happy to move it. I like the current state extension and find the UI and icons to be quite intuitive. However, I think @Dimitri_S excellent suggestion on providing some additional state super-types other than “final” would really enhance things: > [@An archive or failure Workflow state?](https://community.fibery.io/t/an-archive-or-failure-workflow-state/1650/1): > > Seems like workflows seem to be designed to go from 0% (not started) to 100% (done) > > … > > It can also have ‘super-states’ which may temporarily or permanently take the prospect out of the default state flow. Example: getting moved to **backlog** , or getting **closed** for various reasons @Polina_Zenevich suggested using “Final” for cancelled/rejected/closed states which technically works. But from a semantic and UI perspective, it might be better if you could mark these state conditions more consistently (i.e. these situations would be shown with an ❌ rather than a ✔). I don’t think the “final” state suggestion works for moving things into a backlog. Having backlog as the first state is a possible fix, but that messes with the progress “pie-chart” for rest of states which are truly the first steps in a workflow (e.g. Intake, Proposal, etc.). So it would be amazing to have a backlog as another state type with its own logo (e.g. ⌛) To sum up, per @Dimitri_S proposal, I think three super-states should capture most situation: - ⌛ **Backlog** : items that are backlogged or otherwise delayed and no immediate action is going to be taken - ❌ **Closed** : items that are rejected, cancelled or no longer active/closed - ✔ **Final** : items that are complete I know that you can chose your own icons and colours for each state. But I think that actually becomes confusing as the extension icons also appear. I also don’t want to do away with the progress icons because I prefer Fibery figuring out the steps in between rather than trying to find emoji’s for each step. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [July 8, 2021, 3:29pm UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/3 "2021-07-08T15:29:42Z")
I actually think it is sub-optimal to have the workflow states (or superstates) too strictly pre-defined, given that there could be just as many preferences as there are users 🙂 As an example, my preference for workflow states is sometimes Draft - Under Review - Reviewed - Approved - Obsolete and at other times is Pending - In Progress - Done. I would rather have the option to choose names/icons/colours and fallback values if no choices are made. And in a perfect world, each user could define their own workflow templates that can be chosen from for each type. There’s a related discussion here: > [@Allow custom colours (or shading) for workflow states](https://community.fibery.io/t/allow-custom-colours-or-shading-for-workflow-states/1442): > > In some cases I use the workflow states to indicate when an entity is progressing from ‘draft’, through ‘in review’ to ‘approved’ state. In these cases, it’s actually preferable that the ‘draft’ and ‘in review’ states are greyed out, and only the ‘approved’ state is shown in white (i.e. the opposite of the current functionality). Can we have the ability to customise the shading (or even the colours) of the workflow states. Also, although it is nice that there are little icons to represent the … And here: > [@Proper workflow: States, Transitions, etc](https://community.fibery.io/t/proper-workflow/1626): > > Workflow should consist of States and Transitions. States have Transitions. Transitions have Guards (conditions and permissions) and target States. Transitions can be triggered via a user action (e.g. button) if they have the required permission, or automatically if the condition formula is true. A Role has Permissions on an entity based on the State of the entity. Groups can have roles. Users can have roles, and they can belong to groups (inheriting the roles of the group). ---
**Author:** ![mgiammarco](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mgiammarco/32/4033_2.png) [@mgiammarco](https://community.fibery.io/u/mgiammarco)\ **Post date:** [December 17, 2021, 9:00am UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/4 "2021-12-17T09:00:22Z")
I have asked too in another thread proceess.st like features. Fibery is a nocode relational engine with several prebuilt “views” (kanban, list and so on). The default views are optimized for process management (scrum, kanban). We need some views to cover the BPM management like in process street. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [December 17, 2021, 9:39am UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/5 "2021-12-17T09:39:28Z")
> [@mgiammarco](#): > > We need some views to cover the BPM management like in process street. Having suitable views will not alone provide BPM capabilities. Fibery doesn’t currently support defining configurable workflows like tools such as process st do. The Fibery automation options are pretty good, but it’s not really the same thing. ---
**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:** [December 19, 2021, 5:07am UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/6 "2021-12-19T05:07:51Z")
> [@mgiammarco](#): > > We need some views to cover the BPM management like in process street. I think It would be great if Fibery could complete the features needed for good process management such as with process.st or another good app that does that, Pipefy. One improvement that I have found a continuing need for would be expansion of the workflow extension to include these great capabilities: > [@Kanban board details - WIP Limits](https://community.fibery.io/t/kanban-board-details-wip-limits/328/7): > > @B_Sp Yeah, when we will create proper Kanban App in Fibery this should be done. In general Kanban MVP will require the following things: Cycle/Lead Time calculation Reports (CFD, CT distribution, CT change over time) Groups of States on a board WIP limits A great specific use would be to have multi-levels, like TargetProcess has, so you can do things like define a “backlog” master State, and have sub-states under that such as “in planning” and “on ice” to differentiate stories that are not yet ready when doing software development, for example ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 7, 2022, 8:16am UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/7 "2022-09-07T08:16:46Z")
> [@Invitation to users wanting improved workflows](https://community.fibery.io/t/invitation-to-users-wanting-improved-workflows/3259): > > 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 like more sophistication. Without making any promises, I would like to invite users to get in touch if they have specific use cases in mind that cannot currently be achieved in Fibery. This may allow us to develop templates that might be useful, as well as helping us understand what functions/features…