Like all ExtraView features, integrating ExtraView with Perforce is configurable, and there is no fixed method for providing integration between the two products. ExtraView Corporation provides a sample integration with the code for the integration, based upon a summary of best practices seen across multiple customers. However, it is simple to adapt this best practice and adopt your own methods.
The following is a summary of how the integration may be used:
| ExtraView Activity | Effect |
| Add Issue | Creation of new issues in ExtraView may trigger the creation of new Perforce jobs. Perforce job creation can be conditional upon the selection of one or more configurable field values in ExtraView. Alternatively, new ExtraView issues may be linked to existing jobs in Perforce |
| Edit Issue | When issues in ExtraView are updated, the corresponding Perforce job (or jobs) is also updated, e.g. values entered in mapped fields are replicated in the Perforce job |
| Close Issue | When the status of an ExtraView issue is changed to Closed, the Integration Daemon can be easily configured to update the status of the corresponding Perforce job. This is an example of the use of the replication facilities rather than a standalone feature |
| Reopen Issue | When the status of an ExtraView issue is changed from Closed back to Open, the Integration Daemon can be easily configured to update the status of the corresponding Perforce job. This is an example of the use of the replication facilities rather than a standalone feature |
| Change Status | Since submission of an associated changelist changes the status of a Perforce job to Closed, the Integration Daemon captures ExtraView status other than Open and Closed by utilizing an ExtraView-specific Perforce jobspec field called EVstatus. Whenever the status of an ExtraView issue is updated to a new value, the Perforce job EVstatus field is updated to reflect the current ExtraView status. Note that EVStatus has no special meaning, it is simply a field that can be replicated. The field may be any available field |
| Create / Edit Job | When a job is created or edited in Perforce, it may be mapped to an existing issue in ExtraView, or a corresponding issue is automatically created in ExtraView if none already exists. If a new issue is created, the Perforce Job is subsequently updated to reflect the issue ID in ExtraView |
| Submit Changelist | When a changelist is submitted that fixes one or more jobs, the corresponding ExtraView issues may be updated with the job status, the changelist description, other fields and resulting diffs. Diffs may be uploaded to ExtraView as an attachment to the affected issues or as comments. All field mappings are configurable, according to your needs |
| Close Job | When a job is Closed in Perforce, the Integration Daemon can be easily configured to update the status of the corresponding ExtraView issue |
| Open Job | When a job status is set to Open in Perforce, the Integration Daemon can be easily configured to update the status of the corresponding ExtraView issue |
| Update EVstatus | When the EVstatus field of a Perforce job is edited to reflect another mapped status in ExtraView, the ExtraView issue status is updated accordingly. This is an example of the use of the replication facilities, rather than a standalone feature |
.