Lookup CRM Data

This configuration Go2Group's CRM Plugin can be used to lookup account and contact data from a JIRA issues' create or edit screen, and the account and contact can then be stored with (i.e., associated with) the JIRA issue. Searching and sorting of JIRA issues can then be done by your CRM account and/or contact.

For example, on the create screen, the lookups for account and contact look like:

And once the issue is created the issue looks like:

And JIRA issues can be found for an account or contact:

Configuration

To configure the (v1.1-en) Lookup CRM data setup, use the initial install, and follow these additional steps to remove the listener, the service, and the Case custom field.

Remove RemoteTicket Listener

Remove the RemoteTicket listener from the JIRA Administrator/Listeners setup. Removing the listener prevents any new or updated JIRA issues from being communicating (and updating) your CRM data in Salesforce or SugarCrm.

After clicking on ?Listeners?, delete the RemoteTicket listener:

Note your Remote Ticket listener may be called RemoteTicket, SugarRemoteTicket, SalesforceRemoteTicket, etc.

Remove JIRA service

Remove the (v1.1-en) JIRA service from the JIRA Administrator/Listeners setup. Removing the service prevents any new or updated CRM cases from being communicating (and updating) your JIRA issues.

If you're using the 3.2 version of the plugin there is an option on the CRM Setup Advanced Settings to remove the service.

If you're using an earlier version of the plugin use the following instructions.

After clicking on ?Services?, delete the CreateIssueCron service:

Note your CreateIssueCron service may be called SugarCreateIssueCron, SalesforceCreateIssueCron, CreateIssueCron, etc.

Delete the Case Custom Field

The Case custom field is used to record the id of the CRM case object, but since the JIRA and CRM issue data is not synchronized, this field in JIRA can be deleted.

After clicking on Custom Fields, delete the Case field.