Create a new user account in your ExtraView site that will be used by the ExtraView integration daemon to communicate with the ExtraView system. Configure this new account with a user role that has access to add, update, and search for records in ExtraView.
The account must be assigned the default business area and project of the records that are to be integrated, or where the integration daemon will create new records propagated from the JIRA system.
It is recommended to create a separate user role for the integration process and configure the new role with just the necessary permissions for the ExtraView records to be integrated. Alternatively, the Administrator role or another user role already configured in the ExtraView site may be used for the purposes of the integration.
The integration daemon requires one ExtraView user defined field for the integration process. Create a new field with a display type of Text Field. Provide this with a Fixed Name of JIRA_ID, for example. This field is automatically populated by the integration daemon with the JIRA record identifier (Key) of the JIRA record mapped to the ExtraView record. The field must have the Allow selection on reports attribute set to Yes. All fields mapped or referenced in the integration must also have the Allow selection on reports attribute set to Yes. This is because the integration daemon runs reports to extract information from ExtraView.
The security permissions for all ExtraView fields mapped in the integration must be Read/Write for the user role assigned to the ExtraView Account used by the ExtraView integration daemon.
The field required by the integration daemon, along with all other fields mapped in the integration, must be configured to be on the following layouts for the records integrated:
The layouts configured can either be defined for all user roles in the system, or can be role-specific layouts configured for the user role assigned to the ExtraView Account created above (less common).
