Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation copy from parent not working Edited

Hi

I am trying to implement a simple automation rule and I can't figure out why it's not working. 

My goal it to set this up so that if you just create a subtask it will by default apply the same tags, due date, assignee, etc, as the parent issue (either an epic, or regular issue).

I thought this was very straight-forward and just set up the following:

When: Issue Created 

Then: Edit fields –> 

–> and for each field I have selected, "copy from parent"

 

What could I be doing wrong?

 

Edit: additional information.

 

Here is a screenshot of the automation rule that I created. If I look at the rule audit, it says that it executes successfully but, "Can't find issue to copy from"

 

Screenshot 2020-07-06 12.29.15.png

1 answer

1 accepted

0 votes
Answer accepted
John Funk Community Leader Jul 06, 2020

Hi Evan - Welcome to the Atlassian Community!

Can you share a screenshot of your rule? And the error you get?

Thanks! I know I have a lot to learn, but I'm excited to get going!

 

Here is a screenshot of the automation rule that I created. If I look at the rule audit, it says that it executes successfully but, "Can't find issue to copy from"

 

I feel like this should be simple compared to everything else Jira is capable of, so it's making me feel silly that I'm struggling. 

 

Screenshot 2020-07-06 12.29.15.png

Hi, @Evan   -- Did any of the fields copy from the parent? 

Also, please consider adding a condition after the trigger to ensure that the issue type is a sub-task.  Otherwise, other issue creates will attempt to process this rule's copy fields.

 

Hi, @John Funk  -- This is the second post today I have seen for automation rules using the multi-field edit syntax, and the values do not copy from the parent.  The other one did not copy an epic's fields to a child story.

 

Best regard,

Bill

Simeon Ross Atlassian Team Jul 06, 2020

Hi @Evan ,

The advice that Bill gave you is correct. I would have a guess that the issue that failed your rule wasn't a sub task and so we couldn't find the parent issue because there wasn't one. The best thing to do here is to add an issue condition that checks it is a sub task before trying to edit. 

Like so:

issuecondition.png

Cheers,

Simeon.

Simeon Ross Atlassian Team Jul 06, 2020

Hey @Bill Sheboy ,

With the other one that you saw, was it also issue created? If so, they might need to add a refetch action to the rule. Occasionally we can get an issue from Jira that was created but the epic has yet to be set on it and a refetch can often sort that out.

Cheers,

Simeon.

Hi @Simeon Ross 

Yes, it was also a create issue trigger.  That was my thought as well: timing condition.  I suggested adding a condition check for issue type, as above, and adding tracing statements (debug or comments) to confirm the source data availability.

If that doesn't work out I will suggest the refetch next.

Thanks for the help!

Thanks so much everyone for all the suggestions and help!

@Simeon Ross Thanks for the tip! I will definitely add this as a condition. (It seems like I am just scratching the surface of all the automation features). 

@Simeon Ross @Bill Sheboy The refetch seems to be doing the trick! It must be a timing issue of some kind.

I appreciate all the assistance, looking forward to learning more!

Like Bill Sheboy likes this

To answer the question above: without the refetch, none of the fields are copied. Once I added the refetch, it all seems to transfer to the new issue.

Like John Funk likes this
david I'm New Here Jun 30, 2021

I'm facing the same issue even with the re-fetch, the re-fetch is at the end of my automation, should it go somewhere specifically?

Simeon Ross Atlassian Team Jun 30, 2021

Hi @david ,

Yep, it should. Think of it as a "refresh". Put it before the action that is having the issue so it can refresh it. At the end of the rule nothing else comes after it so isn't getting the benefit of the refresh.

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Confluence

👁‍🗨 Confluence Team planning dashboard_Atlympics 🌈

Hi Atlassian's, How is your journey with #Atlympics 2021 so far....excited! Me too, same excitement. Here's my typical team planning and vision dashboard which I used to share to my management and ...

2 views 1 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you