Automation - Subtasks won't pick up Parent information (Next Gen Cloud)

[Jess H.]

Context: We're using subtasks for "bugs" when a Story didn't meet its acceptance criteria and I want to be able to move the parent story from "In QA" to "To-Do" when a new subtask is created, and I want that subtask to take info like assignee from the parent.

I feel like I've tried this a million and one ways. Everything I do fails because "There's no parent." I wrote a simple bit of JQL it has to pass to verify that the parent field is not empty. It passes that, then still thinks there's no associated parent to pull data from.

Any help appreciated.

[Daniel Eads · Accepted solution]

Hi Jess,

Unfortunately this is a known behavior with Automation and Next Gen projects. Our development team is aware of the problem and will be addressing it soon. You can follow along with the progress here: AUT-1297 

Cheers,
Daniel | Atlassian Team

[Jess H.]

There doesn't appear to be a way for me to mark myself as a watcher on that ticket =\

But thanks Daniel! I'm going to be doing a lot of automating for my next gen cloud project, so I'm sure you'll see me pop up again.

[onur]

Hi @Daniel Eads ,

I've just check the AUT-1297 it seems to be fixed but I'm still facing exactly the same issue. 

[Daniel Eads]

Hi @onur - I'd recommend opening a case with our support team at support.atlassian.com/contact so we can take a look at the logs for your site and see if something's amiss. Please include the name of the rule you're seeing this issue on when creating the support case. Thanks!

[Mikael Sandberg]

Hi @Jess H.,

Welcome to Atlassian Community.

Have you tried using an Edit issue action and set the assignee to copy from parent?

 

[Mikael Sandberg]

Also, have you tried checking the issue type is set to sub task by using the Issue field condition instead of using the JQL?

[Jess H.]

Hey thanks Mikael, I've tried both of those to no avail. It's saying its successful, but not grabbing the parent assignee in either case:

[Jess H.]

Just to be triple sure, I checked the parent and it does have an assignee ;)

[Mikael Sandberg]

Odd, I just created the same rule on my end and it successfully copied the assignee. If you look at the history (click the down arrow next to Comments under Activity) for the sub task, do you see an entry where Automation sets the assignee? 

[Jess H.]

Does it matter that I'm in Jira Cloud? Here's the history log.

[Mikael Sandberg]

Okay, that looks a bit different than mine, I'm on Cloud too.

Okay, so I think it is because you are using a next-gen project, I just tested it and get the changed the Parent instead of the updated the Parent entry in the history, and the automation rule is not copying the Assignee. Let me get someone from Atlassian to take a look at it.

[Jess H.]

[GoodWhale Admin]

Hi,

@Mikael Sandberg @Daniel Eads 

Though the issue was resolved. It seems like the problem continues to persist. Is there another possible reason for the "Copy from Parent" not working?

Automation:

- Trigger: Creation of Issue

- Condition: Created Issue equal Subtasks

- Action: Copy Label From Parent

Test:

- Click "+" to add subtask in a Parent Issue. (This is where I think the problem is as Subtasks created via this method might have the Parent added only after it is created?)

Outcome:

Success -> Audit Log -> "Can't find issue to copy from labels"