In my previous post I explained how jira automatically manage the movement of the parent issue.
I analyzed it deeply and here I am with other details.
Before I said that the parent issue must have been in progress in order to allow jira to move it automatically. I didn’t pay attention to default jira behaviour because using the simplified workflow, jira automatically moves it even though the parent issue is in TO DO status.
This made me crazy and I started struggling trying with different workflows and here the result.
What I said in the part1 is the main key:
The parent issue workflow status must be set in the last column, when all subtasks are moved to the last column, Jira checks if the parent issue workflow allows the parent issue to move from the current status to the first status available in the last column of your board.
Here my board configuration:
Here my simple subtask workflow:
Here my previous parent issue workflow that doesn’t allow me to move the parent issue from TO DO to TO DEPLOY, but the parent issue must be set in progress:
Here my new one that allows jira to automatically move the parent issue from TO DO to TO DEPLOY:
Notice the link between TO DO and TO DEPLOY, this is the magic link that leads this behaviour.