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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,552,465
Community Members
 
Community Events
184
Community Groups

How can I get an event date change to all child issues?

One of the fields we are using is "Event Date". This is something that is then repeated in each child issue. How can I set it to where I set it on the parent and it just automatically updates it throughout the child issues?

1 answer

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 18, 2023

Hello @Lisa Mills 

Welcome to the Atlassian community!

What types of issues are these? Are they Epics with child issues? Are they Stories/Tasks with subtasks?

The basic structure of the rule would be

Trigger: field value changed: Event Date
Condition: Issue Type = (the "parent" issue type for your scenario)
Branch: (depends on the types of the parent and child issues)
Action: Edit Issue
Field: Event Date
Copy from Trigger Issue

I tried this but it didn't seem to work. If it helps we have it broken down like this: Each "Epic" is a month, within each month is any campaigns, events, or projects we're running (this is for marketing), then with each campaign is each "child issue" that includes all the tasks for that campaign. Both the parent (or campaign in this instance), and the individual tasks (child issues), have standard information, which includes the date of the event or beginning of the campaign. we use an "Event Date" field for this. I tried inputting the automation rule you outlined above, but it didn't seem to actually run down. I want to be able to input the event date, and that changes for all the individual tasks within it. Where the purple icon is, I tried the rule with that set as parent, then with it set as sub-task, and neither worked... Screenshot 2023-04-21 100324.png

Never mind! I figured out what I missed... I didn't have it set to the "triggered" issue. Thank you!

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 21, 2023

Can you describe the issue hierarchy?

It sounds like you have

Epic
|-- Campaigns, Events, Projects (What are the actual issue types of these items?)
|-- child "tasks" (What are the actual issue types of these items?)

The default issue hierarchy in Jira is

Epic
|-- base level issues (i.e. Story, Bug, Task)
|-- subtask type issues

Are you using that hierarchy to create the parent/child relationships between the issues, or are you using generic issue linking to artificially create a parent/child relationship?

At which level are you setting Event Date?

To which level are you trying to copy that data?

Can you provide a screen image of an issue where you want to set the Event Date, where that image also shows the "child" issues that you want to have automatically updated?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events