I've several projects that share the same workflows.
Among them, there is one called "Dev lifecycle" that has a state machine rule.
There are other project with similar workflows, however, the "Lifecycle" rule is slightly different.
Both rules share many transitions, so when I update one, I often need to update the other.
I was wondering if I could create a third workflow, with just a state machine rule that has all the shared transitions.
What blocks me however is the "initial state", as this is supposed the first state when submitting the ticket.
Instead, in my case, it should be considered the initial state from where all the transitions should follow.
Meaning that the ticket might be submitted with a different state, but the rule must start working only when ticket reach the initial state.
So, to make it cleared and using a realistic example, we have two life cycles:
The both have the same lifecycle:
- In progress (*)
- Won't fix
(*) Development need to also go through these states after it change to "In progress" (that's just a shor version):
- Fix proposed
- Fix approved
- Tests needed
- Tests passed
- Test failed
- Test needs improvement
- Fix declined