About P4V icons

P4V uses a variety of icons and badges (decorations) to depict Helix server objects and their status. The following table describes commonly encountered icons.

P4V displays file icons in the Tree pane and throughout the user interface, with file status indicated as shown in the following table. Note that file icons might be displayed with multiple "badges" (for example, check marks, lock indicators), each indicating an aspect of the file’s status. This table does not list all possible combinations. Note that red badges indicate actions taken by you, and blue badges indicate actions taken by another user. To display a tooltip containing more details about a file’s status, hover the mouse pointer over the file.

Category Icon Description

Files

p4v file txt

File in depot

 
p4v file notmapped

File in depot but not mapped by workspace view

 
p4v file differs

File in workspace differs from head revision

 
p4v file ws

File in workspace but not in depot

 
p4v file sync

File synced to head revision

 
p4v file notsync

File synced to previous revision

 
p4v file needs resolve

File needs to be resolved

 
p4v file lock

File locked by you

 
p4v file lock other

File locked by other user

 
p4v file add

File open for add by you (red "+")

 
p4v file add other ws

File open for add in other workspace (blue "+")

 
p4v file edit head

File open for edit by you (red check mark)

 
p4v file edit other

File open for edit by other user (blue check mark)

 
p4v file delete

File open for delete by you (red "x")

 
p4v file delete other

File open for delete by other user (blue "x")

 
p4v file deleted

File deleted in depot

 
p4v move

File open for rename/move ("+" indicates target)

 

File open for rename/move ("x" indicates source)

 
p4v file branch

File open for branch

  p4v file branch by other user

File open for branch by other user

 
p4v file integ

File open for integrate (will need resolve)

 
file import

File imported from another stream (cannot be submitted to current stream)

 
p4v symlink

Symbolic link

Repo Files Repo file synced to headBlob and at headCommit
Repo file at headBlob but not at headCommit
p4v file notsync Repo file not at headBlob and not at headCommit

Changelists

shelved file

Shelved file in pending changelist

 
pending resolve icon

Pending changelist has files that need resolve

 
pending shelved icon

Pending changelist contains shelved files

  pending empty icon

Pending changelist has no open files

 

Pending changelist in another workspace

Pending changelist not associated with the current workspace or user, with or without open files

Folders

folderdepot

(Blue folder) A folder in the Helix server depot

 
folderworkspace

(Yellow folder) A folder in your client workspace

  A folder that maps to a Graph repo

Depots

Classic depotClosedA repository of Helix server files that is not streams-based. Uses the Perforce file revision model, not the graph model. The default depot name is depot. See also default depot, stream depot, and graph depot.

 
remotedepot

Remote depot: if configured by your Helix server administrator, a remote depot maps a portion of another Helix server repository as if it were a depot. Typically used to enable you to import and export third-party files without providing outsiders with access to your Helix server.

  stream depot icon Stream depot: A depot where stream files are stored.
 

Spec depot: when enabled by your Helix server administrator, a spec depot stores the history of changes to Helix server specifications, such as changelistsClosedA list of files, their version numbers, the changes made to the files, and a description of the changes made. A changelist is the basic unit of versioned work in Helix server. The changes specified in the changelist are not stored in the depot until the changelist is submitted to the depot. See also atomic change transaction and changelist number..

  Graph depot: A depot for storing files in a repo , which uses the graph model associated with git instead of the "classic" Perforce file revision model.

Workspaces

Workspace associated with a depot

Workspace associated with a classic depot

 
Workspace associated with a stream

Workspace associated with a stream depot

  Workspace associated with a graph depot, which might or might not be a hybrid workspaceClosedA workspace that maps to files stored in a depot of the classic Perforce file revision model as well as to files stored in a repo of the graph model associated with git.
Swarm Pending changelist with shelved files in Swarm review

Pending changelist with shelved files in Swarm review

 

Empty pending changelist with shelved files in Swarm review

  Submitted changelist with Swarm review

Submitted changelist with Swarm review

  Folder History with Swarm review