Search

Team Explorer - Pending Changes - Policy Warnings - Comment by Fabien Lavocat

Closed
as Duplicate Help for as Duplicate

3
0
Sign in
to vote
Type: Bug
ID: 767199
Opened: 10/12/2012 8:50:54 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
When you activate the Check-in Policy: Changeset Comments Policy
if you check-out a file, go to "Team Explorer - Pending Changes" enter a comment, the policy warning is not removed, you have to either navigate to another panel in the Team Explorer either click the Refresh button.
Details (expand)

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

Visual Studio 2012

What category (if any) best represents this feedback?

 

Steps to reproduce

When you activate the Check-in Policy: Changeset Comments Policy
if you check-out a file, go to "Team Explorer - Pending Changes" enter a comment, the policy warning is not removed, you have to either navigate to another panel in the Team Explorer either click the Refresh button.

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

When you activate the Check-in Policy: Changeset Comments Policy
if you check-out a file, go to "Team Explorer - Pending Changes" enter a comment, the policy warning is not removed, you have to either navigate to another panel in the Team Explorer either click the Refresh button.

Expected results

When we change the comment in the textbox, the policy should be refreshed automatically.

Locale

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by RobSiklos on 3/4/2013 at 11:35 AM
I see this is closed as a duplicate.

A duplicate of what?
Posted by Microsoft on 10/15/2012 at 2:05 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 10/12/2012 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.