VCS: Branch Details View

The description of the branch. Inserting URLs converts them to hyperlinks when saved. JIRA URLs become hyperlinks and use the ticket value as the name. For example: https://{{yourCompany}}.atlassian.net/browse/EN-6061 becomes EN-6061.

Enter all or part of a module's name to search for it.

By default, the Search field is empty.

Select the method to sort modules by when clicking the Search button. Sort options include:

• Last Modified: Sort from recently edited modules to oldest ones. Corresponds with the Last Modified column.

• A-Z: Sorts modules in alphabetical order.

• Z-A: Sorts modules in reverse alphabetical order.

By default, the Sort By drop-down is set to the Sort By option.

Select the module status type to filter by when clicking the Search button. Options include:

• No Conflict: Filter for branch modules that do not have conflicts with the main module

• Conflict: Filter for branch modules that are out of sync with the main module.

By default, the Select Status drop-down is set to the Select Status option.

Resets the Search, Last Modified, and Select Status fields to their default settings.

Click to search for a module using the values in the Search, Last Modified, and Select Status fields.

This list displays all modules added or marked during the Create Branch process.

Displays the name of the module. The branch name is included in brackets. And, if applicable, the icon displays next to modules that are marked for deletion.

The date and time when the module was last edited.

By default, the module's Last Merged Date displays.

Displays the last Owner or Contributor to edit the module.

Displays the sum of modifications to a branch module. Modules created in the branch start with a value of 1.

The Changes value increases when:

• Adding new components.

• Editing existing components.

• Moving components.

• Deleting components.

• Changing module settings.

• Changing module transforms.

Reverting a change reduces the Changes count. For example, adding a new component increases the Changes value by 1. Removing the new component in the same branch decreases the value by 1.

Displays the conflict status between the branch module and its main module. Module status changes if the branched module does not match the most recent merge of the main module.

The Action button contains context-sensitive options depending on the module's state. These option include:

• Edit: Opens the Module Builder. Available for new, existing, or restored modules in the branch.

• Preview: Opens the module in Express View. Available for new, existing, or restored modules in the branch.

• See Main Module: Opens the branched module's main module in Designer View. Available for modules branched or restored from the main module.

• Leave Comment: Opens the Comments panel for the module. The Comments Scope is set to Module Comments Only.

• Resolve Conflict: Opens the Resolve Conflicts page. Available for branched modules that conflict with the main module.

• View Diffs: Opens the View Diffs page. Available for branched modules that conflict with the main module.

The name of the user who owns the branch.

The name of the Owner or Contributor that submitted the Pull Request.

The date and time the Pull Request was created.

The name of the user assigned to the Approver role. The Approver reviews modules in the Pull Request and approves or rejects them.

The description of the branch entered on the Create a Branch page.

Contains modules submitted for review in the Pull Request. All modules in this list must be approved or rejected before approving the Pull Request.

Displays the module and branch name in brackets.

Displays the name of the main module that the branch module was created from.

Displays the conflict status between the branch module and its main module. Module status changes if the branched module does not match the most recent merge of the main module.

The Approver's decision to include or reject the Module in the merge.

Displays options for the Approver to review, approve, or reject the branch module in the Pull Request. Options include:

• Approve: Marks the module as Approved. Approved modules are merged once the Pull Request is approved.

• Reject: Marks the module as Rejected. Rejecting a branch module prevents the Pull Request from being approved for merge. The Owner and Contributors must resolve the rejected module and submit another Pull Request.

• Review Module: Opens the View Diffs page. The Approver then compares changes between the branched module and the main module before approving or rejecting the branched module changes.

Displays the branch's Pull Request events in a list categorized by the Date & Time category.

The type of Pull Request event. Events include submissions, cancellations, and rejections.

The local date and time of the Pull Request event.

The user that submitted the pull request and their role (Owner or Contributor) in the branch.

The description of the branch. Inserting URLs converts them to hyperlinks when saved. JIRA URLs become hyperlinks and use the ticket value as the name. For example: https://{{yourCompany}}.atlassian.net/browse/EN-6061 becomes EN-6061.

The Branch Activity list displays modifications to the branch, Pull Requests, and comments.

Select the activity type to filter by when clicking the Search button. Options include:

• Comments Only: Displays branch activity that contains comments that include conflict resolutions, branch description, and Pull Request approvals or rejections.

• Actions Only: Displays branch activity actions that include Branch creation and modification, conflict resolution, and Pull Request creation or cancellation.

• All: Displays action and comment types. This setting has the same effect as leaving the Filter drop-down empty.

By default, the Filter drop-down is empty.

Select the method to filter the scope by when clicking the Search button. Filter options include:

• Branch: Displays branch creation and modification activity.

• Pull Request: Displays Pull Request submissions, rejections, and cancellations.

• Module: Displays module comments, conflict resolutions, and rejections or approvals from Pull Requests.

• Component: Displays comments from conflict resolutions.

By default, the Scope drop-down is empty.

Enter the start date you want to filter the Branch Activity list by. The From Date field accepts the mm/dd/yyyy date format.

By default, the From Date field is empty.

Enter the end date you want to filter the Branch Activity list by. The To Date field accepts the mm/dd/yyyy date format.

By default, the To Date field is empty.

Resets the Search, Last Modified, and Select Status fields to their default settings.

Click to search for a module using the values in the Search, Last Modified, and Select Status fields.

The description of the branch. Inserting URLs converts them to hyperlinks when saved. JIRA URLs become hyperlinks and use the ticket value as the name. For example: https://{{yourCompany}}.atlassian.net/browse/EN-6061 becomes EN-6061.

The participants list displays all users added to the branch. Participants are Creator-users defined on the Creator (User) Administration page.

The Creator-user's name and role in the branch.

The participant's Creator-User email.

The Creator-user's ID.

The role permission assigned to the participant.