When comparing a TFS Changeset in SQL Compare it will show all schema changes that are different between the Changeset and the destination, but within a TFS Changeset, there is metadata within the Changeset to indicate which specific database objects are being changed within the Changeset. It would be a huge timesaver to allow SQL Compare to be able to only select the database objects that are actually being impacted by the Changeset by default. The situation I have is this:

Developer 1 - Adds a table to database A and checks in the change to the development database, but cannot yet promote it to the testing database
Developer 2 - Adds a table to database A and checks in the change to the development database. In order to promote his change he compares the changeset to the testing database and SQL Compare display a list of objects that are different. That list for Database A includes Developer 1's table and Developer 2's table, but Developer 2 doesn't always care about what Developer 1's table does since it is not in his changeset. It would be nice if it continues to show Developer 1's table, but that it would automatically select Developer 2's table because it was specifically marked as changed as part of Develper 2's changeset. For 1 table, it is not that big of a deal, but when a changeset includes multiple tables, multiple stored procedures, etc it can be very tedious to go through and remember each object that was impacted and not mistakenly select a table that was not part of the changeset. By defaulting it to select this Developer 2 still has the ability to select/deselect other objects that he wants to include, but it at least cuts out the work needed to manually include tables that he knows need to be compared since it is part of the changeset.