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)?
Parent workflow (TODO / IN PROGRESS / DONE)
* Do desing
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.
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.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events