Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


New Issues created under an epic not inheriting epic's team

Is there any way to set stories in a epic to use the same team as the epic itself, or am I stuck manually updating the team for every new story I create in the epic? We are grouping our roadmap by team, however the default state for every new story created under epics (even epics assigned to a team) is for them to go into the "Unassigned" bucket. I would like it better if the new story inherited whatever the epic's team value is by default.

1 answer

Yes, we do this ourselves.

You need to know the custom field number for the team field on your instance. In our case, it is 10356 -- so you can follow the example.

The first screen shot is the automation I have in place. Note that you need to have an epic link to reference the epic's team field. You can see the trap I have for that and also the way I handle it. 

The way to make this work is to edit the issue field the way I show in the second screen shot.

I hope that helps.


Screen shot 1:



Screen shot 2:TeamName2.PNG

Thanks Rick - this makes sense, but unfortunately I don't believe I have access to the automation tool for my project. Maybe I can convince the admin to help me out with that.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events