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

Auto Update Subtask field upon creation based on parent issue

Hello community,

I have the following case scenario that i'm fighting with. 
When I create a parent issue (e.g. user story) I populate a field called "Team". 
Once the parent issue is created, subtasks are then created. Each sub-task needs to inherit the team field value from the parent. 
The reason I need it is because we are using one board for two different teams. Each team has it's own swimlane. So I want the subtasks of the parent story to appear in the same swimlane. 

I would be great if you help with the automation of this.


Thank you!

2 answers

1 accepted

0 votes
Answer accepted
Jack Brickey Community Leader Dec 21, 2022

Yes this is certainly possible. Have you attempted an automation rule as yet? It would look something like below.

  • trigger - issue created
  • condition - type = subtask
  • condition - any other condition to ensure the action is only executed as desired
  • action - edit issue, choose your Team field and choose Copy from parent

Thanks! I havent noticed the option to COPY from parent

Like Jack Brickey likes this

Hi @Iavor Zayn 

Is it a custom field called Team, or is it the Jira built-in Team field?

If it's the Jira built-in Team field, we ran into a problem with this situation because apparently Jira doesn't allow you to assign Team values to sub-issues - Jira "knows" that all sub-issues belong to the Team assigned to the parent.  We went back to our custom Team field when we found out about this the hard way.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events