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!


How to copy fields from linked issue


Let's say we have this structure:

Feature -> Story

Assume that

1. Components are set in Features.

2. Link is created from Story to Feature


Here is the requirement, once a Story is linked to a feature(no matter during creation or modified after), the corresponding component value of the feature should be copied to stories.


I tried couple implementations in automation but still nothing works. (e.g. screenshot is for story creation)


For the smart value for edit issue, I have tried couple, but none of them work:





Anyone can suggest on this?

2 answers

1 vote
Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 27, 2023

Hi @Javen Li 

If you would look at it from the moment the issues are linked.

Would the following rule might give you a start to the solution:

Screenshot 2023-10-27 at 10.15.17.png

You might need to add a condition after the branch to verify the trigger issue is a feature or even before the branche

Thanks a lot Marc.


However, I'm not sure if trigger issue works in this scenario. I have made couple rules with trigger issue and they work fine. But per my understanding:

In the context where user modified the link issue of a story, the trigger issue should be the story itself.

So if using trigger issue in the rule in the scenario, actually it is equalivent to use {{issue}} and make no difference about the question.


Not sure if my understanding is correct. 


As I mentioned, I have made couple rules involving trigger issue as well. However that's the different scenario. e.g. When component is changed in feature, I want all the changes back to stories.

In that case, the trigger issue is the feature itself, and I can make a brached rule, using {{}} to refer the value and set the value to linked issues.

So is there a simple smart value that I can use to fetch some information from its linked issue(e.g. description from the linked issue)?


We can even restrict the scope of the question:

1. there will be only 1 linked issue.

2. always the issue is linked from the child(in this case, story) to the parent(in this case, feature). No other direction.

Suggest an answer

Log in or Sign up to answer