Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team Assessment is not working #1001

Closed
cdvolvo opened this issue Jan 28, 2025 · 3 comments · Fixed by #1002
Closed

Team Assessment is not working #1001

cdvolvo opened this issue Jan 28, 2025 · 3 comments · Fixed by #1002
Labels
bug Something isn't working

Comments

@cdvolvo
Copy link

cdvolvo commented Jan 28, 2025

Describe the bug
Team Assessment is not working. The icons do not appear correctly, and votes cannot be entered. Bug is in Edge and Chrome.

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

If Yes, what version of the extension?

To Reproduce
Open Team Assessment in Retrospectives. Attempt to enter a vote by clicking on item.

Expected behavior
expect original icons/button which allow collection of votes.

Screenshots

Image

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

@cdvolvo cdvolvo added the bug Something isn't working label Jan 28, 2025
@evanvenell
Copy link

This is also not working for my ADO as well. Might have been a commit pushed to something that tries to contact a server or just the resource server for the elements is offline due to the 404's in the networking tab of the dev tools.

@Alfadbhq
Copy link

We are currently facing the same issue where the radio button has turned into a box and is unclickable. Hopefully, we can have this resolved soon.

@MOlausson
Copy link
Collaborator

Thanks for reporting, this is also tracked in #984. The extension fails to load icons from the network, we are investigating and will share an update asap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants