Automation zwischen Subtasks

[Simone K_]

Hallo, 

Ich stehe aktuell vor folgendem Problem:

(Company-managed Projekt)

Es existiert bereits eine funktionierende Regel Nr.1 die Bei Erstellung von TASK X

unterschiedliche Subtasks erstellt (Subtasks wurden zuvor als Vorgangstypen angelegt):

Sub-Task A

Sub Task B

Sub-Task C

Diese Sub-Tasks sind ursprünglich keiner Person zugewiesen.

Nun möchte ich eine zweite Regel erstellen die folgendes bewirkt:

Wenn Sub-Task A erledigt ist, dann weise Sub-Task B der zuständigen Person von TASK X (= Parent von Sub-task A und Sub-Task B) zu.

Ich finde einfach keine Lösung hierzu, Kann mir hier jemand helfen?

[Bill Sheboy]

Hi @Simone K_ -- Welcome to the Atlassian Community!

Will the subtasks all be assigned to the same person originally assigned to their parent Task?  If so, could the subtasks all be assigned when they are created?

If not, how do you know which subtask is next?  That is, which one is "Subtask B"?

If it is always the same subtask, based on some criteria, your rule could use branching and then assign the task.  For example:

• trigger: transitioned to "done" (or your completed status)
• condition: issue type equals subtask
• branch: on JQL to find the correct, next subtask with the same parent as the trigger issue
  • action: assign issue, selecting the options of
    • Assign issue to: Copy from another issue
    • Copy value from: Parent issue

Kind regards,
Bill

[Simone K_]

Hi Bill,

thanks a lot for your answer.

Will the subtasks all be assigned to the same person originally assigned to their parent Task?  If so, could the subtasks all be assigned when they are created?

No - just one subtask should have a specific Person which is responsable just at the time when Parentstatus changes.

If not, how do you know which subtask is next?  That is, which one is "Subtask B"?

which one is next depends of current Status from Parent.

The subtasks are predefinied as different Subtasktypes. ( Business Projekt)

If it is always the same subtask, based on some criteria, your rule could use branching and then assign the task.  For example:

• trigger: transitioned to "done" (or your completed status)
• condition: issue type equals subtask
• branch: on JQL to find the correct, next subtask with the same parent as the trigger issue -> Why do i have to use JQL? Because there is only One Subtask Type B defined. 
•  
  • action: assign issue, selecting the options of
    • Assign issue to: Copy from another issue
    • Copy value from: Parent issue