Assignee doesn't copy from parent

[Endre Kallai]

Hi there,

I have created this automation rule where my intent was that the sub-task created within the parent card would automatically assign any sub-tasks created to the assignee of the parent issue. 

The first 3 steps seem to work fine but execution fails on the final step. Apparently, it doesn't recognise the parent issue - says no parent found...

I'm not quite sure where I went wrong. 

Could anyone have a look and suggest a plan of action, please?

Best wishes,

Endre

[Kian Stack Mumo Systems]

According to what you've shown here, you say "copy assignee from trigger issue". But the trigger issue is the issue you just created, which according to your conditions needs be have no assignee. 

Change the final action to Copy from parent. 

[Endre Kallai]

Yeah, I know. originally it was 'Copy from Parent' and I still received the same message. I'm not sure why for I have created the sub-task within the card of the parent task issue.

[Kian Stack Mumo Systems]

Well the audit log before showed that 527 didn't meet the conditions you set forth. Can you confirm that 527 was a sub-task without an assignee?

Thanks,

Kian

[Endre Kallai]

@Kian Stack Mumo Systems oh, yes. You see, I have created the sub-task with no assignee to see if it copies automatically. I have just changed the action from assign issue to edit issue field as in your screen shot. Created a new issue, assigned it to myself then created sub-tasks. Checked the audit log, it's confirmed that the automation rule has been executed successfully but the subs are still unassigned. Not sure what went wrong this time:

[Kian Stack Mumo Systems]

@Endre Kallai, I apologize, I did not mean to imply that you should use the "Edit Issue action". I was just trying to illustrate that the final action should be copy from parent.

I'm afraid I'm still not quite sure what's going on. The audit log you are showing refers to DXON-541, but you're showing me screenshots of DXON-539 and DXON-540.

[Endre Kallai]

@Kian Stack Mumo Systems Yeah, I'm not sure what's going on either. So I created DXON-539 as the parent task assigned to me. DXON-540 and 541 are the sub-tasks that meant to take on the assignee of the parent as I have created them but it's not happening. 

I hoped that the Edit issue action would sort the situation but no luck. The problem in both cases - DXON-540 and 541 - are the same. They remained unassigned...

What else do you think I should change? To me this seems like a pretty straight forward automation rule but yet it is not doing what it's meant to.

If you have any more suggestions, I am happy to hear you out. If you build the same automation rule, does that work for you?

Thanks again.

[Kian Stack Mumo Systems]

@Endre Kallai, these configurations work for me!

[Endre Kallai]

@Kian Stack Mumo Systems I have the exact same setup. Audit log claims that rule has been executed successfully but sub-task is still unassigned. Still not sure what could be wrong. Should I raise a ticket for Atlassian Support, you think? Or do you have any suggestions what could've possibly gone wrong, please?