Closed xymunter closed 5 years ago
@xymunter Can you share your full xml file to I can test locally?
Sure thing. See the WIT attached in this post. UserStory.zip
@xymunter I wasn't able to reproduce it locally and I tried the same set up as the xml you provided. Is it okay that we look at your repro via online screen sharing? Please feel free to reach out to me @ joezha@microsoft.com if you need further help.
@xymunter as we talked over skype, this is a UI bug in TFS 2018 and has been fixed in TFS 2019. The bug is that we will accidently identify them as the same field if they are using the same contribution.
@joezha Thank you very much for your help. Really appreciate it.
TFS 2018.2 Multivalue control 2.2.25
I have a workitem type that contains two Multivalue controls. One of the bound fields is configured to be set as Required when the workitem is in the Closed state (so this is defined in the State tags, not in a Transition).
Here's what the configuration somewhat looks like:
This works well, actually a little bit too well: it seems as if all Multivalue controls are now being Required:
Now if the actually required Multivalue control gets selected, both indicator disappear: