Team field is visible to others and me, but only I can choose/get the drop-down menu with a team to choose from, other people in my organization do not, but they had that working in the past. please help
The Team picker needs the Browse users and groups global permission to search, the same as the Assignee picker and the other user pickers. Your description matches what happens when other users lose that permission: the field still renders, the dropdown stays empty. Since you get suggestions and they don't, I'd guess you hold it through a site-admin group and they used to hold it through a group that has since been dropped from the grant, or the default product access group changed.
Two checks before changing anything:
To fix it, scroll to the bottom of that Global permissions page, choose Browse users and groups, pick the group your users belong to (normally the default product access group) and click Add. They need to log out and back in for it to take effect.
KB for the same symptom in user pickers: https://support.atlassian.com/jira/kb/jira-cloud-unable-to-search-users-in-user-picker-fields/ KB for Teams specifically: https://support.atlassian.com/jira/kb/unable-to-view-teams-options-within-jira-service-management-when-clicking-on-teams/
If Assignee search works for them and only the Team dropdown is empty, post back with a screenshot. That would point at the field's context or scope instead.
Thanks for detailed explanation, as I gave permission to the group long time ago i checked and is still active. I went and created another group with only 1 user, and gave global permission for Browse users and groups and is still not working. Assignee picker is working. I logged in as that user via admin and can choose a team easily, I can see it and drop down menu to pick team is available.
But all individual team members can see it/pick it, also team members cant see teams anymore they used to see it in the past, I see all the teams.
OK, so it's not the permission. The interesting bit is that the same account works when you sign in as them from your machine. Same account, different result, so the difference is where they sign in from.
My bet: your org has more than one site (a sandbox counts) and they open Jira from a different URL than you do. Teams stopped being org-wide when Atlassian migrated organizations on original user management to site-level visibility (Oct 2025 to Feb 2026). Since then a team shows up only in the site it was assigned to. If the teams got assigned to your site and your users live on another one, they see nothing, you see everything, and it "used to work". Check under Atlassian Administration → Apps → pick the site → Groups → Assign teams, or open any team's profile and look for "Assign this team to a site".https://support.atlassian.com/platform-experiences/docs/how-to-assign-teams-to-a-site/https://support.atlassian.com/platform-experiences/docs/understanding-team-visibility/
If you have a single site, the other thing that gives you "admin sees teams, nobody else does" is an open site. When people can join through your approved domain without an admin approving them, Atlassian switches Teams off for those users. That one is tied to the account, so it doesn't square well with your sign-in test, but it takes a minute to check: Atlassian Administration → Apps → App access settings, see what your domain is set to.https://support.atlassian.com/jira/kb/users-can-not-view-or-access-teams-in-atlassian-cloud-site/
One thing I couldn't tell from your second message: do the affected people get an empty dropdown, or a dropdown that's missing some of the teams? Missing some would mean the teams are split across sites.
It looks like you're new here. Sign in or register to get started.
