Versions Compared

Version Old Version 15 New Version 16
Changes made by

Wayne Westmoreland

Wayne Westmoreland

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Anchor
CRMFaQTop
CRMFaQTop

...

Section


Column
width15%


Panel
bgColor#f0f0f0
borderStylenone
Navigation Map
label-crm-site-en
label-crm-site-en
cellWidth140
wrapAfter1
cellHeight20



Column
width85%


General Assistance

  1. I just updated to Version 8.x of the CRM Plugin, is my license still valid?
  2. Can I enter my old Goldfinger Holdings license with the latest version of the plugin?
  3. Are all features of the plugin available when using an evaluation license key?
  4. Do you perform customizations if required?
  5. Help! I've run into a problem and can't seem to find a solution. What should I do?
  6. I want to be notified of any CRM Plugin updates, upgrades, or news. What's the best way to do this?
  7. What type of security is built into the CRM Plugin?

Installation

  1. What versions of JIRA and CRM systems work with the CRM Plugin?
  2. What setup is required in my CRM system?
  3. I want to install the CRM Plugin in our Salesforce sandbox environment so we can thoroughly test it before moving it to production. How do I do this?
  4. Does each CRM user need to have a JIRA user account?
  5. What permissions does the CRM Account used by the plugin need?
  6. Our JIRA instance is located on our intranet and is not publicly accessible - Can we still use the CRM Plugin?
  7. How do I upgrade to the latest release of the plugin?
  8. What's the best way for me to upgrade the plugin when I upgrade JIRA?
  9. Will I lose any plugin configuration settings when I upgrade?
  10. Is there a way to backup or copy the plugin configuration settings to another JIRA server?
  11. After installing or upgrading the plugin I get an error message that says "java.lang.IllegalStateException: The bundle is uninstalled"?
  12. After installing or upgrading the plugin I get an error message that says "java.lang.UnsupportedClassVersionError: com/go2group/jira/crm/config/PluginProperties : Unsupported major.minor version 51.0"
  13. Can I keep users from linking a JIRA issue to more than one CRM record?

Usage

  1. How does data get copied between JIRA and CRM?
  2. When I edit a JIRA issue why don't I see the plugin fields for the CRM Account, Contact or Case?
  3. When a new JIRA issue is created from a CRM record, which JIRA project is used?
  4. When the plugin prompts the CRM user for the project in which a new issue is to be created, can I restrict the list of projects and issue types displayed?
  5. How do I set JIRA fields from CRM?
  6. Can I use the custom CRM fields for reports / searches within JIRA?
  7. Is it possible to only synchronize certain Projects within JIRA and leave the others untouched (un-synchronized)?
  8. Is it possible to restrict which types of records in CRM are synchronized with JIRA?
  9. Can I link more than one JIRA Issue to a Single Salesforce Case?
  10. How do I make a field in Salesforce that hyperlinks to the linked issue in JIRA?
  11. How are values in JIRA Multi Select and Cascading Select fields sync'ed with CRM?
  12. How do I use the JIRA REST API to set values in the plugin's CRM fields?
  13. How are Usernames matched between JIRA and CRM?
  14. Can I sync data between JIRA issues and any object in CRM?
  15. How can I make the reporter of a JIRA issue the CRM user who clicked the "Create/Update JIRA" button?'
  16. When CRM data is used to update JIRA, how do I control which JIRA user is used in the change history as the user making the change?
  17. How do I control the author in Jira of comments copied from CRM?
  18. For SugarCRM can I sync issues with Cases instead of Bugs?
  19. Which types of JIRA custom fields can I sync with CRM?
  20. What about the API limits imposed by Salesforce?
  21. Why does the Cron Service fail to copy some Salesforce Files to Jira?
  22. What happens if my company copies our Salesforce records to a new Salesforce organization?

Procurement

  1. How much does the CRM Plugin cost?
  2. Is there an End User License I need to agree to before using the CRM Plugin?
  3. Is the EULA based per instance, or per user?
  4. How can I purchase the CRM Plugin?
  5. If for some reason I am not satisfied with the CRM Plugin, can I apply for a refund?


...

Anchor
i12
i12
12. After installing or upgrading the plugin I get an error message that says "java.lang.UnsupportedClassVersionError: com/go2group/jira/crm/config/PluginProperties : Unsupported major.minor version 51.0"

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
i15
i15
13. Can I keep users from linking a JIRA issue to more than one CRM record?

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.

Top of Page    

...

Usage

Anchor
U0
U0
1. How does data get copied between JIRA and CRM?

...

Anchor
U21
U21
 22. What happens if my company copies our Salesforce records to a new Salesforce organization?

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.

Another possible solution is to use a list of Jira Issue Keys along with the new Salesforce record Ids to create a list of URLs for either the Jira REST API or the CRM plugin's link-issue servlet and then use a utility like curl to execute this whole list of URLs (each URL would update one Jira issue to set the new Salesforce record ids into the appropriate Jira custom fields).

 

Top of Page

...

Procurement

Anchor
q17
q17
1. How much does the CRM Plugin cost?

...

Goldfinger Holdings does not offer refunds. Goldfinger Holdings allows its customers to evaluate the CRM Plugin for a period of 30-days (and beyond where necessary), which allows our customers to determine whether the CRM Plugin will work within their environment. If you have any questions prior to purchasing the CRM Plugin, please contact us.


Top of Page