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,457,001
Community Members
 
Community Events
176
Community Groups

When I add issues to a team, does the team field on the issue get filled out automatically?

Hi,

When I create a team in Advanced Roadmaps, I can add issues to this team.

There is then a team field on the JIRA issue, e.g., a story or a bug.

Q1. Does this field get filled out automatically, or is it manual?

Q2. Can this field be applied to Epics and other issue types?

Many thanks,

Faith

2 answers

0 votes
Curt Holley Community Leader Mar 08, 2022

Hi @Faith Sparkes 

Welcome to the community.

Like @Rick Olson has said, add the Team field to all the relevant screens and then people can add the team to any issue type via the screen.

Presuming you are using Jira cloud? so.....you can automate the population of the team field for the members of the team with a rule like the one below. 

Note: By using If/else, you can do various teams within one rule. Also, you do need to know the team ID and configure the additional fields section with the required teams ID

Screenshot 2022-03-09 091826.png

We put the team field on our Jira issues screens (Initiatives, Epics, Bugs, Stories, and Tasks) and we maintain those values there. We use shared teams, which makes the team visible on the Jira screens. Adding Team to a sub-task Jira screen isn't necessary since sub-tasks are pinned to the team where it's parent (bug/story/task) is associated.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events