Hi Community,
I am seeking help to solving an issue today.
Currently we have an automation running where parent status changes based on a subtask status.
But for other reasons we would need to change the setup so parent + child becomes subtask to the same issue.
I do not see any opportunity for one subtask status change to change the other subtask status or I am missing the obvious connection that can make a automation run?
As the system does not support support parent + child + grandchild this seems to be the only way of keeping the automation with my limited knowledge.
Or do I need to run a JQL to solve it?
Thanks for all input
Hello @Jacob Kock Plinius
The default hierarchy for Jira is
Epic
|- standard issue types
|- subtask issue types
With the Premium subscription you can add to the hierarchy from Epic upwards, but you cannot add to the hierarchy levels below Epic.
If you need three recognizable levels in your hierarchy, you need to use the levels shown above.
You can, however, create an automation such that the change of Status on a subtask causes a change both to its parent standard issue and to 1..n of its sibling subtasks. The implementation requires that you have a way to identify the sibling subtask you want to change.
You might consider using a unique Link Type to create a link between the "parent subtask" and its sibling/"child subtask". Or you might consider having a custom field in the subtask where you enter the issue key for its "parent subtask".
With those methods there are different actions you can use in Automation rules to find the "child subtask" and make a change to it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.