Urgent: Control Showing Wrong Value about vsts-extension-multivalue-control HOT 4 OPEN

Even I raised this issue couple of months ago, this issue makes this field unusable. I haven't had luck in resolution of this, I had to abandon using this and go for alternate methods.

from vsts-extension-multivalue-control.

Even I raised this issue couple of months ago, this issue makes this field unusable. I haven't had luck in resolution of this, I had to abandon using this and go for alternate methods.

What was the alternate method you used for this? I am looking for MV control with some more functionality. Can you please help?

from vsts-extension-multivalue-control.

I have the same issue in my user base. The issue can be easily recreated and appears to be related to three combined areas; Firstly, an open ticket in the URL. Secondly, affects the pop-up from the search bar ONLY - pop-ups from direct links do not exhibit the issue. Finally, something to do with the user.

We have managed to re-create the issue by having two test work items. User 1 (admin), can open both tickets with no issue. The 2nd user (non-admin) can open the first ticket but the issue is exhibited constantly when opening the second from the search bar. Changing the second user to an admin made no difference.

To recreate;

1. Create two new work items of choice containing the multivalue selector.
2. On item 1, set the multivalue selector to a distinct value.
3. On item 2, do not set the multivalue selector (or set it as anything other than Item 1).
4. On work item 1 directly so it shows as https://dev.azure.com/[org]/[proj]/_workitems/edit/xxxxxx/ in the address bar.
5. Now open work item 2 from the search bar.

• Note work item 2 now shows the same value in the multivalue selector as item 1.
• Note the save button no longer works if you change the value in work items 2 multivalue selector.
• Note making a change to the multivalue selector in item 2 applies those changes directly to item 1 behind.
• Note also that item 1 save button has also been activated as a result of the change on item 2.

I must add that if you do fail to recreate it then please go and create another standard contrib user on your org and try with that user. Hopefully you will see the same issues as us - where one user (who happens to be me and the admin) doesn't have this behavior and the second user has this behavior constantly.

Hopefully this detail will allow you to find the fault and post an update soon - without it we will be forced to remove the extension.

from vsts-extension-multivalue-control.

Thanks for reporting, we'll dig into this.

from vsts-extension-multivalue-control.