File Status Information

The operations you can perform on a particular file depend upon the status of the file. A successful check-in or check-out operation updates the status of your working file to Current, unless you check out a historical revision or delete the file. This list includes all status classes and shows their effects on check-ins and check-outs.

Current

The tip revision of this file is in your working folder.

Check‑ins Does not affect the file revision in the repository.
Check‑outs Does not affect the file revision on your workstation.
Ignore

Ignore acts as a note to self to ignore the marked files. It does not change any functionality within the files or within StarTeam. You can restore files back to their StarTeam status when you are done ignoring them. Right-click the file and select Ignore or Restore.

Check‑ins Not applicable. Files with the Ignore status can be checked in. However, marking them as Ignore indicates that you do not want to work with the file.
Check‑outs Not applicable. Files with the Ignore status can be checked out. However, marking them as Ignore indicates that you do not want to work with the file.
Missing

The file is not in your working folder.

Check‑ins Not applicable. If a file has a Missing status, it is not in your working folder, so it cannot be checked in.
Check‑outs Copies the file to your working folder. If a file has a Missing status, you will be asked if you want to check it out when you open it. You can also check it out manually.
Merge

The file in your working folder has been modified, but is not based on the tip (latest) revision of this file. This status usually occurs when you and another person have both been working on a file, but the other person has checked it in before you.

Check‑ins Unless you force a check-in, File Compare/Merge starts. If the file is a text file, File Compare/Merge can reconcile the differences between it and the tip revision. If the file is binary, you may be able to merge the working version and the tip revision by using the application in which the file was created.
Check‑outs Not allowed, unless you force the check-out. The file changes you have made in your working folder will be lost.
Modified

Your working file has been altered and is based on the tip revision of this file.

Check‑ins Unless someone else has the file locked, you can check in the file.
Check‑outs Not allowed, unless you force the check-out. The file changes you have made in your working folder will be lost.
Not in view

The file is in your working folder, but not in the project view.

Check‑ins Not applicable. Files with the Not in View status cannot be checked in. However, you can add them to the project with the Add Files command.
Check‑outs Not applicable. Files with the Not in View status are not in the project view, so they cannot be checked out.
Out of Date

The file in your working folder is an outdated revision of the file. If you need the current revision, you should check it out.

Check‑ins Not allowed, unless you force the check-in. Checking in an Out Of Date file overwrites the changes made to the tip revision of the file with your older file revision.
Check‑outs Checking out an Out Of Date file makes the file in your working folder Current.
Unknown

The file in the working folder has the same name as a file in the view, but the file in the view has not been checked out from the repository. You may have copied it from another location.

Check‑ins Not allowed, unless you force the operation. If the file status is Unknown, the consequences of this action are also unknown, except that the file in your working folder becomes the tip revision in the repository. Before forcing a check-in, try to identify the file by using Update Status with an MD5 checksum instead of a time stamp (see File Options). If you still cannot identify the file, compare the file in your working folder to the current tip revision.
Check‑outs Allowed, if you merge the file in your working folder with the tip revision. However, because the first revision acts as the ancestor file for the merge, many parts of the files may be in conflict. Instead of merging, you may prefer to force a check-out or check-in. If the file status is Unknown, the consequences of forcing a check-out are also unknown, except that this action also overwrites the file in your working directory. Before forcing a check-out, try to identify the file by using Update Status with an MD5 checksum. If you still cannot identify the file, compare the file in your working folder to the current tip revision.