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

Advanced Roadmaps - Auto-Assign Teams?

I am leveraging advanced roadmaps across 10 different jira projects so that I can visualize and manage cross-team dependencies.  Each project = 1 team.


1. To get a Team associated to a Jira issue, I have to publish an edit to Advanced Roadmaps.   

This spams the team with email notifications (they have a lot of tickets in their respective projects).  Is there any workaround to not do this?   I tried to bulk edit within Jira but looks like this needs to be done from Advanced Roadmaps.


2.  Assuming every issue in a Jira project needs to be associated with its respective team, is there any sort of clean automated way to ensure new Jira issues are tied to the team?  Or is this something we need to manually reconcile on a continuous basis?


2 answers

2 accepted

3 votes
Answer accepted
Curt Holley Community Leader Jul 01, 2021

And yes, you can use automation to add the Team.

In Project A create automation like:

Trigger: When issue is created

Action: Edit issue

Currently the “Team” field cannot be selected from the “Choose fields to select” dropdown, so you need to add a Smart value setup like this into the “more options” section.


Note; Team 298 is just an example. To find the relevant team name type into Advanced search (JQL): 

"Team[Team]" =

Then start typing the name of the team and select it from the list. JQL will transform it into the number

that is fantastic, much appreciated!

Like Curt Holley likes this

Curt Holley 

I tried setting this up for my Advanced Roadmap as I have multiple projects included in the Roadmap and each project represents one team.  I got this error:


Teams Error.png

How do I fix this?  Ideally, whenever someone creates a ticket for a particular project, when I go to view this ticket in the Advance Roadmap, I will see a team assigned to that ticket.

Thanks for the assistance!

Curt Holley Community Leader Feb 27, 2022

Hi @Trina Woodworth 

So 116 is definitely a valid Team ID, yeah?

Can you share the rest of how you have put the automation together please? as I have never encountered that error.
But, what you want to do should be achievable. 

Yes, I believe it is a valid Team ID.  I got it from following the steps written above.


I selected When Issue created, then used the Advance Fields with the team text you outlined above:



Curt Holley Community Leader Feb 28, 2022

Is the Team field available for all the issue types and projects in scope for your version of te automation?

2 votes
Answer accepted

@Jack Arndt ,

You could turn your teams into "shared teams", in doing so, this opens up the "Team" field in Jira, that you can add to your screen as each shared team will become an entry in the "Team" field dropdown, and you can then do your bulk edit, to get all the existing issues caught up with the "Team" Value.

awesome, thank you!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

📅 Partner Webinar & Events Opportunities: July 2022

Hi community 👋, Here is another monthly roundup of the partner-organized events in July 2022. If there is any event missing please let me know in the comments below 🙏 If you're looking for Atla...

29 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you