All workflow and orchestration engines are Turing complete, the whole purpose is to automate execution flows.

snemvalts 7 hours ago | parent | next [-]

How many of them can run infinitely? Or be re-triggered by humans to continue where they left off?

	▲	pjmlp 7 hours ago \| parent [-]
		Depends on how you code the workflow and transition state triggers.

▲

tgv 7 hours ago | parent | prev [-]

I don't think so. First, JIRA is not orchestration. Second, all workflow needs to do is associate some status with external information, and make it easy to manipulate those. You need triggers and rules, some thing like infinite counters, two stacks, a bidirectional tape, etc.

Prove me wrong!

▲

pjmlp 7 hours ago | parent [-]

Yes, and the rules engine is there when creating custom workflows.

https://developer.atlassian.com/server/jira/platform/creatin...

I also explicitly mentioned workflows on my comment.

▲

tgv 7 hours ago | parent [-]

You implied all workflows, not just Jira.

▲

pjmlp 7 hours ago | parent [-]

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 5 hours ago | parent [-]

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 2 hours ago \| parent [-]
		Conditions and state transitions, plus actions for side effects, obviously.