Structural conflicts occur when incoming and outgoing change sets include changes to the
same directory namespace, usually the result of moving, removing, or renaming files or folders in a
directory. Conflicts can be automatically or manually resolved without loading content into the
sandbox. This ability simplifies the conflict resolution workflow for cases where result
verification is performed through automated builds.
About this task
You can resolve a structural conflict by working with
the incoming change set that includes the conflicts.
Procedure
- In the Pending Changes view, navigate
to the Unresolved folder of the component in
which the conflict exists.
This folder and the conflicting
files it contains are overlaid with the

icon. (Nonconflicting files have already been added
to your workspace.)
- Move your mouse pointer over the name a conflicting file
to see hover help that identifies the type of conflict and suggests
ways to resolve it.
- Optional:
Configure a preference so that an attempt is made to automatically resolve conflicts on an
accept or resume operation:
-
From the main menu bar, click .
-
Expand the Team entry, expand Jazz Source Control, and click
Changes.
-
On the Changes page, select Automatically attempt to
auto-resolve conflicts on accept and resume and click OK.
Note: You can inspect the merge results after the accept action completes. Any merges that are not
wanted can be undone.
- Right-click the conflicting file and choose a way to resolve
the conflict.
Results
You are prompted to confirm your choice. After you do,
the merge is completed, and the outgoing change set can be delivered.