Why is the Team field not added to screens by default?
Asked by Rob Horan:

Team is pretty much a mandatory field for Advanced Roadmaps so why isn't it on every screen by default?

Honest question - this makes zero sense to me.

What else needs to be added to make this product (Advanced Roadmaps) work as expected?


Answers:
author: Curt Holley
body: [@Rob Horan](/t5/user/viewprofilepage/user-id/853604)

Check these links out. *Might help shine a light*?

[Advanced Roadmaps Guide \| Jira Software \| Atlassian](https://www.atlassian.com/software/jira/guides/roadmaps/advanced-roadmaps)

[Creating your first plan in Advanced Roadmaps - YouTube](https://www.youtube.com/watch?v=xJ-RmFwEVjM)

[Advanced Roadmaps Home \| Advanced Roadmaps for Jira Cloud \| Atlassian Documentation](https://confluence.atlassian.com/advancedroadmapscloud)

comments: author: Rob Horan
body: Thanks, I appreciate it, and apologize for letting my frustration with this product get the best of me. I've been asking multiple roadmaps questions and you're the first person to answer with helpful information.

How can a team adopt this product when they have already been doing things a certain way?


author: Rick Olson
body: In our environment, we do include the team on the screens for the issue types of stories, tasks, bugs, and epics. What is shown on the screen, by team name, is only those teams that are configured as shared teams in Advanced Roadmaps.

When using shared teams, in advanced search, when creating the query I select 'Team' from the drop-down list, which resolves itself as "Team\[Team}". Then I enter "=" followed by the first couple letters of the team. I select the team from the drop down list and that team name gets resolved as the teamid. Hear is a sample query: "Team\[Team\]" = 195.

Because I am using shared teams, I can query for them in Jira since the teamid is included in the issue. I don't know if querying by plan-specific team supports the ability to query in Jira.

comments: author: Jane Brock
body: Ok, not getting it yet. I don't know which is a key word and which is a real team name....is it Team\[Jokers\] = 4 or Jokers\[Team\] = 4

when you start typing it just comes up with Team = 4


author: Rick Olson
body: Of the query "Team\[Team\]" = 195, it is simply 'Team' in both places.

In your case, on the search line you would literally type (with quotes): "Team\[Team\]"

and then add a space and the equal sign, followed by a space.

Then start typing 'Jokers' until you see it listed in the drop-down list. Select if from the list and the screen will replace 'Jokers' with the TeamID of '4'.


author: Curt Holley
body: HI [@Rob Horan](/t5/user/viewprofilepage/user-id/853604)   
I think you "pretty much" answered your question with the "pretty much mandatory" description.

Shared teams although handy (and yes! I can't imagine not having them anymore) Advanced Roadmaps can certainly be used without them.

Plus, by not enforcing onto all screens (which could be tricky for Atlassian to do when existing Jira Standard sites move up to premium) it gives the admins of the site the opportunity to configure in a way the best suits the processes and screens already in place (like [@Rick Olson](/t5/user/viewprofilepage/user-id/3741809) describes, for example).

comments: author: Rob Horan
body: Hi Curt,

I apologize, because what you provided was very helpful, but now I have another question.

You started off by saying Shared teams. Are you saying the team field can only contain a shared team value? And maybe in some senses that can be considered obvious... but it isn't.


author: Curt Holley
body: That is correct [@Rob Horan](/t5/user/viewprofilepage/user-id/853604) the Team field is a single entry field that is populated by the teams configured in the Shared teams section of Plans.

It simply means these teams can be assigned to issues in any Jira projects that are configured with the team field on them.


author: Rick Olson
body: The way we do our planning, at the sub-tasks and any level higher than epic we don't need the team field. The team for a sub-task is the team associated with its parent. It we had the team field on every type of issue screen, that would be a problem for us.

To your question of what else has to be added to make it work as expected...

You'll find that you cannot sort the Team field in a filter. I had to create another field that, through automation, keeps the team value in it, just so that I could sort a list of issues by team.

I keep learning more things, like using Shared Teams if you want to actually see the name of the team on the Jira screens...

Enjoy the journey!

comments: author: Rob Horan
body: Thanks! Right now the journey is more like being trapped in a room with no lights and someone stole the car keys and GPS and I need to find the secret highway

How are you able to use Advanced Roadmaps without Teams though? Seems impossible to manage capacity without that.


author: Jane Brock
body: Rick, are you able to use the team field in a filter? I can't seem to pull back any data related to a Team When I attempt to use it, it pulls back a key value, but then no data. Is that why you created another field?? looking for a workaround.


Tags: advanced-roadmaps

capacity

team