Automation - Story with subtasks does not get updated

[Laura Hanna]

I have two automation rules.

One rule, creates

Story 1

story 2

story 3

   3.1 subtask

   3.2 subtask

   3.3 subtask

My second rule, will update ALL stories when due date is changed in Story 1.

All Update except the subtasks under story 3. 

All stories are linked "as child" to Story 1.

But, the sub tasks are sub tasks. If I try to link in automation, I have the choice of trigger (story 1 or "most recently created issue" .

So in essences 3.1 would work. It would link as child to Story 3.

But, if I do the same for linking 3.2 it would link as child to 3.1 and so on...

So when I try to do a due date update on ALL stories listed under Story 1 including subtasks. Only the stories are updated. I also tried "for linked issues" where type is subtasks. This does not work either.

Rule 1

Rule 2

[Trudy Claspill · Accepted solution]

Hello @Laura Hanna 

I see that you tagged your question as jira-cloud, but the images you shared look to me like the Automation feature within Jira Server or Jira Data Center. Can you confirm which hosting type you have? If you are using Jira Server or Jira Data Center you will be able to find Jira application version information at the bottom of screens accessed through the Dashboard menu. If you find that version information please share it.

Following that, my second question is why have artificially created a parent/child relationship between issue of the same type (Story)?

My third question is why are you create an addition generic link between the Sub-task and its parent issue? The parent/child relationship between its subtask and its parent issue is native Jira functionality and does not require the use of generic issue linking.

The remainder of my answer is based on Jira Cloud functionality. I have not confirmed that the same functionality is available in the Automation features for Jira Server or Jira Data Center.

Disregarding that, looking at your Automation Rule you appear to be using the Create Issue action to create the Sub-tasks. Instead you should be using the Create Sub-tasks action. This will properly link the new Sub-tasks as subtasks of the Story.

Next, I would recommend you create a separate rule to handle updating the Due Date of Sub-tasks when the Due Date of their parent issue changes.

[Laura Hanna]

My apologies, I am "new" to the game... And my terminology gets mixed up sometimes...

Yes, we are using "Jira Agile" that is what the "about" states.

I did use the "create sub-tasks" option. But, as soon as you start adding more then one field to add to the sub task, it starts to separate the sub-tasks to look like I presented.

And they all link together, I think I may have figured it out, as you state, make "its own" rule for the sub tasks.

Thanks I will work on this today.