First, it is a clearly stated issue, so no elaboration needed.
- make one task node (in progress)
- make two tasks in there, one for the developer, one for the QA
- create two screens, one for the developer, one for the QA
- have each screen have just a subset of the transitions
hey, maybe you should not even use one state, but a fork, parallel task nodes and a join. Mixing up the higher level state of a case and indivual 'task' can make things more complex than they realy need to be.
Cancelling things in a process is often needed in multiple places. I personally do not model these as state/task, just separate pages, more like a case manager. The same is (imo) true for reassignment things. Only if an assignment step is explicit, we put it in the model. Otherwise it is a separate action on
Thanks for your prompt response. I believe that this is what I was looking for.