So just to clarify.. you have for example a Parent Task with 5 Sub-Tasks that are executed in specific order and you want to move the next one to In Progress when the previous is Done?
Yes exactly. There would need to be a condition though as may happen that sub-task assignee may be in Unassigned state so then obviously this can't progress without a valid assignment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would not be more natural to simply modify the parent workflow and since we cannot start sub-tasks simultaneously design it in a way that next status is the work that need to be done (currently defined in a sub-task)?
Example:
Parent workflow (TODO / IN PROGRESS / DONE)
Sub-Tasks * Do desing * Implement * Test..
so combining this to single ticket it would be
TODO / DESIGN / IMPLEMENTATION / TESTING / DONE..
I do not quite understand the idea of creating 5 Sub-Task on the beginning if we wait for previous state to be completed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh it's because they're completely repetitive. All that changes is assignees at different stages. It's not a software related project but rather an ongoing process where the same set of tasks is done for different clients so all that changes is the parent Epic name and as mentioned, the sub-task assignees. The transition is mainly to inform the next in row assignee to start processing as their clock started ticking.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.