Configuring automation triggers between two or more sub-tasks

[Italo Gonsalves]

When creating tasks I will have multiple sub-tasks within that task. I'm trying to accomplish the following. 

-When sub-task (A) status transitions to DONE.

TRIGGER

-Currently unassigned sub-task (B) with specified assignee.

*Each sub-task involved has a unique "issue type" and "workflow" associated. 

Current automation rule is as follows. 

-When: Issue transitioned FROM (X) to (DONE)

-If: Sub-task present

-And: Issue type = (Y)

-Then: Assign the issue to (Z)

I gather since the automation is working by a direct parent>child rule its not acknowledging sub-task (B) as (B) isn't the child of sub-task (A).

Is there another way to accomplish this? 

[Italo Gonsalves]

Ok thank you for all of your help John!

[John Funk]

Hi Italo - Welcome to the Atlassian Community!

Is there some type of established relationship between Sub-task(A) and Sub-task(B) since it appears that they have different parents?

[Italo Gonsalves]

Thank you John! Great to be here.

They are both Sub-tasks of the same parent Task. 

I'm trying to leave (B) unassigned until (A) status changes to DONE at which point (B) gets an assignee. The assignee's start work as soon as they get their Sub-task assigned. 

The main Task represents a fulfillment work order. The Sub-tasks are situational and are created manually when the main task is created. Some Sub-tasks auto assign when created based on post function triggers. Some Sub-Task need to wait until a previous Sub-task is completed to be assigned and due to their situational nature I'm not able to merge the two Sub-tasks into one workflow.

I created several unique Sub-Task issue types, each with unique workflows. 

Thanks for the feedback!

[John Funk]

So something like this:

A transitions to Done.

B is then given an assignee (is specific name is included in the automation or is the assignee based on another field?)

Is B then automatically transitioned to a new status?

Do you have the rule created already? If so, can you share it?

[Italo Gonsalves]

Yes sir. Yes the specific name is included. (B) does not transition to a new status. It remains in OPEN status. 

The rule is as follows:

When - Issue Transition: From POS training to DONE

If - Related issues condition: Related issues = Sub-tasks > Condition = Are present

And - Issue fields condition: Field = Issue type > Condition = equals > Issue type custom NAME

Then - Assign issue: Assign the issue to = Specific user >select user = Italo Gonsalves

[John Funk]

Sorry for the delay in responding. Is the above process working for you? Or are you getting an error or it just doesn't work?

[Italo Gonsalves]

Hi John. It just doesn't work. 

I need some way to relate both sub-tasks to the parent main task. Since Jira issues a unique ticket number to all tickets whether main task or sub-task I'm having a hard time associating the family of tasks together. 

Furthermore I'll want to make sure that if I have multiple main tasks w/ children sub-tasks that have "status changes" which trigger automation, those triggers are staying within the unique family of tasks. I wouldn't want the status of (MT-21) transitioning to DONE to trigger (MT-32) to assign user. 

example: 

MAIN TASK (jira ticket#) = MT-20,

Sub-Task (A) (jira ticket#) = MT-21,

Sub-Task (B) (jira ticket#) = MT-22,

-Family of Tasks for (jira ticket#) MT-20-

MAIN TASK (jira ticket#) = MT-30,

Sub-Task (A) (jira ticket#) = MT-31,

Sub-Task (B) (jira ticket#) = MT-32,

-Family of Tasks for (jira ticket#) MT-30-

[John Funk]

So you want to be able to link MT-21 to MT-22 for purposes of doing some automation to one or the other?

[Italo Gonsalves]

Yessir. That is correct. 

I attached the audit log details below. 

[John Funk]

That's a little bit complicated.  :-)

What about something like this:

[Italo Gonsalves]

Thank you John! Sorry for the long delay.

I feel like this is getting me closer to the goal. It didn't quite get me there yet.
The automation is now failing here.
{{triggerissue.parent link}} = {{issue.parent linkl}}
Is there something specific that I should reference here?
The trigger issue is Sub-Task (A)
Thank you!

[John Funk]

Can you provide more information about the failure? What does the Audit Log say? Also, have you verified that the parent for both the issue and the trigger issue are the same?

[Italo Gonsalves]

Hi John,

 Yes the Parent is the same I attached the parent ticket example with its sub-tasks along with audit log.

Parent ticket = PS-117

Trigger Subtask ticket (New) = PS-122

Target Subtask ticket (Digi$shield) = PS-123

[John Funk]

Is the issue type actually called DigiShield? Or is that just the name of the ticket (the value for the Summary)?

[Italo Gonsalves]

Hi John, It is actually called Digi$hield. 

I created a new subtask type and named it that.

[John Funk]

I would go ahead and submit a support ticket with Atlassian. Then please post back here what the resolution was. 

https://support.atlassian.com/contact/#/

[Jillian Amyot _Unito_]

Hi @Italo Gonsalves ! Check out Unito, where you are able to sync the two so when it becomes finished in one category it gets sent to the next. Here is a link that might help you :) 

https://unito.io/jira-sync/