| Anchor | ||||
|---|---|---|---|---|
|
...
...
| Anchor | ||||
|---|---|---|---|---|
|
This message means you are using an older version of Java than required by Jira and the CRM plugin. See https://confluence.atlassian.com/display/JIRA/Supported+Platforms. You can see the current version of Java used by Jira by going to your Jira admin screen: System -> System Info and look at the value displayed for Java Version. Updating the version of Java you are using will resolve this problem.
| Anchor | ||||
|---|---|---|---|---|
|
Yes. In Jira, go to the plugin's "CRM Record Definitions" configuration screen. Edit the "case" settings, look in the User Interface Settings section for a setting labeled "Multiple CRM Linking". Uncheck this setting and save the change.
...
Usage
Anchor U0 U0
1. How does data get copied between Jira and CRM?
| U0 | |
| U0 |
...
| Anchor | ||||
|---|---|---|---|---|
|
The CRM Plugin stores Salesforce record Ids in the Jira database (specifically as values for the plugin's custom fields, Account, Contact, Case, etc.). When Salesforce records are migrated to a new Salesforce Organization, these record ids change and all the link data used by the plugin is no longer valid.
To restore the link data, the Jira database has to be modified to replace each old Salesforce record id with whatever its new record id is after the migration. One way to do this is to create a list of all the old CRM record ids and their new ids, this list is then "fed" to some process that would update the Jira database. One way to obtain this list of ids is, prior to migration, create a new custom field in the Salesforce records being migrated and copy the Salesforce field "id" to this custom field, now after the migration, the new records will have the new record id in the "id" field and the old record id in the custom field. Alternatively, one could create a mapping of old ids to another unique value, for example Case Number for Cases would work, and then use this mapping to go from the old record id to the Case Number and from Case Number to the new record id. I'm sure there are other ways to build this list. Once you have such a list you then need to pick a way to update the Jira database, my preference would be to use a SQL client program connecting to whatever database is used with Jira and executing a SQL script (i.e. a list of SQL Update commands) that would update the table that holds the Jira custom field values.
...
| Anchor | ||||
|---|---|---|---|---|
|
Most likely you are sending the Case Id for a Case in one CRM system to a Jira server that is configured to connect to a different CRM system. For example, you may have the custom button in your test Salesforce system pointing at your production Jira system or vice versa.
Click on the custom button that is causing the error and look in the browser's location bar at the URL host name, make sure that is the host name is hostname for the correct Jira system, then log into that same Jira system using an admin account and look at the plugin's "Initial Setup" screen at the CRM Connection settings. If you have more than one CRM system defined on the plugin's "Initial Setup" screen, your URL in CRM needs to indicate to the plugin which CRM connection to use. Check that your URL in CRM includes an argument named "_crm" that is set to the name of the CRM connection. On the plugin's "Initial Setup" screen, for each CRM system you have defined, there is an example of the URL labeled "CRM Button URL".
Once you are sure your custom button URL is using the correct CRM definition, look at the CRM Connection settings for that CRM system definition, that Salesforce Username and URL should go to the same CRM system you were in when you clicked the custom button that caused the error. You may want to manually log into CRM using the same credentials on that "Initial Setup" screen to make sure.
Although not as likely, there is one other possible cause of your error message and that is that the CRM Username you are using on the plugin's "Initial Setup" screen does not have permission in Salesforce to read the CRM record being synced to Jira.
...
Procurement
| Anchor | ||||
|---|---|---|---|---|
|
...