Optimize "Refresh Comparison" to only pull metadata that has been changed since the last comparison
Currently, clicking Refresh Comparison does not optimize the comparison in any way, it just allows you to skip selecting some of the configuration steps from running a new comparison.
This means that it takes the same amount of time actually comparing the orgs.
It would be nice if on clicking of "refresh comparison" the logic didn't run a full compare and instead just looked at metadata that had been changed since the last compare in order to reduce the comparison time.
19
votes
Anonymous
shared this idea
-
Anonymous
commented
This may not work with how Last Modified Date is updated on Metadata components. It is not always updated with standard changes which may result in false negatives, resulting in the changes not being deployed / compared.