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

Copy custom field value from parent issue to child issue (where child issue is not a sub-task)

I'm trying to copy a custom field value from an issues parent. 

Our current hierarchy is:

  • Initiative (parent)
    • Task (child)

Scenario is: when a child Task is created, copy the value from custom field 'stream' from parent Initiative into custom field 'stream' in child Task

Can anyone help with the jira automation rule for this? 

3 answers

1 accepted

1 vote
Answer accepted
Scott Harwood Community Leader Feb 25, 2019

Hi Natasha,

Yes, unfortunately for the moment you cannot copy a value from a portfolio parent. We have an open issue to add support for this:

https://codebarrel.atlassian.net/browse/AUT-389

There is a workaround for "acting" on the parent, but unfortunately not copying a value from it. 

I have linked this article to the ticket so we will notify you when we ship a fix.

Thanks,

Scott.

Did you find any way to do this?  I have the same requirement, to "cascade" a field value down from Portfolio Parent.  It was essentially why we purchased Automation for Jira, didn't realise it couldn't be done!

0 votes
Iago Docando Community Leader Feb 25, 2019

I think you can get this done even without an automation rule. 

Simply create a custom workflow for the subtask type you want and configure a postfunction for the "create" transition where that custom field value is copied from the parent issue.

I hope it helps.

Does this work for a non-sub-task?

Iago Docando Community Leader Feb 25, 2019

Well... in this particular case, for a non-subtask there's no parent issue to copy the custom field value from. But in a more general sense, yes, using postfunctions you can automate a lot of things.

We are using Jira Portfolio and have created the hierarchy:

  1. Parent - Initiative
  2. Child - Task

I thougt you were working with "normal" Jira. I haven't worked with Jira Portfolio yet so I'm not familiar with the concept of "Iniciative" but I would assume every Atlassian product is similarly designed. I won't state anything as a fact without actually knowing, though.

I'd advise you to just try what I told you, if that makes sense, and tackle it from there i it doesn't work. Since I don't know the platform, I don't know if the concept of workflow or transition makes even sense for Jira Portfolio.

Best of luck. I'm afraid I can't help you further with this if this doesn't work.

Iago Docando Community Leader Feb 25, 2019

I've added the "portfolio-for-jira" tag to the topic ;)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

5 mobile apps for Jira Cloud to boost productivity

  It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...

260 views 2 5
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