Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

Color picklist control by Microsoft DevLabs failed to load. #16

Closed
ghost opened this issue Feb 7, 2019 · 3 comments
Closed

Color picklist control by Microsoft DevLabs failed to load. #16

ghost opened this issue Feb 7, 2019 · 3 comments

Comments

@ghost
Copy link

ghost commented Feb 7, 2019

Some of the guest users to our Azure DevOps Services ("cloud") organization are coming across the below error when trying to load a work item type that contains the custom Color picklist control.

The error message they are receiving is, "Color picklist control by Microsoft DevLabs failed to load."

Our internal users and other guest users have not been able to reproduce this issue. Guest users are users who are guest accounts on the Azure Active Directory our DevOps collection is connected to.

Any troubleshooting steps for this issue, along with common reasons why the multivalue control fails to load, would be much appreciated!

We've had the guest users try multiple different browsers (Edge, IE, Chrome, and Firefox), InPrivate browsing mode, and clearing all browser data to no avail.

failed to load

@mmanela
Copy link
Contributor

mmanela commented Feb 7, 2019

@mishellcap Can you check your browser's console and share what the error is? It may be the bug that @trevorsg is already fixing

@ghost
Copy link
Author

ghost commented Feb 7, 2019

@mishellcap Can you check your browser's console and share what the error is? It may be the bug that @trevorsg is already fixing

Thank you for the quick reply, @mmanela ! I will reply back with some screenshot(s) from the users.

@ghost
Copy link
Author

ghost commented Feb 11, 2019

Hi, the users came back and said that the issue has been resolved on their end. It turned out the issue was caused by settings on their VLAN.

Local IT resolution: “(/|.|^)vsassets.io has been added for mentioned VLAN.”

Thank you again for the quick replies. Closing out this issue.

@ghost ghost closed this as completed Feb 11, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant