Skip to content

Settings and activity

7 results found

  1. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jesse Jacob shared this idea  · 
  2. 19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Review Assistant  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jesse Jacob supported this idea  · 
  3. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jesse Jacob shared this idea  · 
  4. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jesse Jacob supported this idea  · 
  5. 47 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jesse Jacob commented  · 

    I believe this is a limitation of TFS itself. MS has said they will introduce an iterative pre-commit code review policy in TFS 2015 around the Update 1 timeframe. Hopefully ReviewAssistant will be able to support this work when it's available as they did with the existing pre-commit code review policy. I wouldn't hold your breath waiting for them to implement this on their own.

  6. 51 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jesse Jacob commented  · 

    I think you're trying to make the tool patch over a bad code review process...I don't see many people needing this feature if they're doing frequent reviews. In my experience this problem crops up when people wait a very long to time to post a review a review--so long that other people can make unrelated changes to the same files as you've described. This is a pattern you should try to avoid by having people submit reviews more frequently so the changes being reviewed are more granular.

  7. 32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jesse Jacob supported this idea  ·