Engineering Workflow Management source control icons

Edit online

Engineering Workflow Management source control uses specific icons to represent source control artifacts. The basic icons have variants that reflect their status in certain views, such as the Team Artifacts view, Pending Changes view, and Repository workspace editor.

The following table lists the basic source control icons and their variants.

Artifact Icon

Stream
Stream icon

Repository workspace
Repository workspace icon

Snapshot
Snapshot icon

Baseline
Baseline icon

Component variants

  1. If shown within a repository workspace, the icon indicates that the component is loaded or partially loaded in a sandbox.
  2. Owned by a project area.
  3. Owned by the current user.
  4. Owned by a contributor who is not the current user.
  5. If shown within a repository workspace, the icon indicates that the component is not loaded in a sandbox.
Component icons

Change set variants

  1. Active: Not completed and not linked to any work item.
  2. Active and current: Not completed. Automatic check-ins default to this change set.
  3. Completed: Not linked to any work item.
  4. Completed: Linked to one work item.
  5. Completed: Linked to two or more work items.
Change set icons

Pending changes view icons

The figure below shows all of the icons that can be displayed in the Pending Changes view.

Pending changes view icons
Table 1. Pending changes view icons
1 Pending Patches node contains all patches that need to be reviewed by the user and manually merged or removed.
2 The JUnit workspace is offline. This workspace belongs to a repository that is currently not accessible. User should login. The component nodes are decorated with a little gray round circle as a reminder that they are offline. The synchronization information is out-of-date and no changes can be flowed.
3 Workspace node representing the workspace named Source Control Workspace collaborating with the stream named Source Control. It is online. Engineering Workflow Management source control supports working with workspaces from different repositories, unlike the previous workspace shown in (2). The component nodes are shown right under the workspace node.
4 Component node named Filesystem in workspace Source Control Workspace is busy. It has pending conflicts (red cross decoration), pending local changes (yellow underlay) and outgoing change sets (left to right arrow). More details are available under this node.
5 Unresolved folder contains local changes and conflicts for its parent component. It is good practice to resolve all unresolved items in this folder before accepting or delivering change sets. This means checking in local changes and resolving conflicts.
6 Local change that represents a content change to the resource AbstractAdrenalineOptimization.java in the Eclipse workspace. The user can undo this local change or check it in one of their outgoing active change sets.
7 Conflicted item representing a content conflict on the resource AbstractAdrenalineOptimization.java. The user has to decide between two versions of that modified file. User can also decide to auto merge or manually merge the content of these two conflicting versions.
8 Outgoing current change set. This node represents a change set. It is outgoing because it is under the Outgoing folder, which means this change set does not exist yet in the target flow of this workspace, the stream Source Control. It has a little triangle decoration which means it is the current change set. The change set the developer is currently working on. It is not completed which means the developer can continue to check-in more changes into it.
9 Outgoing file change. This node represents a content change for the resource AbstractAdrenalineOptimization.java. The developer can double click on this node to see that change in a compare editor. User can undo that change.
10 Outgoing completed change set. This change set contains a bug fix for defect 50000. It can no longer be edited and is ready to be delivered.
11 Outgoing completed file change. This describes the actual fix for defect 50000.
12 Work item associated to an outgoing change set. This work item describes the purpose of the change set.
13 Suspended change set. It is an outgoing change set that was suspended. For example, to work on something else. The change set an be resumed to become outgoing again. Can also be discarded if it is no longer needed.
14 Outgoing baseline. A baseline that can be delivered. The node can be expanded to reveal its outgoing change sets which will be delivered with that baseline to the flow target.
15 An incoming baseline which contains one change set not in the workspace named Source Control Workspace. It can be accepted to be up to date with the flow target Source Control.
17 Component node with a custom flow target to the stream named Repository 0.6 RC5. The other components in the workspace use the workspace's flow target set to stream Source Control. Flow targets can be set at the workspace level and overridden at the component level.
18 Unloaded component. The component Repository Client from workspace Source Control Workspace is not loaded into the Eclipse workspace. None of the projects it contains are shared. The component icon is empty (blue outline) for non loaded components and full blue for loaded ones. Any component can be individually loaded or unloaded as needed.
19 Outgoing component deletion and incoming component addition. It is possible to flow entire components between workspaces and streams. In this case the developer removed the Server component from their workspace Source Control Workspace. Developer can deliver that component deletion to their stream. For example, remove that component from the stream Source Control as well. Someone added a new component named Work Item to the stream and our developer can accept it into their workspace Source Control Workspace. This will also load its content into the Eclipse workspace.
20 This component is pending gap resolution, which results from accepting a change set with a gap and merging it into the repository workspace instead of accepting all of the change sets that fill the gap. Merge the changes from the source change set (the change set that you are attempting to accept) into a resulting change set in the Gap editor. You can open the editor by selecting the Open Gap editor context menu item on the component node.
21 The resulting change set of the Gap workflow. A resulting change set has not been completed and has a delta overlay at the top right of the icon (representing a link to a source change set; see #23 or #24 below).
22 This outgoing change set was a resulting change set in the Gap editor but is now completed. The delta overlay at the top right of the icon indicates that it is linked to a source change set. In this case, the source change set is also displayed in the incoming folder, so a label decorator of Linked to an Incoming Change Set indicates that these two change sets are semantically equivalent.
23 This is a change set that has a link to one or more work items as well as a link to another change set (since it was the source change set in the Gap editor). This is indicated by a combination of a delta overlay (see #24) and a work item overlay (see #10) at the bottom right of the icon. In the Gap workflow, you can accept a source change set with a gap and merge it into your repository workspace by applying similar changes into a new resulting change set. After the merge is complete, you can create a link between the original change set and resulting change set.
24 This is a change set that has a link to another change set and was the source change set in the Gap editor. This is indicated by a delta overlay at the bottom right of the icon. In the Gap workflow, you can accept an original or source change set with a gap and merge it into your repository workspace by applying similar changes into a new resulting change set. After the merge is complete, you can create a link between the original change set and resulting change set.