Azure Test Plan - Multivalue control issue in Test Case when creating from Test Plan

microsoft / vsts-extension-multivalue-control

A work item form control which allows selection of multiple values.

MIT License

46 stars 44 forks source link

Azure Test Plan - Multivalue control issue in Test Case when creating from Test Plan #179

Closed MFigAs closed 2 years ago

MFigAs commented 2 years ago

Hi all, We are facing a strange issue since yesterday with a multivalue control : we have one in the Test Case workitem and when we create the Test Case directely from the Test Plan, the different values are not available and not editable. View image 1 and 2

But if we create it from the work item page, we have the different values to select. We sometimes have to refresh the page to view the values. View image 3 and 4

Can you please help us ?

Thanks a lot for your help

bminisi commented 2 years ago

We are also experiencing this. We noticed that to see the values when going directly to the work item, you have to have the "Change process of team project" permission set to "Allow". Project Admins already have this permission.

Is this extension still being supported?

Vertex-btb commented 2 years ago

@bminisi we are observing the same, but not all users in our org observe the behavior. The project admins and those with the "Change process of team project" cannot replicate the issue. Those that do observe the 'bug' have reported that a refresh resolves the issue. Yet we cannot ask all users to "Refresh the page anytime you observe an issue"

@ostreifel @mmanela @joserady @mohitbagra I see that there have been no commits to the extension since late 2019. Can you confirm if a contributor will be looking into this issue? We're hoping that the DevLabs team is still supporting this extension. thank you.

MOlausson commented 2 years ago

@MFigAs @bminisi @Vertex-btb Thanks for reporting this. I'm part of the team taking care of the DevLabs extensions. We'll take a look at this issue right away and ramping up in general to work through the queued up issues.

Vertex-btb commented 2 years ago

@MOlausson great news. thanks for getting back to us on this.

MFigAs commented 2 years ago

@MOlausson Great news thanks ! Looking forward for good news

JGPease commented 2 years ago

We are experiencing this issue as well and are glad to hear that there are plans to address it. Thank you!

MOlausson commented 2 years ago

Short update - still investigating but not found the root cause yet. Hope to have good news to share soon!

t-anderson commented 2 years ago

My Azure DevOps org admin and users are also observing this behavior.

What we see:

The multivalue control field on the test case is not visible when opening a test case from the Test Plans service. This is the same for Project Admins and non project admin users.
The field is visible when opening a test case from other pages, such as the Boards > Work items, Boards > Queries, Kanban board card, or Search results.
The field is intermittently not visible when opening a test case from other pages, such as the Boards > Work items, Boards > Queries, Kanban board card, or Search results. Clearing browser cache fixes this intermittent behavior.

Environment Details:

Azure DevOps Services
Process: Our projects are using an Inherited process from the Agile (system) process
Work Item Type with the multivalue control: Test Case
Browser: Edge, Chrome

teckert1964 commented 2 years ago

MOlausson commented 7 days ago Short update - still investigating but not found the root cause yet. Hope to have good news to share soon!

Has there been any progress in resolving this issue?

MFigAs commented 2 years ago

@MOlausson Any news to share about the investigation ? Thank you.

MOlausson commented 2 years ago

@MFigAs @teckert1964 Still investigating, it's one of those cases where it "just should work", nothing obvious wrong. Except it doesn't work... Work-around is to open the test case outside of Test Plans but we'll post an update here before EOW.

MOlausson commented 2 years ago

Short update: we've identified the issue and working to get a fix out.

MFigAs commented 2 years ago

@MOlausson Thanks for the update. Looking forward for the fix.

MOlausson commented 2 years ago

@MFigAs @teckert1964 @t-anderson @bminisi @Vertex-btb @JGPease Happy to share that the fix is rolling out now, it's working again in our Azure DevOps organization. Check if it's reached your already, else give it a day or two to propagate.

JGPease commented 2 years ago

Appears to be working for us on Edge and Chrome browsers! Thank you!

MOlausson commented 2 years ago

@JGPease thanks for confirming!

MFigAs commented 2 years ago

@MOlausson Seems to be working for us also. Thanks for the fix !

MOlausson commented 2 years ago

@MFigAs great to hear! I'll close this issue for now based on the positive feedback,

t-anderson commented 2 years ago

It's working for us too. Thank you @MOlausson!

bminisi commented 2 years ago

It's working for us too!! Thanks @MOlausson