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.
I have created an epic: and I wonder if there is a simple way to communicate the new migration date in a way that it cascades to all tasks that have been created under the epic? Or is to include this information in the activity log in the epic and mention everyone involved the only way to do it?
Hi @Beatrice Monreal and welcome to the community!
The best way to do this is with automation. Here's an example where I'm using Due Date:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mark Segall In this example automation is the For Stories (or other issues in Epic) available in the Jira Cloud? I'm new to automation and I'm not finding that component. If not, is there an equivalent for Cloud? I'd like to copy an Epic custom field to all child issues when it is updated in the epic.
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.