Copy Selective Components to Subtask

[Tejas Patil]

Hi Team,

I am trying to create an manual automation to create subtask based on components.

Lets say Current issue has Component A,B,C,D,E,F.

The automation I am trying is: If Trigger issue / Current issue has any of A,B,S,W,Q components (sequence can be any) , then create one subtask with available / matching component. So in this case it should create one subtask with components A & B.

Thanks

[Arkadiusz Wroblewski]

Hello @Tejas Patil 

As Corrected from @Marc -Devoteam- -

My approach isn’t suitable/Contextual don´t fit Into Cloud in this case and don´t wanna provide wrong Solution. I’ll evaluate the solution when I have a free moment.

[Marc -Devoteam-]

Hi @Arkadiusz Wroblewski 

Please stop using AI answers, your part in 3b doesn't exist, you can't target an issue in the edit action.

[Arkadiusz Wroblewski]

Hi @Marc -Devoteam- 

I didn’t use AI for that.

You’re right for native Cloud Automation: Edit issue can’t target another issue by key  it only edits the issue in scope. The reason it “feels possible” is that in Data Center (or with apps like ScriptRunner) ( and im steel Deep into Hybrid between Data Center and Cloud with many Migration going on) you can update any issue programmatically, including newly created subtasks. In Cloud native Automation, you need to either set the fields during “Create sub-task” or branch to “Most recently created issue” and then edit within that scope.

I checked that Twice now. You correct.

Thank You. My wrong. After Years still Learning.

[Arkadiusz Wroblewski]

@Marc -Devoteam-  @Tejas Patil 

As promised. The most reliable way I can think of is doing it with a trigger + an IF condition, then create the sub-task, and after that use a Branch rule (Related issues → Most recently created issue).

Inside the branch you just add a few small IF blocks to copy only the matching components from the parent.

If you want fewer blocks, you can also do it via Advanced field editing (JSON) (“More options”) on the create/edit action, using the same JSON format as the Jira REST API but honestly the IF-block approach is usually the easiest to maintain in Cloud and not demand from you JSON knowledge.

Here Atlassian Documentation about advanced-field-editing https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ 

[Bill Sheboy]

Hi @Tejas Patil 

This may be done by creating two lists of components, finding the overlapping values, and finally using list iteration to build an advanced edit with JSON expression to add the desired components.

Please see this article I wrote describing how to find the overlaps between two lists of items:

https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Find-Overlaps-Between-Lists/ba-p/3045704

Kind regards,
Bill

[Marc -Devoteam-]

Hi @Tejas Patil 

I don't think this is possible, as there is no dynamic lookup in automation.

Based on how many possible combination are we discussing this.

You might can create a lookup table based on possible option and create an issue based on the lookup table value to fill the component field.

@Bill Sheboy any thoughts from your end?