Search

The value <> is not in a recognized format by Change8gent

Closed
as Not Reproducible Help for as Not Reproducible

1
0
Sign in
to vote
Type: Bug
ID: 780124
Opened: 2/27/2013 9:02:24 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Users cannot move an issue from one state (QA) to another (UAT) without encountering this issue.
we've looked at rule matches and cannot seem to fix the issue.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Create issue
Move from New to QA
Move from QA to UAT > Error

Product Language

English

Operating System

Windows Vista

Operating System Language

English

Actual results

The value for field "Requires UAT in a recognized format"

Expected results

Issue saved and moved to next state
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 3/7/2013 at 3:28 AM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 3/4/2013 at 3:20 AM
Hello,

Sorry for bothering. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thank you!
Posted by Microsoft on 2/27/2013 at 11:08 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please provide some screenshots to help us better understand this scenario?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 2/27/2013 at 9:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.