← Back to context Comment by tgv 11 hours ago You implied all workflows, not just Jira. 3 comments tgv Reply pjmlp 11 hours ago And I stand by it, naturally it depends on the specific workflow engine how those features are exposed.Then we can split hairs about which one don't really support it, so that you want win Internet discussions about all not being all. bigbluedots 9 hours ago Well, you did say all. Is there a minimal set of exposed features that must be exposed for a workflow engine to be included? pjmlp 6 hours ago Conditions and state transitions, plus actions for side effects, obviously.
pjmlp 11 hours ago And I stand by it, naturally it depends on the specific workflow engine how those features are exposed.Then we can split hairs about which one don't really support it, so that you want win Internet discussions about all not being all. bigbluedots 9 hours ago Well, you did say all. Is there a minimal set of exposed features that must be exposed for a workflow engine to be included? pjmlp 6 hours ago Conditions and state transitions, plus actions for side effects, obviously.
bigbluedots 9 hours ago Well, you did say all. Is there a minimal set of exposed features that must be exposed for a workflow engine to be included? pjmlp 6 hours ago Conditions and state transitions, plus actions for side effects, obviously.
And I stand by it, naturally it depends on the specific workflow engine how those features are exposed.
Then we can split hairs about which one don't really support it, so that you want win Internet discussions about all not being all.
Well, you did say all. Is there a minimal set of exposed features that must be exposed for a workflow engine to be included?
Conditions and state transitions, plus actions for side effects, obviously.