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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Copy a field value from Initiative to Epic when Epic ticket is parent linked to Initiative


Hello Community,

Can you please advise how can I copy a field value from Initiative to Epic? Epic ticket is linked to Initiative through "parent link". I can do that with Epic to Story without any issues, using the Copy Value From Other Copy Value From Other Field Post-Function and Automation Rule, but when it comes to Initiative issuetype it doesn't do anything. Any suggestion is highly appreciated. Thank you .


2 answers

1 accepted

0 votes
Answer accepted

Hello @Kay ,

There are some fields that are baked into the base functionality of Portfolio directly to alter the Base Jira behavior and do not live as a traditional field types for Jira, as they have additional functionality outside the traditional field types and exist in different locations of the database to complete the special functions.  The "Parent Link" field is one of these Special Portfolio field types used to map a standard issue type to the higher hierarchy levels.

Because of this the "Parent Link" field is not a searchable field by many add-ons including automation for Jira, so you won't be able to do this like you described.

The Functionality needed to use the field in this manner is being tracked in the following Feature Request in both Jira Cloud and Server respectively, I am adding both incase anyone else runs into this thread looking for a solution on the alternate platform:


Hello @Kay 

I'm looking for an Automation rule which can copy a value from a cascading type field of an Epic to its child tasks (issuetype Story), can you please share your code for this with me?
Thank you in advance!

Kind Regards


Hi there,

You can use this:

"fields": {
"Client": {
"value": "{{issue.Client.value}}",
"child": {
"value": "{{issue.Client.child.value}}"


"Client" = Name of Field

Client.value = first value in cascade drop down menu

Client.child.value = second drop down menu value


Also check out Ravi's video here:

It's for a sub-task but you can adjust for copying from an Epic.

Good Luck!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events