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

Since we already have some good support on this one from @Chr1sG and @Matt_Blais , and I imagine @rothnic as a dev-focused user in here, I wanted to point out a good post I have often dreamt about becoming reality - this is an older one as a veteran in here I recall from a good while ago: …

Nice, I’m glad there’s support for this way of thinking :slight_smile: I just know the TargetProcess name, I’m not familiar with how it works. I’d like to stress that I’m not thinking about boards in particular though. These are primitives that are fundamental to the content system. Workflow is …

I’ve actually been chatting with Anton about my needs for permission-driven workflow/states, and he indicated that work on it would be dependent on demand (as is to be expected) so I’m hugely relieved to hear enthusiasm here from others. Having said that, I also know, from some of the posts that Mi…

[image] jean1: I’m aware that really none of the current popular platforms have anything like this complete and flexible a workflow/security model. I think Jira Next-gen projects (now renamed to ‘team-managed’ projects) have nearly exactly what you were originally asking for: [image] …

It looks like Jira supports fairly sophisticated workflows, but does it enforce permissions according to role (and thereby to users/groups)? I don’t have a great deal of experience with Jira and I don’t want to sign up just to answer this :wink:

Yes, that is one of the rules you can apply: [image] [image]

There are a few basics in Jira, like workflows, and conversion of Entity I talked about here that I really hope Fibery can come close to duplicating. Right now though, both the workflow extension, and converting between types, is a long way from what Jira has. And these are two huge pieces needed …

[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. https://community.fibery.io/t/proper-workflow-states…

Workflow states should have multiple checkpoints, to monitor progress. for example bake cake state would have order ingredients , bake cake. deliver cake would have book collection, collected, delivered. but the ability to monitor progress in a non linear way would be very useful. e.g. you could boo…

That sounds like tasks with dependencies, right? The tasks (order ingredients, bake, deliver) would each have a state (pending, in progress, completed) and then you would want to implement dependencies, e.g. so that bake could not enter the ‘in progress’ state if order ingredients was not ‘complete…

Proper workflow: States, Transitions, etc

Ideas & Features

Chr1sG September 7, 2022, 8:16am 9

Topic		Replies	Views
Invitation to users wanting improved workflows News & Announcements	15	1097	May 31, 2025
Workflow Extension Enhancements for Advanced Dev Teams Ideas & Features	6	1781	September 7, 2022
New template - Advanced workflow News & Announcements	20	885	October 20, 2022
Kanban board details - WIP Limits Ideas & Features board-view	16	2486	August 21, 2025
Conditional Buttons to transition entities through states Get Help	3	855	July 17, 2023

Proper workflow: States, Transitions, etc

Related topics