Why does the MSSCCI sometimes put automatically a green tick on Rhapsody packages?

MSSCCI sometimes puts automatically a green tick in front of a package that has not been checked-out (not locked under RTC). I suppose it concerns RHP dependencies between packages that RTC detects as a modification.

It may occur if the timestamp in packages have been updated even though the package may not have changed.

It means that we cannot trust the MSSCCI to know which files are locked or not. We have to go to the RTC client.

What is the correct process to adopt? Do we have to ignore/undo these false modifications? Do we have to include them in a Change Set?