microsoft / vsts-extension-retrospectives

An Azure DevOps extension for efficient retrospectives
MIT License
182 stars 81 forks source link

Can No Longer See All Teams from Retrospectives Dropdown #914

Open hansenbc opened 5 days ago

hansenbc commented 5 days ago

Describe the bug Within the past few days our team members can no longer see all teams from within the project by clicking on the team dropdown in the top left corner of the Retrospectives page, the only team we can see is the team we're assigned to.

Are you using the Retrospectives Tool on-prem? [ ] Yes [ x] No

If Yes, what version of the extension?

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Retrospectives'
  2. Click on 'Team Dropdown'
  3. Scroll down to ''
  4. See error

Expected behavior When I click on the team dropdown I would expect to see the team I'm assigned to under "My Teams" and then the remaining teams in the project under "All Teams".

Screenshots If applicable, add screenshots to help explain your problem. If you have any developer console information that feels relevant, that is also helpful!

What screen type are you seeing this on ? [ x ] Desktop [ ] Mobile

Additional context Add any other context about the problem here.

grantburdon commented 4 days ago

This is also the case for me and my Teams. We are using version 1.92.29 (Latest), which was updated yesterday.

lobbo232 commented 4 days ago

Members of our team are also experiencing this issue on 1.92.29 (Latest). Seems like you maybe can only see the team you had selected before the latest update was deployed, can't see other teams any more. Direct links to other teams retros also don't work.

tandel commented 4 days ago

Happening for me too. Will only show the last team that I worked with. Nothing in the teams dropdown, and the links to All teams and My teams are not active links.

joaotrajanoonr commented 4 days ago

We have the same issue after the latest versions. Yesterday there were 4 updates (1.92.25, 1.92.26, 1.92.27 and 1.92.29), we don't know exactly which version presented this issue.

benwcb commented 3 days ago

Issue persists in 1.92.30.