You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
There are couple fields in child issues that mostly match the parent issue, but sometimes need to be changed. For easy implementing I would like to copy the Epic values upon creating the child issue. I tried using 'Automation' in different configurations but I can't get it to work. It say's 'Succes' but the fields in the new issue don't reflect the fields in the Epic.
This is the current exported rule:
Thank you for taking your time to help me with this issue!
Would you please post images of your rule definition? That will help the community try to answer your question.
Your custom fields are different from those defined in other people's instances, so importing the rule's JSON may not help others understand your rule.
Best regards,
Bill
Hi Bill,
Thank you so much for replying so soon! I've updated the original post. :)
- Huey
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Huey,
Thanks for the additional information. Three next steps to try:
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
An update: another community member saw a similar issue with the edit/copy not working. They solved that by adding a re-fetch action to solve a potential timing problem where the created issue does not yet have the parent link.
So, your updated rule would be:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy ,
Thank you so much for helping me, your advice did the trick! For anyone searching the forums here is my implemented solution:
Tip: be sure to configure the last step 'Then: Edit issue fields" correctly by telling it to copy from epic. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just wanted to say thanks to @Bill Sheboy for this answer. Worked perfectly first time and saved me the time having to figure it out
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have this automation running and it works when an issue is created; however is there a way to get this to trigger when the field value changes on the Epic and it copies the the new field value to all child issues (tasks/stories)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Brellison -- Welcome to the Atlassian Community!
First thing: please consider creating a new question, and perhaps linking to related ones. That will ensure more people see it...only the people currently following this thread will see it otherwise.
On to your questions...
The rule you show is triggered on a field value change, not issue create. Are you certain that triggers on create as you noted?
Next, you should be able to detect the change in the epic and then copy that down to its child issues. For example:
Please also see the template library for other example rules like this: https://www.atlassian.com/software/jira/automation-template-library#/
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your help Bill! Your solution helped.
For clarification, I had the original rule in this thread running fine, but found a limitation in it that when the Epic's fields were updated, the existing issues' fields did not update to reflect the new value. But the automation you provided me fixes that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
I have tried the same .but it is copying from parent to child .but not child to grand child.any suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Aarohi
Please consider creating a new question, and perhaps linking to related ones. That will ensure more people see it...only the people currently following this thread will see it otherwise.
Regarding what you asked about...
Are you using Jira Cloud or Server/Data Center version?
If on Cloud, what is your project type: Company-managed or Team-managed?
When you note you tried the same thing, what do you mean? Would you please post images of your complete rule and audit log details, showing the execution which does not work as you expect? That will provide context for the community to offer help. Thanks!
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Aarohi
Currently, nesting of branches is not possible, so you would need 2 rules. The only differences between the rules are the conditions and the branches.
Rule #1 can trigger rule #2, so in the detail settings for Rule #2 you may enable the "Allow Rule Trigger" option to make this work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.