Release Notes - CRM Plugin - Version 9.1.2 (released 11/02/2022)

Bug

• [PLUGINCRM-2815] - Null pointer exception when creating new JIRA issue from a Salesforce record containing an embedded image
• [PLUGINCRM-2823] - Error sending Jira comments with content containing resolved issue keys (strikethrough) to Salesforce chatter feed

Improvement

• [PLUGINCRM-2814] - Support fetching more than one field from a related object in Salesforce

Release Notes - CRM Plugin - Version 8.3.2 (released 11/02/2022)

Bug

• [PLUGINCRM-2815] - Null pointer exception when creating new JIRA issue from a Salesforce record containing an embedded image
• [PLUGINCRM-2823] - Error sending Jira comments with content containing resolved issue keys (strikethrough) to Salesforce chatter feed

Improvement

• [PLUGINCRM-2814] - Support fetching more than one field from a related object in Salesforce

Release Notes - CRM Plugin - Version 9.1.1 (released 9/29/2022)

Improvement

• [PLUGINCRM-2809] - Avoid multiple plugin error emails for the same error
• [PLUGINCRM-2810] - When using a button in Jira to popup a list of CRM comments, include Salesforce Chatter Feed posts
• [PLUGINCRM-2813] - When using the feature to asynchronously copy Jira data to CRM, ensure the latest changes are included

Release Notes - CRM Plugin - Version 8.3.1 (released 9/29/2022)

Improvement

• [PLUGINCRM-2809] - Avoid multiple plugin error emails for the same error
• [PLUGINCRM-2810] - When using a button in Jira to popup a list of CRM comments, include Salesforce Chatter Feed posts
• [PLUGINCRM-2813] - When using the feature to asynchronously copy Jira data to CRM, ensure the latest changes are included

Release Notes - CRM Plugin - Version 9.1.0 (released 9/1/2022)

Bug

• [PLUGINCRM-2798] - Error thrown when an attachment is deleted in CRM and the plugin's Attachments option "Add comment" is enabled
• [PLUGINCRM-2802] - When creating new issues from CRM sometimes the issue-type is not set correctly

New Feature

• [PLUGINCRM-2799] - The "#Issue-Key" option can now be used for CRM attachments
• [PLUGINCRM-2800] - New field mapping options for Jira Watchers
• [PLUGINCRM-2801] - New option to use exact matches when searching CRM records from Jira

Release Notes - CRM Plugin - Version 8.3.0 (released 9/1/2022)

Bug

• [PLUGINCRM-2798] - Error thrown when an attachment is deleted in CRM and the plugin's Attachments option "Add comment" is enabled
• [PLUGINCRM-2802] - When creating new issues from CRM sometimes the issue-type is not set correctly

New Feature

• [PLUGINCRM-2799] - The "#Issue-Key" option can now be used for CRM attachments
• [PLUGINCRM-2800] - New field mapping options for Jira Watchers
• [PLUGINCRM-2801] - New option to use exact matches when searching CRM records from Jira

Release Notes - CRM Plugin - Version 9.0.0 (released 8/2/2022)

New Feature

• [PLUGINCRM-2786] - Support Jira 9.x

Release Notes - CRM Plugin - Version 8.2.5 (released 8/2/2022)

Bug

• [PLUGINCRM-2773] - Cron Service sometimes creates a duplicate issue in Jira

Improvement

• [PLUGINCRM-2785] - Error message from 3rd party validator not displayed

Release Notes - CRM Plugin - Version 8.2.4 (released 6/28/2022)

Bug

• [PLUGINCRM-2757] - When using "SugarCRM (v7.5 or later)", SQL expressions testing for NULL cause errors
• [PLUGINCRM-2766] - Error when sending a Jira value to a Dynamics CRM number field

Improvement

• [PLUGINCRM-2772] - Support custom objects in Dynamics CRM that have names with prefixes other than "new_"

Release Notes - CRM Plugin - Version 8.2.3 (released 6/8/2022)

Bug

• [PLUGINCRM-2752] - Existing comments & attachments in Jira not copied to CRM when an Issue Condition is used to auto create records in CRM
• [PLUGINCRM-2759] - SQL error when a non case record is synced from CRM to Jira after a change in Jira

Release Notes - CRM Plugin - Version 8.2.2 (released 5/25/2022)

Bug

• [PLUGINCRM-2753] - Index out-of-bounds error when converting an HTML comment from CRM to Jira wiki format

New Feature

• [PLUGINCRM-2755] - New field mapping feature to copy more than one CRM field to a Jira field
• [PLUGINCRM-2756] - Ability to add a delay to updates from Jira to CRM

Improvement

• [PLUGINCRM-2727] - Jira Labels field is blanking out after a workflow transition

Release Notes - CRM Plugin - Version 8.2.1 (released 3/23/2022)

Bug

• [PLUGINCRM-2725] - The create-issue prompt form omits Jira fields that have a non-global field context when the Issue Type field is not displayed on the form
• [PLUGINCRM-2729] - The JIRA/CRM Field Mappings screen was erroneously showing a "missing rec def" warning for field mappings to child objects

Release Notes - CRM Plugin - Version 8.2.0 (released 3/3/2022)

Bug

• [PLUGINCRM-2686] - NullPointerException when transitioning issues in Jira
• [PLUGINCRM-2722] - Unable to add new CRM definitions on the Initial Setup screen

New Feature

• [PLUGINCRM-2719] - Add ability to run the Cron Service interactively using a date range

Improvement

• [PLUGINCRM-2649] - Dynamics CRM Notes containing HTML markup show the HTML tags in Jira
• [PLUGINCRM-2651] - The "CRM Attachment added" comment is sometimes marked Internal for Service Desk projects
• [PLUGINCRM-2661] - Ability to set different default values for different custom field contexts of the plugin's Case field
• [PLUGINCRM-2709] - Ability to close a Dynamics CRM case from Jira

Release Notes - CRM Plugin - Version 8.1.3 (released 1/27/2022)

• Fixed problem with recognizing some Atlassian licenses

Release Notes - CRM Plugin - Version 8.1.2 (released 1/26/2022)

New Feature

• [PLUGINCRM-2711] - When using Dynamics CRM, a CRM error is thrown when the plugin writes to CRM LookupType fields

Release Notes - CRM Plugin - Version 8.1.1 (released 1/26/2022)

Bug

• [PLUGINCRM-2710] - Sometimes saving the Value Translations on the JIRA/CRM Field Mappings admin screen fails

Improvement

• [PLUGINCRM-2701] - Plugin fails to recognize custom field names when language translation is used
• [PLUGINCRM-2702] - Locating Jira accounts using an email address should give active accounts priority
• [PLUGINCRM-2704] - Show message when CRM file is rejected due to size

Release Notes - CRM Plugin - Version 8.1.0 (released 1/5/2022)

Bug

• [PLUGINCRM-2671] - When creating a Jira issue from CRM, the default Priority value of the "Default priority scheme" is used rather than the Priority scheme defined for the project
• [PLUGINCRM-2672] - Error during Move Issue operation when the JIRA Field Vlue Count custom field is not in-context
• [PLUGINCRM-2675] - SF Chatter Post replies not attributed to the correct Jira user
• [PLUGINCRM-2696] - Some Dynamics CRM ".name" fields return blanks instead of the name value

New Feature

• [PLUGINCRM-2697] - Support the version 10 REST API for SugarCRM

Release Notes - CRM Plugin - Version 8.0.1 (released 10/25/2021)

New Feature

• Switch to using Atlassian issues license keys instead of vendor issued license keys
• Add support for Japanese language

Improvement

• [PLUGINCRM-2649] - Dynamics CRM Notes containing HTML markup show the HTML tags in Jira
• [PLUGINCRM-2651] - The "CRM Attachment added" comment is sometimes marked Internal for Service Desk projects
• [PLUGINCRM-2661] - Ability to set different default values for different CRM Plugin fields

Release Notes - CRM Plugin - Version 7.2.15 (released 8/25/2021)

Bug

• [PLUGINCRM-2671] - When creating a Jira issue from CRM, the default Priority value of the "Default priority scheme" is used rather than the Priority scheme defined for the project
• [PLUGINCRM-2672] - Error during Move Issue operation when the JIRA Field Vlue Count custom field is not in-context
• [PLUGINCRM-2675] - SF Chatter Post replies not attributed to the correct Jira user
• [PLUGINCRM-2696] - Some Dynamics CRM ".name" fields return blanks instead of the name value

New Feature

• [PLUGINCRM-2697] - Support the version 10 REST API for SugarCRM

Release Notes - CRM Plugin - Version 7.2.15 (released 8/25/2021)

Bug

• [PLUGINCRM-2621] - Salesforce comments copied to Jira Service Desk issues are set to Internal
• [PLUGINCRM-2632] - Jira comments with line breaks within formatted text are not copied to Salesforce

New Feature

• [PLUGINCRM-2635] - Add ability to display option label values in Jira for SugarCRM dropdown and multiselect fields

Release Notes - CRM Plugin - Version 7.2.14 (released 7/30/2021)

Bug

• [PLUGINCRM-2616] - Comment not copied to CRM due to error: element type "s" must be terminated by the matching end-tag "</s>"
• [PLUGINCRM-2624] - Some Jira Service Desk attachments fail to get copied to CRM
• [PLUGINCRM-2625] - Fix problem where Jira comments get copied to CRM and back again overwriting the original comment in Jira

Improvement

• [PLUGINCRM-2626] - Support removing Account and Contact relationships in SugarCRM

Release Notes - CRM Plugin - Version 7.2.13 (released 7/6/2021)

Bug

• [PLUGINCRM-2098] - Fixed HTML error from Salesforce when copying some comments to CRM
• [PLUGINCRM-2613] - Comment header line being added to Jira comments but not removed when copied back to Jira

Release Notes - CRM Plugin - Version 7.2.12 (released 6/30/2021)

Bug

• [PLUGINCRM-2599] - Rollback change to detect when "Create new linked issue" operation is used for cloning

Release Notes - CRM Plugin - Version 7.2.11 (released 6/24/2021)

Bug

• [PLUGINCRM-2610] - Comments from Jira are copied to CRM and then back to Jira editing the original comment in Jira

New Feature

• [PLUGINCRM-2587] - Indicate in Jira that a comment has already been copied to CRM
• [PLUGINCRM-2609] - Option to remove the Public check box from the form when Jira comments are manually copied to CRM

Improvement

• [PLUGINCRM-2599] - Create new linked issue is linking the new issue to the old case, despite the cloning settings
• [PLUGINCRM-2602] - Need ability to edit CRM record field when a fetch error exists
• [PLUGINCRM-2608] - Support setting a SugarCRM Bug's Accounts and Contacts from Jira

Release Notes - CRM Plugin - Version 7.2.10 (released 3/31/2021)

Bug

• [PLUGINCRM-2172] - Using CRM Plugin fields in Jira Queues leads to warnings in log
• [PLUGINCRM-2174] - Issue Option "Update Only Primary Case" sometimes updates a Case other than the first linked Case

New Feature

• [PLUGINCRM-2141] - Support wildcards in value translations of field mappings
• [PLUGINCRM-2190] - Ignore field mappings for Jira fields that aren't in-context for the issue being updated
• [PLUGINCRM-2211] - New option to make syncs from Jira to CRM asynchronous
• [PLUGINCRM-2212] - Option to remove "Return to Case" link on the results window after using a custom button in CRM

Improvement

• [PLUGINCRM-2152] - On the create issue form, only show valid priority options for the select project

Release Notes - CRM Plugin - Version 7.2.9 (released 12/16/2020)

Bug

• [PLUGINCRM-2125] - Error updating CRM FeedItem (Error while parsing Rich Text Content)

New Feature

• [PLUGINCRM-2127] - Need to map from Salesforce to a Jira field of type "Group Picker (single group)".
• [PLUGINCRM-2137] - New Many-to-one option for CRM boolean/checkbox fields

Improvement

• [PLUGINCRM-2129] - Do not show Archived Components in Salesforce when the "prompt user" option is selected

Release Notes - CRM Plugin - Version 6.6.9 (released 12/16/2020)

Bug

• [PLUGINCRM-2125] - Error updating CRM FeedItem (Error while parsing Rich Text Content)

New Feature

• [PLUGINCRM-2127] - Need to map from Salesforce to a Jira field of type "Group Picker (single group)".
• [PLUGINCRM-2137] - New Many-to-one option for CRM boolean/checkbox fields

Release Notes - CRM Plugin - Version 7.2.8 (released 09/23/2020)

Bug

• [PLUGINCRM-2085] - The Threaded feature on the plugin's Error Log screen not accurate with Data Center
• [PLUGINCRM-2092] - Linking a CRM record to an existing Jira issue can erroneously leave CRM fields blank

Improvement

• [PLUGINCRM-2086] - New ability to filter plugin log messages on the "Error Log" screen
• [PLUGINCRM-2088] - New status display for the plugin's Cron Service
• [PLUGINCRM-2089] - When a Jira comment is copied to a SFDC Feed, replies to that comment should get copied back to Jira

Release Notes - CRM Plugin - Version 6.6.8 (released 09/23/2020)

Bug

• [PLUGINCRM-2085] - The Threaded feature on the plugin's Error Log screen not accurate with Data Center
• [PLUGINCRM-2092] - Linking a CRM record to an existing Jira issue can erroneously leave CRM fields blank

Improvement

• [PLUGINCRM-2086] - New ability to filter plugin log messages on the "Error Log" screen
• [PLUGINCRM-2088] - New status display for the plugin's Cron Service
• [PLUGINCRM-2089] - When a Jira comment is copied to a SFDC Feed, replies to that comment should get copied back to Jira

Release Notes - CRM Plugin - Version 7.2.7 (released 07/29/2020)

New Feature

• [PLUGINCRM-2018] - Option to send email when the plugin logs an error

Improvement

• [PLUGINCRM-2006] - Prompt CRM User does not work for Cascading Select field types
• [PLUGINCRM-2012] - Include the title from Salesforce Notes that are copied to Jira

Release Notes - CRM Plugin - Version 6.6.7 (released 07/29/2020)

New Feature

• [PLUGINCRM-2018] - Option to send email when the plugin logs an error

Improvement

• [PLUGINCRM-2006] - Prompt CRM User does not work for Cascading Select field types
• [PLUGINCRM-2012] - Include the title from Salesforce Notes that are copied to Jira

Release Notes - CRM Plugin - Version 7.2.6 (released 05/20/2020)

Improvement

• [PLUGINCRM-1994] - Only the first Sprint from a Jira Sprint field is copied to CRM
• [PLUGINCRM-1995] - Allow having other custom fields in Jira with the same name as the plugin's custom fields
• [PLUGINCRM-1998] - Improve CRM user lookup
• [PLUGINCRM-1999] - Restricting the "Sync to CRM" operation in Jira should also affect Jira's bulk change
• [PLUGINCRM-2000] - Option to hide the Issue Operation "Bulk Link to CRM" on the Jira view issue screen

Release Notes - CRM Plugin - Version 6.6.6 (released 05/20/2020)

Improvement

• [PLUGINCRM-1994] - Only the first Sprint from a Jira Sprint field is copied to CRM
• [PLUGINCRM-1995] - Allow having other custom fields in Jira with the same name as the plugin's custom fields
• [PLUGINCRM-1998] - Improve CRM user lookup
• [PLUGINCRM-1999] - Restricting the "Sync to CRM" operation in Jira should also affect Jira's bulk change
• [PLUGINCRM-2000] - Option to hide the Issue Operation "Bulk Link to CRM" on the Jira view issue screen

Release Notes - CRM Plugin - Version 7.2.5 (released 04/30/2020)

Bug

• [PLUGINCRM-1982] - '5004Y0000016VLy' is not a valid Salesforce ID for the type Jira Dev Issue

Release Notes - CRM Plugin - Version 6.6.5 (released 04/30/2020)

Bug

• [PLUGINCRM-1982] - '5004Y0000016VLy' is not a valid Salesforce ID for the type Jira Dev Issue

Release Notes - CRM Plugin - Version 7.2.4 (released 04/28/2020)

Bug

• [PLUGINCRM-1976] - The UI Parent settings in the plugin's CRM Record Definitions are being ignored

Release Notes - CRM Plugin - Version 6.6.4 (released 04/28/2020)

Bug

• [PLUGINCRM-1976] - The UI Parent settings in the plugin's CRM Record Definitions are being ignored

Release Notes - CRM Plugin - Version 7.2.3 (released 04/16/2020)

Bug

• [PLUGINCRM-1953] - In Jira Data Center, the Cron Service sometimes runs on more than one node at the same time
• [PLUGINCRM-1955] - When an issue linked to CRM is deleted sometimes CRM fields are erroneously blanked out
• [PLUGINCRM-1962] - Cron Service error when copying attachment from CRM child object to Jira

New Feature

• [PLUGINCRM-1954] - Need ability for the create-issue servlet to display the prompt form to CRM users without showing the project field
• [PLUGINCRM-1959] - Cron Service needs ability to create a Jira Issue when seeing new record in CRM child object
• [PLUGINCRM-1972] - Ability to delete a Salesforce attachment from Jira when it is deleted in Salesforce

Improvement

• [PLUGINCRM-1949] - Make the plugin's custom fields work with statistics gadgets
• [PLUGINCRM-1974] - Support copying CRM values to the Jira "Insight Object/s" field type from "Insight - Asset Management" plugin

Release Notes - CRM Plugin - Version 6.6.3 (released 04/16/2020)

Bug

• [PLUGINCRM-1953] - In Jira Data Center, the Cron Service sometimes runs on more than one node at the same time
• [PLUGINCRM-1955] - When an issue linked to CRM is deleted sometimes CRM fields are erroneously blanked out
• [PLUGINCRM-1962] - Cron Service error when copying attachment from CRM child object to Jira

New Feature

• [PLUGINCRM-1954] - Need ability for the create-issue servlet to display the prompt form to CRM users without showing the project field
• [PLUGINCRM-1959] - Cron Service needs ability to create a Jira Issue when seeing new record in CRM child object
• [PLUGINCRM-1972] - Ability to delete a Salesforce attachment from Jira when it is deleted in Salesforce

Improvement

• [PLUGINCRM-1974] - Support copying CRM values to the Jira "Insight Object/s" field type from "Insight - Asset Management" plugin

Release Notes - CRM Plugin - Version 7.2.2 (released 01/30/2020)

Bug

• [PLUGINCRM-1931] - No CRM 'Case" record could be found that matched id:
• [PLUGINCRM-1941] - Salesforce Case Emails copied to Jira get copied back to Salesforce as attachments
• [PLUGINCRM-1942] - The Project/Filter picker for the "Resync to CRM" utility not working in Jira 8
• [PLUGINCRM-1943] - Slashes in CRM attachment names break the download link in Jira

Improvement

• [PLUGINCRM-1930] - Convert Salesforce chatter comments to Jira wiki format
• [PLUGINCRM-1940] - Preserve rich-text formatting when copying Jira comments to Salesforce Chatter

Release Notes - CRM Plugin - Version 6.6.2 (released 01/30/2020)

Bug

• [PLUGINCRM-1931] - No CRM 'Case" record could be found that matched id:
• [PLUGINCRM-1941] - Salesforce Case Emails copied to Jira get copied back to Salesforce as attachments
• [PLUGINCRM-1943] - Slashes in CRM attachment names break the download link in Jira

Improvement

• [PLUGINCRM-1930] - Convert Salesforce chatter comments to Jira wiki format
• [PLUGINCRM-1940] - Preserve rich-text formatting when copying Jira comments to Salesforce Chatter

Release Notes - CRM Plugin - Version 7.2.1 (released 11/26/2019)

Bug

• [PLUGINCRM-1896] - Using the Cron Service to copy a new status from CRM to Jira does not correctly start and stop Service Desk SLAs
• [PLUGINCRM-1921] - Labels for CRM fields in Jira are wrapping
• [PLUGINCRM-1926] - CRM comments added to Jira do not trigger Service Desk automations

New Feature

• [PLUGINCRM-1917] - Add ability to truncate long Jira values when copied to CRM

Improvement

• [PLUGINCRM-1919] - Honor line-breaks for CRM values on Jira view issue screen
• [PLUGINCRM-1920] - Support the 3rd party custom field type "Deviniti [Dynamic Forms] - Dynamic Cascading Select"

Release Notes - CRM Plugin - Version 6.6.1 (released 11/26/2019)

Bug

• [PLUGINCRM-1896] - Using the Cron Service to copy a new status from CRM to Jira does not correctly start and stop Service Desk SLAs

New Feature

• [PLUGINCRM-1917] - Add ability to truncate long Jira values when copied to CRM

Improvement

• [PLUGINCRM-1919] - Honor line-breaks for CRM values on Jira view issue screen
• [PLUGINCRM-1920] - Support the 3rd party custom field type "Deviniti [Dynamic Forms] - Dynamic Cascading Select"

Release Notes - CRM Plugin - Version 7.2 (released 9/24/2019)

Bug

• [PLUGINCRM-1894] - Handle creating a new CRM record from Jira without unlinking existing records
• [PLUGINCRM-1911] - Scrolling the Jira window while CRM record search results are shown cause the search results to close

New Feature

• [PLUGINCRM-1903] - Option to delete CRM comments in Jira if they are deleted in CRM
• [PLUGINCRM-1907] - Add ability to specify what Jira values are displayed in the link-issue search results

Improvement

• [PLUGINCRM-1623] - Improve the select list used in JIRA for the plugin's CRM record fields
• [PLUGINCRM-1909] - Improve configuration screens to handle large numbers of Jira groups

Release Notes - CRM Plugin - Version 6.6 (released 9/24/2019)

Bug

• [PLUGINCRM-1894] - Handle creating a new CRM record from Jira without unlinking existing records

New Feature

• [PLUGINCRM-1903] - Option to delete CRM comments in Jira if they are deleted in CRM
• [PLUGINCRM-1907] - Add ability to specify what Jira values are displayed in the link-issue search results

Improvement

• [PLUGINCRM-1623] - Improve the select list used in JIRA for the plugin's CRM record fields
• [PLUGINCRM-1909] - Improve configuration screens to handle large numbers of Jira groups

Release Notes - CRM Plugin - Versions 6.5.7 and Version 7.1.4 (released 6/28/2019)

Bug

• [PLUGINCRM-1886] - A Null Pointer Exception is sometimes thrown when copying a Jira custom field value to CRM

Release Notes - CRM Plugin - Version 7.1.2 (released 6/17/2019)

Bug

• [PLUGINCRM-1874] - Cron Service sometimes throws error with Jira 8.x
• [PLUGINCRM-1877] - The create-issue prompt form shown to CRM users may omit some Jira fields set for prompting
• [PLUGINCRM-1881] - Jira attachments made in the Service Desk Portal do not copy to CRM
• [PLUGINCRM-1883] - "Remove value from clone issue" not working

New Feature

• [PLUGINCRM-1876] - Support linking multiple Jira issues to a single Dynamics CRM record

Release Notes - CRM Plugin - Version 6.5.5 (released 6/17/2019)

Bug

• [PLUGINCRM-1877] - The create-issue prompt form shown to CRM users may omit some Jira fields set for prompting
• [PLUGINCRM-1881] - Jira attachments made in the Service Desk Portal do not copy to CRM
• [PLUGINCRM-1883] - "Remove value from clone issue" not working

New Feature

• [PLUGINCRM-1876] - Support linking multiple Jira issues to a single Dynamics CRM record

Release Notes - CRM Plugin - Versions 7.1.1 & 6.5.4 (released 5/1/2019)

Bug

• [PLUGINCRM-1862] - Comments in JIRA Duplicating
• [PLUGINCRM-1863] - Some files synced from Salesforce to Jira contain a double file extension
• [PLUGINCRM-1868] - The plugin option "Auto-set Account/Contact" sometimes throws an error with SugarCRM

Improvement

• [PLUGINCRM-1867] - The fields on the create-issue prompt form are sometimes in an illogical order

Release Notes - CRM Plugin - Version 7.1.0 (released 4/4/2019)

Bug

• [PLUGINCRM-1853] - The plugin sometimes fails to copy a renamed Salesforce Files record to Jira
• [PLUGINCRM-1858] - Some types of Salesforce Chatter posts are not copied to Jira
• [PLUGINCRM-1860] - The plugin does not properly log errors from Salesforce Duplicate Rules

Improvement

• [PLUGINCRM-1859] - Support using Files for Salesforce Case Email attachments
• [PLUGINCRM-1861] - New attachments option to limit the size of CRM attachments copied to Jira

Release Notes - CRM Plugin - Version 6.5.3 (released 4/4/2019)

Bug

• [PLUGINCRM-1853] - The plugin sometimes fails to copy a renamed Salesforce Files record to Jira
• [PLUGINCRM-1858] - Some types of Salesforce Chatter posts are not copied to Jira
• [PLUGINCRM-1860] - The plugin does not properly log errors from Salesforce Duplicate Rules

Improvement

• [PLUGINCRM-1859] - Support using Files for Salesforce Case Email attachments
• [PLUGINCRM-1861] - New attachments option to limit the size of CRM attachments copied to Jira

Release Notes - CRM Plugin - Version 7.0 (released 3/14/2019)

• Version for JIRA 8.x

Release Notes - CRM Plugin - Version 6.5.2 (released 3/13/2019)

Bug

• [PLUGINCRM-1844] - CRM records may be updated even if no fields are set
• [PLUGINCRM-1846] - JIRA Default Value from field mapping is sometimes not used
• [PLUGINCRM-1851] - Unable to save record definition for Dynamics CRM

Release Notes - CRM Plugin - Version 6.5.1 (released 1/16/2019)

Bug

• [PLUGINCRM-1834] - Error setting PickList field in Dynamics CRM
• [PLUGINCRM-1836] - The create-issue 'redirect-do-jira' argument has stopped working
• [PLUGINCRM-1838] - Getting error syncing to CRM when the "Update Only Primary Case" option is enabled
• [PLUGINCRM-1840] - Text values with special characters causing error when copying to Dynamics CRM

New Feature

• [PLUGINCRM-1832] - When using the "Comments" button in JIRA, add ability to download any attachments from the CRM comment
• [PLUGINCRM-1833] - Add the ability for JIRA users to see and download CRM attachments directly from CRM
• [PLUGINCRM-1837] - Give users the ability to auto-close the results window when using the "Create/Update JIRA" button in CRM
• [PLUGINCRM-1842] - Copy JIRA comments to Salesforce Chatter Feed

Release Notes - CRM Plugin - Version 6.5 (released 11/29/2018)

Bug

• [PLUGINCRM-1814] - Draft Salesforce Emails creating new record in JIRA with each save
• [PLUGINCRM-1822] - SQL error with SQL Server

New Feature

• [PLUGINCRM-1791] - New attachment option to use a keyword to mark the CRM attachments to be copied to JIRA
• [PLUGINCRM-1823] - Improve the capture of debugging messages from the plugin
• [PLUGINCRM-1829] - Automatically create a new CRM record when a JIRA issue reaches a certain state

Improvement

• [PLUGINCRM-1820] - Make the plugin work better with the new UI introduced in JIRA 7.10

Release Notes - CRM Plugin - Version 6.4.12 (released 10/24/2018)

Bug

• [PLUGINCRM-1816] - Default values from the plugin's field mappings are sometimes ignored
• [PLUGINCRM-1817] - Cron Service may fail to find modified records in Dynamics CRM
• [PLUGINCRM-1818] - Error copying long JIRA comments to Salesforce

Release Notes - CRM Plugin - Version 6.4.11 (released 10/04/2018)

Bug

• [PLUGINCRM-1805] - When multiple field mappings exist for the same JIRA field, sometimes the wrong mapping is used
• [PLUGINCRM-1807] - The "Sync to CRM" issue operation in JIRA is not reporting attachment errors to the JIRA user
• [PLUGINCRM-1808] - The create-issue prompt form sometimes fails to include JIRA fields that should be displayed
• [PLUGINCRM-1809] - The filtering feature on the "JIRA/CRM Field Mappings" config screen does not always list the correct results

Improvement

• [PLUGINCRM-1804] - Sometimes the Issue Type field is not shown on the create-issue servlet prompt form
• [PLUGINCRM-1806] - Fix problem with JIRA data being displayed in CRM iframes.
• [PLUGINCRM-1810] - In Dynamics CRM, need the ability to copy JIRA values to CRM Option Set fields

Release Notes - CRM Plugin - Version 6.4.10 (released 08/09/2018)

Bug

• [PLUGINCRM-1789] - Option to manually copy JIRA attachments to CRM doesn't work with filenames containing "&"
• [PLUGINCRM-1790] - Null Pointer Exception when mapping multiple JIRA issues to one CRM record

Release Notes - CRM Plugin - Version 6.4.9 (released 08/02/2018)

Bug

• [PLUGINCRM-1781] - The plugin's Cron Service fails to copy Salesforce Files attachments to JIRA from a Case record's custom/child object
• [PLUGINCRM-1783] - When syncing a CRM comment to JIRA, the plugin sometimes updates the comment even though it did not change.
• [PLUGINCRM-1784] - Sometimes a Salesforce attachment is duplicated in JIRA
• [PLUGINCRM-1786] - The Cron Service fails to blank out the Salesforce Case custom field used for comments
• [PLUGINCRM-1787] - The "Copy to CRM" link used in JIRA to manually copy attachments to CRM is not appearing properly

Improvement

• [PLUGINCRM-1782] - Avoid duplicate Salesforce records in child objects when other plugins are firing issue events
• [PLUGINCRM-1785] - Include the "Use Salesforce Notes" option on the plugin's "Comment Options" config screen
• [PLUGINCRM-1788] - Eliminate unnecessary change entries for the plugin's record fields when an issue is edited in JIRA

Release Notes - CRM Plugin - Version 6.4.8 (released 06/08/2018)

Bug

• [PLUGINCRM-1774] - Authentication failure when using Dynamics CRM UK servers

New Feature

• [PLUGINCRM-1779] - Support passing CRM user names or email address to CRM user id fields

Improvement

• [PLUGINCRM-1776] - CRM record searches from JIRA don't handle special characters
• [PLUGINCRM-1777] - Don't wrap field labels in JIRA
• [PLUGINCRM-1778] - Add support for the Clone Plus plugin

Release Notes - CRM Plugin - Version 6.4.7 (released 05/09/2018)

Bug

• [PLUGINCRM-1771] - Cron Service fails to copy Salesforce attachments from Task and Event records

New Feature

• [PLUGINCRM-989] - Suppress wiki rendering for CRM comments copied to JIRA
• [PLUGINCRM-1680] - Case Table collapsible?
• [PLUGINCRM-1770] - Option to display HTML form to CRM users even when the JIRA project is specified

Release Notes - CRM Plugin - Version 6.4.6 (released 04/07/2018)

Bug

• [PLUGINCRM-1764] - Invalid 'crmtoken' error from plugin's servlets

Improvement

• [PLUGINCRM-1763] - Better explain the Salesforce "FeedItem requires a filter by Id" error.

Release Notes - CRM Plugin - Version 6.4.5 (released 04/05/2018)

Bug

• [PLUGINCRM-1738] - ActiveObject syntax error when using the PostgreSQL database
• [PLUGINCRM-1753] - Some filename extensions for Salesforce Files not copied correctly to JIRA
• [PLUGINCRM-1759] - The "Open link in new window" setting sometimes was not set correctly
• [PLUGINCRM-1761] - Plugin is unable to copy JIRA attachments to Salesforce Tasks or Events

New Feature

• [PLUGINCRM-1748] - Option to copy JIRA attachments to Salesforce Files
• [PLUGINCRM-1757] - Need ability to delete attachments in CRM when deleted in JIRA
• [PLUGINCRM-1758] - Need a way in JIRA to view only comments from a specific CRM record

Release Notes - CRM Plugin - Version 6.4.4 (released 02/28/2018)

Bug

• [PLUGINCRM-1738] - ActiveObject syntax error when using the PostgreSQL database
• [PLUGINCRM-1746] - Error when using a "Update JIRA" custom button in CRM on a child record
• [PLUGINCRM-1747] - JIRA changes failing to get copied to CRM child records

Release Notes - CRM Plugin - Version 6.4.3 (released 02/24/2018)

Bug

• [PLUGINCRM-1740] - Chatter feed comments containing attachments are not copied to JIRA
• [PLUGINCRM-1742] - Cron service not creating new Jira issues
• [PLUGINCRM-1743] - The JIRA default value in a field mapping sometimes not used when it should

Release Notes - CRM Plugin - Version 6.4.2 (released 02/20/2018)

Bug

• [PLUGINCRM-1737] - The JIRA/CRM Field Mapping "JIRA Default Value" for "reporter" field doesn't work as documented
• [PLUGINCRM-1738] - ActiveObject syntax error when using the PostgreSQL database
• [PLUGINCRM-1739] - Salesforce error: Maximum number of duplicate updates in one batch

Improvement

• [PLUGINCRM-1735] - Miscellaneous security improvements

Release Notes - CRM Plugin - Version 6.4.1 (released 01/30/2018)

Bug

• [PLUGINCRM-1734] - Unbalanced parenthesis error for Dynamics CRM

New Feature

• [PLUGINCRM-1731] - Copy images embedded in Salesforce rich-text fields to JIRA as attachments

Improvement

• [PLUGINCRM-1729] - Eliminate unnecessary CRM updates
• [PLUGINCRM-1732] - Use the JIRA comment header for all comments copied to CRM

Release Notes - CRM Plugin - Version 6.4 (released 01/12/2018)

New Feature

• [PLUGINCRM-1690] - Append Salesforce Chatter Feed responses to JIRA comments
• [PLUGINCRM-1711] - Send email notifications if the plugin's Cron Service stops running
• [PLUGINCRM-1712] - JIRA field that contains the count of CRM records linked to a JIRA issue
• [PLUGINCRM-1717] - Option to make all CRM comments copied to JIRA "internal" comments
• [PLUGINCRM-1721] - Need an easy way to link a group of CRM records to one JIRA issue
• [PLUGINCRM-1726] - Translate rich-text CRM fields when copying to JIRA
• [PLUGINCRM-1727] - A better way to display large amounts of CRM data in JIRA

Improvement

• [PLUGINCRM-1230] - Support using more than one JIRA field to link to the same CRM object
• [PLUGINCRM-1704] - In JIRA, display CRM date/time values in the default JIRA format

Release Notes - CRM Plugin - Version 6.3.5 (released 09/29/2017)

Bug

• [PLUGINCRM-1700] - Search broken when linking an existing JIRA issue to CRM

Release Notes - CRM Plugin - Version 6.3.4 (released 09/28/2017)

Bug

• [PLUGINCRM-1671] - JIRA comments copied to CRM are being duplicated in JIRA
• [PLUGINCRM-1695] - The create-issue prompt form does not populate form fields with CRM values

New Feature

• [PLUGINCRM-1676] - Option to limit which JIRA issues can be updated by the Cron Service
• [PLUGINCRM-1689] - Sync only new Salesforce Case Emails to JIRA

Improvement

• [PLUGINCRM-1681] - Make it easier for users to set up custom fields for the plugin
• [PLUGINCRM-1699] - Limit the link-issue search feature to only JIRA projects that can be linked to CRM

Release Notes - CRM Plugin - Version 6.3.3 (released 07/27/2017)

Bug

• [PLUGINCRM-1668] - When defining JIRA/CRM Field Mappings, the CRM field name selected is sometimes formatted incorrectly

New Feature

• [PLUGINCRM-1669] - New option to copy Salesforce Chatter feed comments to JIRA

Release Notes - CRM Plugin - Version 6.3.2 (released 07/26/2017)

Bug

• [PLUGINCRM-1662] - "missing $$$SOURCE_OBJECTS" error when trying to link a case to an existing JIRA issue
• [PLUGINCRM-1664] - The "Link to existing JIRA issue" button in CRM not working for additional CRM definitions

New Feature

• [PLUGINCRM-1661] - Add ability to copy the JIRA sum of time-spent (including sub-tasks) to a CRM field

Improvement

• [PLUGINCRM-1663] - When there is more than one field mapping for a field always favor project-specific mappings

Release Notes - CRM Plugin - Version 6.3.1 (released 06/13/2017)

Bug

• [PLUGINCRM-1658] - Date and Boolean fields not updating in Salesforce
• [PLUGINCRM-1659] - Error copying JIRA comments to Salesforce notes

Release Notes - CRM Plugin - Version 6.3 (released 06/07/2017)

Bug

• [PLUGINCRM-1652] - The plugin sometimes fails to unlink an issue from CRM after a issue move operation
• [PLUGINCRM-1653] - Cron Service fails to copy comment from Salesforce field to JIRA
• [PLUGINCRM-1656] - Sometimes the JIRA issue updated date is not changed after a sync from CRM to JIRA

New Feature

• [PLUGINCRM-1061] - Support the JIRA Sprint field
• [PLUGINCRM-1568] - Improve the UI for JIRA fields on the prompt form presented to CRM users when creating a new JIRA issue
• [PLUGINCRM-1642] - New option to store Salesforce Case Emails in JIRA as attachments
• [PLUGINCRM-1645] - New option to add a JIRA comment when the plugin creates a JIRA attachment
• [PLUGINCRM-1647] - Remove Wiki markup from JIRA comments copied to CRM
• [PLUGINCRM-1648] - Add support for the cloud version of Microsoft Dynamics CRM

Improvement

• [PLUGINCRM-1657] - Allow users to set a CRM attachment filename prefix that doesn't contain a colon

Release Notes - CRM Plugin - Version 6.2.10 (released 04/20/2017)

Bug

• [PLUGINCRM-1628] - Cron Service creates new JIRA issues from Cases in spite of the "case" record definition setting
• [PLUGINCRM-1631] - Sometimes the prompt screen shown to CRM users contains "$prompt.value" as a field value
• [PLUGINCRM-1632] - Setting the field mapping option "Prompt CRM User" doesn't work for mappings without a CRM Field Name
• [PLUGINCRM-1633] - Adding arguments to the create-issue servlet URL sometimes causes a NullPointerException
• [PLUGINCRM-1635] - The ability to open CRM pages in a new window from the JIRA view issue screen is broken
• [PLUGINCRM-1637] - Changes made to the parent info in some CRM Record Definitions do not persist

New Feature

• [PLUGINCRM-1634] - Need option to copy Salesforce private comments to JIRA Service Desk as internal comments
• [PLUGINCRM-1636] - Add option to control the create time for CRM attachments added to JIRA

Release Notes - CRM Plugin - Version 6.0.11 (released 05/19/2017)

Bug

• [PLUGINCRM-1651] - Java NullPointerException when copying CRM comments to JIRA

Release Notes - CRM Plugin - Version 6.0.10 (released 04/20/2017)

Bug

• [PLUGINCRM-1628] - Cron Service creates new JIRA issues from Cases in spite of the "case" record definition setting
• [PLUGINCRM-1630] - Java exception thrown when copying a CRM value to a JIRA "User Picker" field
• [PLUGINCRM-1631] - Somtimes the prompt screen shown to CRM users contains "$prompt.value" as a field value
• [PLUGINCRM-1632] - Setting the field mapping option "Prompt CRM User" doesn't work for mappings without a CRM Field Name

Release Notes - CRM Plugin - Version 6.2.9 (released 03/29/2017)

Bug

• [PLUGINCRM-1621] - java.lang.UnsupportedOperationException when creating a new issue in JIRA

Release Notes - CRM Plugin - Version 6.2.8 (released 03/16/2017)

Bug

• [PLUGINCRM-1607] - The reading of some SugarCRM Case fields is failing
• [PLUGINCRM-1608] - Long JIRA comments copied to Salesforce are sometimes copied back to JIRA causing duplicate comments

New Feature

• [PLUGINCRM-1611] - New JIRA Bulk Change option to re-copy CRM records to JIRA
• [PLUGINCRM-1612] - Javascript error in IE
• [PLUGINCRM-1613] - Option to disable adding new values to JIRA select lists
• [PLUGINCRM-1614] - New option to only show CRM records to specified JIRA users

Improvement

• [PLUGINCRM-1606] - When viewing issues in JIRA, make fetching of CRM data asynchronous
• [PLUGINCRM-1610] - The CRM plugin shows an empty table of CRM values in JIRA for deleted CRM records

Release Notes - CRM Plugin - Version 6.2.7 (released 02/07/2017)

Bug

• [PLUGINCRM-1599] - Plugin's data cache not being used

Release Notes - CRM Plugin - Version 6.2.6 (released 01/30/2017)

Bug

• [PLUGINCRM-1582] - JIRA comments over 4000 characters get copied back from CRM resulting in duplicate comments in JIRA
• [PLUGINCRM-1594] - Javascript bug in the Chrome browser when adding an additional CRM system to the plugin
• [PLUGINCRM-1595] - Connection timeouts to CRM can occur when copying JIRA attachments to CRM

New Feature

• [PLUGINCRM-1557] - Option to customize the "CRM" link used to manually copy a JIRA comment to CRM
• [PLUGINCRM-1572] - Selective syncing of JIRA attachments to CRM
• [PLUGINCRM-1588] - New option to copy existing JIRA attachments to CRM
• [PLUGINCRM-1589] - Add support for JIRA Service Desk custom field type "Organizations"
• [PLUGINCRM-1590] - New option to copy only "New" CRM attachments to JIRA
• [PLUGINCRM-1593] - Add support for copying CRM fields from Salesforce to JIRA for the custom object used to link multiple JIRA issues to one CRM record

Improvement

• [PLUGINCRM-1571] - Enhance the response message CRM users see after updating JIRA so it is clearer what was updated

Release Notes - CRM Plugin - Version 4.6.8 (released 01/30/2017)

Improvement

• [PLUGINCRM-1523] - Fix for Salesforce error : 'UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization

Release Notes - CRM Plugin - Version 6.2.5 (released 11/08/2016)

Bug

• [PLUGINCRM-1574] - 'CRM' link used to manually copy JIRA comments to CRM sometimes disappears
• [PLUGINCRM-1580] - SugarCRM session timeouts not handled correctly by the plugin

New Feature

• [PLUGINCRM-1567] - Add comment and attachment sync'ing from Salesforce to JIRA for the custom object used to link multiple JIRA issues to one CRM record
• [PLUGINCRM-1573] - Option to limit the value for 'linked-issues-keys' to just one type of issue link
• [PLUGINCRM-1575] - Option to limit "Sync to CRM" JIRA issue operation to only permitted users

Improvement

• [PLUGINCRM-1576] - JIRA Service Desk private comments are being copied to CRM when they shouldn't be

Release Notes - CRM Plugin - Version 6.0.9 (released 11/08/2016)

New Feature

• [PLUGINCRM-1296] - Ability to copy a JIRA issue's linked issues information to a CRM field.
• [PLUGINCRM-1575] - Option to limit "Sync to CRM" JIRA issue operation to only permitted users

Release Notes - CRM Plugin - Version 6.2.4 (released 09/19/2016)

Bug

• [PLUGINCRM-1566] - Some types of Salesforce fields not being copied to JIRA

Release Notes - CRM Plugin - Version 6.2.3 (released 09/15/2016)

Bug

• [PLUGINCRM-1560] - Error copying JIRA values to Salesforce date/time fields
• [PLUGINCRM-1561] - Deleting all field mappings causes an error when trying to add a new mapping
• [PLUGINCRM-1562] - Unable to login to Salesforce Professional Edition
• [PLUGINCRM-1565] - Error when unlinking a non-Case record from CRM

Release Notes - CRM Plugin - Version 6.2.2 (released 08/27/2016)

Bug

• [PLUGINCRM-1555] - When syncing a CRM record to JIRA, default values are overriding URL values
• [PLUGINCRM-1556] - MalformedQueryFault error when syncing a non-case record from CRM to JIRA

Release Notes - CRM Plugin - Version 6.2.1 (released 08/18/2016)

Bug

• [PLUGINCRM-1547] - JIRA default values in field mappings for a specific project are getting used for for all projects
• [PLUGINCRM-1552] - New version of plugin fails to work with forward proxy server
• [PLUGINCRM-1553] - Body type not correct error when copying JIRA attachments to Salesforce
• [PLUGINCRM-1554] - Cloning an issue in JIRA may not update the issue key value in CRM

New Feature

• [PLUGINCRM-1296] - Ability to copy a JIRA issue's linked issues information to a CRM field.
• [PLUGINCRM-1548] - Allow both original and cloned issue to be linked with CRM

Release Notes - CRM Plugin - Version 6.2 (released 08/10/2016)

Bug

• [PLUGINCRM-1546] - The setting to only copy public comments from CRM to JIRA is not getting saved

New Feature

• [PLUGINCRM-1366] - Support for parent/child relationships for CRM records other than Account
• [PLUGINCRM-1507] - Add ability to create field mappings that are project specific
• [PLUGINCRM-1540] - Add ability to change the name of the "CRM-1" configuration settings
• [PLUGINCRM-1542] - Ability to copy a Salesforce Case Comment to only a specified issue in JIRA
• [PLUGINCRM-1544] - Add option to disable JIRA email notifications for attachments copied from CRM

Improvement

• [PLUGINCRM-1535] - On the JIRA Issue Navigator screen, add a new Bulk Change operation for re-syncing JIRA issues to CRM
• [PLUGINCRM-1536] - Replace the use of Apache's AXIS libraries for SOAP connections to CRM systems
• [PLUGINCRM-1545] - Use CRM create date when adding CRM attachments to JIRA

Release Notes - CRM Plugin - Version 6.0.8 (released 08/10/2016)

Bug

• [PLUGINCRM-1546] - The setting to only copy public comments from CRM to JIRA is not getting saved

New Feature

• [PLUGINCRM-1544] - Add option to disable JIRA email notifications for attachments copied from CRM

Improvement

• [PLUGINCRM-1545] - Use CRM create date when adding CRM attachments to JIRA

Release Notes - CRM Plugin - Version 6.1.4 (released 06/24/2016)

Bug

• [PLUGINCRM-1525] - Error when copying multiple attachments from a Salesforce Case Email
• [PLUGINCRM-1526] - The URL used to add an HTML link from JIRA issues to CRM is wrong for new users
• [PLUGINCRM-1528] - Attachments from SugarCRM are sometimes duplicated in JIRA
• [PLUGINCRM-1531] - The issue-type field is sometimes missing from the screen that CRM users use to create new issues in JIRA
• [PLUGINCRM-1533] - When using the Auto-set Account/Contact feature the CRM records are not immediately copied from CRM to JIRA

New Feature

• [PLUGINCRM-1524] - Ability to restrict which JIRA users are allowed to edit the plugins custom fields
• [PLUGINCRM-1537] - Add option to limit the time the plugin's cron service runs

Release Notes - CRM Plugin - Version 6.0.7 (released 06/24/2016)

Bug

• [PLUGINCRM-1525] - Error when copying multiple attachments from a Salesforce Case Email
• [PLUGINCRM-1526] - The URL used to add an HTML link from JIRA issues to CRM is wrong for new users
• [PLUGINCRM-1528] - Attachments from SugarCRM are sometimes duplicated in JIRA
• [PLUGINCRM-1531] - The issue-type field is sometimes missing from the screen that CRM users use to create new issues in JIRA
• [PLUGINCRM-1533] - When using the Auto-set Account/Contact feature the CRM records are not immediately copied from CRM to JIRA

New Feature

• [PLUGINCRM-1537] - Add option to limit the time the plugin's cron service runs

Improvement

• [PLUGINCRM-1527] - Ensure plugin works with Salesforce servers that no longer support TLS 1.0

Release Notes - CRM Plugin - Version 6.1.3 (released 04/01/2016)

Bug

• [PLUGINCRM-1503] - Error when saving a CRM Record Definition that has a blank URL setting
• [PLUGINCRM-1504] - When using SugarCRM and editing a JIRA issue, selecting a CRM Account fails to display the associated Contacts and Bugs
• [PLUGINCRM-1505] - Using MS Dynamics CRM and JIRA 7.x causes a Java Linkage Error
• [PLUGINCRM-1509] - The "Use SQL for finding issues linked to CRM" option fails sometimes
• [PLUGINCRM-1512] - JIRA projects not sorted on the screen that prompts CRM users
• [PLUGINCRM-1513] - Field mapping option for Salesforce Child Relationships not showing
• [PLUGINCRM-1515] - Return-to-record link displayed in the CRM window is broken

New Feature

• [PLUGINCRM-1516] - Add option to auto-set Account and Contact for all issues created in JIRA

Improvement

• [PLUGINCRM-1514] - Support the first and last linked many-to-one field mapping option even when records are linked to JIRA at the same time

Release Notes - CRM Plugin - Version 6.0.6 (released 04/01/2016)

Bug

• [PLUGINCRM-1503] - Error when saving a CRM Record Definition that has a blank URL setting
• [PLUGINCRM-1504] - When using SugarCRM and editing a JIRA issue, selecting a CRM Account fails to display the associated Contacts and Bugs
• [PLUGINCRM-1509] - The "Use SQL for finding issues linked to CRM" option fails sometimes
• [PLUGINCRM-1512] - JIRA projects not sorted on the screen that prompts CRM users
• [PLUGINCRM-1513] - Field mapping option for Salesforce Child Relationships not showing
• [PLUGINCRM-1515] - Return-to-record link displayed in the CRM window is broken

New Feature

• [PLUGINCRM-1516] - Add option to auto-set Account and Contact for all issues created in JIRA

Improvement

• [PLUGINCRM-1514] - Support the first and last linked many-to-one field mapping option even when records are linked to JIRA at the same time

Release Notes - CRM Plugin - Version 6.0.5 and Version 6.1.2 (released 02/02/2016)

Bug

• [PLUGINCRM-1489] - Concurrent Modification Exception when linking an existing JIRA issue to a CRM record

New Feature

• [PLUGINCRM-1492] - Add support for timing out network connections to the CRM server
• [PLUGINCRM-1494] - Support the new Salesforce Notes feature
• [PLUGINCRM-1497] - Copying comments & attachments to JIRA - prevent CRM user match to JIRA
• [PLUGINCRM-1498] - Support JIRA Project Picker fields
• [PLUGINCRM-1500] - Need ability for CRM users to create multiple JIRA issues from one CRM record

Improvement

• [PLUGINCRM-1486] - JIRA comments created by the plugin should only use valid JIRA users as the author of the comments
• [PLUGINCRM-1493] - When multiple CRM attachments are copied to JIRA, multiple email notifications are sent
• [PLUGINCRM-1495] - Allow greater control of the URL used to link to CRM records from JIRA.
• [PLUGINCRM-1502] - The HTML form used to prompt CRM users when creating a new JIRA issue should not list invalid projects/issue-types

Release Notes - CRM Plugin - Version 6.1.1 (released 12/02/2015)

Bug

• [PLUGINCRM-1454] - Plugin fails to set the JIRA "Epic Link" field from CRM
• [PLUGINCRM-1465] - The plugin's cron service is running in multiple threads at the same time
• [PLUGINCRM-1466] - The ability to open CRM pages in a new window from the JIRA view issue screen is broken
• [PLUGINCRM-1476] - Error when the plugin is set to use SQL to find issues linked to CRM
• [PLUGINCRM-1481] - JIRA issue integrity lost when plugin changes issue-type
• [PLUGINCRM-1483] - The "Link to existing issue" button in Salesforce doesn't support many-to-one linking with custom objects

Improvement

• [PLUGINCRM-1160] - Improve "No CRM record could be found" message when creating a JIRA issue for a filtered CRM record
• [PLUGINCRM-1473] - Error thrown when license key contains invalid characters

New Feature

• [PLUGINCRM-1273] - Add ability to copy Salesforce Chatter attachments from CRM to JIRA
• [PLUGINCRM-1482] - Option to copy CRM attachments from Salesforce Case Emails to JIRA

Release Notes - CRM Plugin - Version 6.0.4 (released 12/02/2015)

Bug

• [PLUGINCRM-1454] - Plugin fails to set the JIRA "Epic Link" field from CRM
• [PLUGINCRM-1465] - The plugin's cron service is running in multiple threads at the same time
• [PLUGINCRM-1466] - The ability to open CRM pages in a new window from the JIRA view issue screen is broken
• [PLUGINCRM-1476] - Error when the plugin is set to use SQL to find issues linked to CRM
• [PLUGINCRM-1481] - JIRA issue integrity lost when plugin changes issue-type
• [PLUGINCRM-1483] - The "Link to existing issue" button in Salesforce doesn't support many-to-one linking with custom objects

Improvement

• [PLUGINCRM-1160] - Improve "No CRM record could be found" message when creating a JIRA issue for a filtered CRM record
• [PLUGINCRM-1473] - Error thrown when license key contains invalid characters

New Feature

• [PLUGINCRM-1273] - Add ability to copy Salesforce Chatter attachments from CRM to JIRA
• [PLUGINCRM-1482] - Option to copy CRM attachments from Salesforce Case Emails to JIRA

Release Notes - CRM Plugin - Version 6.1 (released 10/13/2015)

Improvement

• [PLUGINCRM-1467] - Support JIRA 7.0

Release Notes - CRM Plugin - Version 6.0.3 (released 9/25/2015)

Bug

• [PLUGINCRM-1454] - Latest release of plugin fails to set the JIRA "Epic Link" field from CRM
• [PLUGINCRM-1455] - JIRA Issue Navigator searches involving plugin fields fail
• [PLUGINCRM-1457] - The plugin sometimes fails to recover from a CRM session timeout
• [PLUGINCRM-1458] - When adding a new field mapping, the mapping should not be saved if an error is reported

New Feature

• [PLUGINCRM-1452] - Support linking more than one JIRA issue to a single custom object record
• [PLUGINCRM-1459] - Ability to copy only selected CRM comments to JIRA

Release Notes - CRM Plugin - Version 4.6.7 (released 9/25/2015)

Bug

• [PLUGINCRM-1457] - The plugin sometimes fails to recover from a CRM session timeout
• [PLUGINCRM-1461] - The Comments Option to copy "All" JIRA comments to CRM fails sometimes to copy comments to CRM.

Release Notes - CRM Plugin - Version 6.0.2 (released 8/24/2015)

Bug

• [PLUGINCRM-1447] - Sometimes cron service fails to copy comments from CRM to JIRA
• [PLUGINCRM-1448] - The create-issue servlet sometimes fails to prompt for issue-type

Release Notes - CRM Plugin - Version 6.0.1 (released 8/20/2015)

Bug

• [PLUGINCRM-1444] - link-issue doesn't work with non-case records

Release Notes - CRM Plugin - Version 6.0 (released 8/18/2015)

Bug

• [PLUGINCRM-1432] - Adding a comment in JIRA doesn't update CRM with new issue-updated value
• [PLUGINCRM-1440] - After an issue unlink from CRM the JIRA history sometimes uses "Anonymous" even though a "modifying-user" is specified.

New Feature

• [PLUGINCRM-1357] - Add additional fields to the HTML issue create screen
• [PLUGINCRM-1419] - Ability to resync JIRA issues to CRM
• [PLUGINCRM-1420] - Support two or more CRM systems sharing data with the same JIRA system
• [PLUGINCRM-1434] - Ability to map CRM field to Epic Link field in JIRA (Agile)

Release Notes - CRM Plugin - Version 4.6.6 (released 8/18/2015)

Bug

• [PLUGINCRM-1432] - Adding a comment in JIRA doesn't update CRM with new issue-updated value
• [PLUGINCRM-1440] - After an issue unlink from CRM the JIRA history sometimes uses "Anonymous" even though a "modifying-user" is specified.

New Feature

• [PLUGINCRM-1434] - Ability to map CRM field to Epic Link field in JIRA (Agile)

Release Notes - CRM Plugin - Version 5.1.5

Bug

• [PLUGINCRM-1388] - Comments added after link-issue operation are not copied to CRM
• [PLUGINCRM-1400] - Vulnerability of plugin services to XSS attack
• [PLUGINCRM-1411] - Salesforce comments from some custom objects are not copied to JIRA

Improvement

• [PLUGINCRM-1403] - Plugin should not report a warning when a blank resolution is copied from CRM to JIRA

Support

• [PLUGINCRM-1391] - Linking a CRM record to a JIRA issue a 2nd time duplicates comments in CRM

Release Notes - CRM Plugin - Version 4.6.5

Bug

• [PLUGINCRM-1410] - Version 4.6.x of the plugin doesn't work with old versions of JIRA

Release Notes - CRM Plugin - Version 5.1.4

Bug

• [PLUGINCRM-1364] - Using MS Dynamics CRM, JIRA comments get duplicated in JIRA
• [PLUGINCRM-1374] - Unable to set "Where Clause" for CRM Record Definitions
• [PLUGINCRM-1375] - Duplicate issues created in JIRA from CRM records

Release Notes - CRM Plugin - Version 5.1.3

Bug

• [PLUGINCRM-1315] - Some non-english characters are displayed incorrectly in search results
• [PLUGINCRM-1316] - CRM plugin error: "No socket factory for 'https' protocol"
• [PLUGINCRM-1317] - Removal of CRM Record Definition's "Where Clause" does not persist
• [PLUGINCRM-1318] - Changes to the CRM Record Definition for "case" cannot saved
• [PLUGINCRM-1319] - JIRA userpicker field values copied to CRM are in the form Username(Userkey) instead of just Username
• [PLUGINCRM-1328] - Changing the Account, Contact of Case field from a blank value messes up the CRM Record Definitions
• [PLUGINCRM-1329] - Global transitions in JIRA workflows are not recognized by the plugin

Release Notes - CRM Plugin - Version 4.6.4

Bug

• [PLUGINCRM-1319] - JIRA userpicker field values copied to CRM are in the form Username(Userkey) instead of just Username
• [PLUGINCRM-1328] - Changing the Account, Contact of Case field from a blank value messes up the CRM Record Definitions
• [PLUGINCRM-1329] - Global transitions in JIRA workflows are not recognized by the plugin

Release Notes - CRM Plugin - Version 5.1.2

Bug

• [PLUGINCRM-1301] - Edit comment links pulls up Copy to CRM dialog box
• [PLUGINCRM-1308] - When multiple field mappings are used for a JIRA field, sometimes the wrong set of value translations is used
• [PLUGINCRM-1310] - JIRA CRM fields excessively wrap in some browsers

Improvement

• [PLUGINCRM-1295] - Both issues are linked to CRM object after cloning
• [PLUGINCRM-1297] - No error reported when JIRA field used for linking to CRM is out of context

Release Notes - CRM Plugin - Version 4.6.3

Bug

• [PLUGINCRM-1301] - Edit comment links pulls up Copy to CRM dialog box
• [PLUGINCRM-1308] - When multiple field mappings are used for a JIRA field, sometimes the wrong set of value translations is used

Improvement

• [PLUGINCRM-1295] - Both issues are linked to CRM object after cloning
• [PLUGINCRM-1297] - No error reported when JIRA field used for linking to CRM is out of context

Release Notes - CRM Plugin - Version 5.1.1

Bug

• [PLUGINCRM-1287] - Errors when creating issues through email (JEMH)
• [PLUGINCRM-1288] - Cron service incorrectly using Default Values when syncing from CRM
• [PLUGINCRM-1291] - Cron service sometimes throws an INVALID_FIELD/duplicate field error

New Feature

• [PLUGINCRM-731] - Field mapping option to clear a JIRA or CRM field when records are unlinked or an issue is deleted
• [PLUGINCRM-933] - Add option to Limit Record fields (ie, Salesforce Account, Salesforce Contact) to 1 entry

Release Notes - CRM Plugin - Version 5.1

Bug

• [PLUGINCRM-1287] - Errors when creating issues through email (JEMH)
• [PLUGINCRM-1288] - Cron service incorrectly using Default Values when syncing from CRM
• [PLUGINCRM-1291] - Cron service sometimes throws an INVALID_FIELD/duplicate field error

New Feature

• [PLUGINCRM-731] - Field mapping option to clear a JIRA or CRM field when records are unlinked or an issue is deleted
• [PLUGINCRM-933] - Add option to Limit Record fields (ie, Salesforce Account, Salesforce Contact) to 1 entry

Release Notes - CRM Plugin - Version 4.6.2

Bug

• [PLUGINCRM-1287] - Errors when creating issues through email (JEMH)

New Feature

• [PLUGINCRM-731] - Field mapping option to clear a JIRA or CRM field when records are unlinked or an issue is deleted
• [PLUGINCRM-933] - Add option to Limit Record fields (ie, Salesforce Account, Salesforce Contact) to 1 entry
• [PLUGINCRM-1268] - Add support for setting JIRA fields of type "Labels" from CRM

Bug

• [PLUGINCRM-1279] - Duplicate issues are being created in JIRA
• [PLUGINCRM-1285] - Cron job turns off when settings are updated

Release Notes - CRM Plugin - Version 5.1

Improvement

• [PLUGINCRM-1266] - Fully support mapping a JIRA field to different CRM fields
• [PLUGINCRM-1283] - When editing an issue in JIRA the Case is changed from "New Case" to "none" when Account or Contact added

New Feature

• [PLUGINCRM-1214] - From CRM when linking to an existing JIRA issue, copy existing comments/attachments from JIRA to CRM
• [PLUGINCRM-1227] - New option to specify the filename prefix used for attachments copied to JIRA from CRM
• [PLUGINCRM-1242] - Need option to only copy public CRM comments to JIRA
• [PLUGINCRM-1268] - Add support for setting JIRA fields of type "Labels" from CRM
• [PLUGINCRM-1277] - New Many-to-one field mapping option to only use the value from the last CRM record linked to JIRA
• [PLUGINCRM-1281] - Add support for Microsoft Dynamics CRM

Release Notes - CRM Plugin - Version 4.6.1

Bug

• [PLUGINCRM-1285] - Cron job turns off when settings are updated

Release Notes - CRM Plugin - Version 4.6

Bug

• [PLUGINCRM-1246] - JIRA issues not updated when unlinked from non-Case records
• [PLUGINCRM-1250] - The comment option "Copy back to CRM" sometimes doesn't copy the comment back to CRM
• [PLUGINCRM-1251] - JIRA custom fields of type "Text Field (read only)" cannot be set to a blank or empty value
• [PLUGINCRM-1254] - The "CRM" link used to copy individual JIRA comments to CRM doesn't work from some JIRA screens
• [PLUGINCRM-1279] - Duplicate issues are being created in JIRA
• [PLUGINCRM-1282] - When using the cron service with a filter to create new JIRA issues from CRM, pre-existing CRM comments are not copied to JIRA

Improvement

• [PLUGINCRM-1253] - Can't update license key when more than one Account field exists
• [PLUGINCRM-1283] - When editing an issue in JIRA the Case is changed from "New Case" to "none" when Account or Contact added

New Feature

• [PLUGINCRM-1214] - From CRM when linking to an existing JIRA issue, copy existing comments/attachments from JIRA to CRM
• [PLUGINCRM-1236] - Support setting a default value for CRM Generic Field types
• [PLUGINCRM-1242] - Need option to only copy public CRM comments to JIRA
• [PLUGINCRM-1277] - New Many-to-one field mapping option to only use the value from the last CRM record linked to JIRA
• [PLUGINCRM-1281] - Add support for Microsoft Dynamics CRM

Release Notes - CRM Plugin - Version 5.0.3

Bug

• [PLUGINCRM-1245] - Unable to turn off public Salesforce comments
• [PLUGINCRM-1246] - JIRA issues not updated when unlinked from non-Case records
• [PLUGINCRM-1250] - The comment option "Copy back to CRM" sometimes doesn't copy the comment back to CRM
• [PLUGINCRM-1251] - JIRA custom fields of type "Text Field (read only)" cannot be set to a blank or empty value
• [PLUGINCRM-1254] - The "CRM" link used to copy individual JIRA comments to CRM doesn't work from some JIRA screens

Improvement

• [PLUGINCRM-1253] - Can't update license key when more than one Account field exists

Release Notes - CRM Plugin - Version 5.0.2

Bug

• [PLUGINCRM-1226] - [apache.axis.configuration.EngineConfigurationFactoryFinder] Unable to locate a valid EngineConfigurationFactory
• [PLUGINCRM-1231] - Cron service is copying CRM Attachments to JIRA even though setting is disabled
• [PLUGINCRM-1232] - Attachments are sometimes copied multiple times from CRM to JIRA

Improvement

• [PLUGINCRM-1240] - Add option on the "Initial Setup" screen to specify the cron service run interval

New Feature

• [PLUGINCRM-1229] - Need ability to limit the number of CRM records returned by a database query

Release Notes - CRM Plugin - Version 5.0.1

Bug

• [PLUGINCRM-1224] - When unlinking an issue from CRM the issue key is not cleared from the CRM field

Improvement

• [PLUGINCRM-1217] - From JIRA when an issue is linked to a CRM record, sync existing comments & attachments from that CRM record to JIRA
• [PLUGINCRM-1223] - CRM Attachments copied to JIRA do not always show the correct user in the History log

Release Notes - CRM Plugin - Version 5.0

Improvement

• [PLUGINCRM-1215] - JIRA Updated Date field is set when sync'ing from CRM even when no changes are made

New Feature

• [PLUGINCRM-1218] - Support JIRA Data Center

Release Notes - CRM Plugin - Version 4.5.8

Bug

• [PLUGINCRM-1231] - Cron service is copying CRM Attachments to JIRA even though setting is disabled
• [PLUGINCRM-1232] - Attachments are sometimes copied multiple times from CRM to JIRA

New Feature

• [PLUGINCRM-1229] - Need ability to limit the number of CRM records returned by a database query

Release Notes - CRM Plugin - Version 4.5.7

Bug

• [PLUGINCRM-1219] - CRM values are being copied to JIRA even when field mapping is set for new issues only
• [PLUGINCRM-1224] - When unlinking an issue from CRM the issue key is not cleared from the CRM field

Improvement

• [PLUGINCRM-1215] - JIRA Updated Date field is set when sync'ing from CRM even when no changes are made
• [PLUGINCRM-1217] - From JIRA when an issue is linked to a CRM record, sync existing comments & attachments from that CRM record to JIRA
• [PLUGINCRM-1221] - CRM attachments using the same filename don't all get copied to JIRA
• [PLUGINCRM-1223] - CRM Attachments copied to JIRA do not always show the correct user in the History log

Release Notes - CRM Plugin - Version 4.5.6

Bug

• [PLUGINCRM-1211] - Link Issue button throws "missing value" error

Release Notes - CRM Plugin - Version 4.5.5

Bug

• [PLUGINCRM-1177] - Some Value Translation settings do not survive a JIRA restart
• [PLUGINCRM-1182] - Unlinking from CRM shows change made by Anonymous in JIRA
• [PLUGINCRM-1183] - JIRA Value Translations are done incorrectly when copying the same JIRA value to two different CRM fields
• [PLUGINCRM-1190] - Value Translation fails when CRM object names use different character case
• [PLUGINCRM-1196] - Option to always create a CRM record from JIRA causes error in create-issue servlet
• [PLUGINCRM-1204] - modifying-user field is being used on issue creates when it is set for updates only
• [PLUGINCRM-1207] - Field Mappings to copy CRM values to JIRA only for updated issues do not work

Improvement

• [PLUGINCRM-1175] - New comment option to specify time period to use to determine "New" comments

New Feature

• [PLUGINCRM-1101] - New option to use the minimum or maximum value when copying multiple CRM records to one JIRA issue

Release Notes - CRM Plugin - Version 4.5.4

Bug

• [PLUGINCRM-1165] - Comments from Salesforce custom object not being copied to JIRA
• [PLUGINCRM-1166] - SugarCRM comments & attachments are sometimes not copied to JIRA
• [PLUGINCRM-1172] - New Jira issues created from CRM are sometimes incorrectly assigned

Improvement

• [PLUGINCRM-1162] - Unrecognized JIRA field errors for 'nonce' and 'sfdcIFrameOrigin'

New Feature

• [PLUGINCRM-1151] - Option to allow blank values in JIRA required fields
• [PLUGINCRM-1157] - Syncing only certain values between JIRA and CRM

Release Notes - CRM Plugin - Version 4.5.3

Bug

• [PLUGINCRM-1133] - Edited comments are copied to SFDC when not originally copied
• [PLUGINCRM-1138] - Cannot change the Account or Contact of a CRM record from JIRA
• [PLUGINCRM-1139] - The Issue Options setting "Auto-set Account/Contact" doesn't update CRM
• [PLUGINCRM-1148] - Error when CRM attachments contain reserved characters in the filename.

Release Notes - CRM Plugin - Version 4.5.2

Bug

• [PLUGINCRM-1120] - Typing pauses in the CRM search box can result in a missed search
• [PLUGINCRM-1122] - Linking a CRM record to a JIRA issue sometimes fails to store the issue key in CRM
• [PLUGINCRM-1125] - Invalid and required JIRA values from CRM are not getting reported correctly
• [PLUGINCRM-1129] - Column sorting on the crm-info results table doesn't work
• [PLUGINCRM-1131] - Adding Salesforce CaseEmails to JIRA sometimes fails to set the author of the JIRA comment correctly

Improvement

• [PLUGINCRM-1132] - New option to speed up CRM record searches

New Feature

• [PLUGINCRM-1126] - Add Salesforce Case URL to Issue Created/Updated results screen
• [PLUGINCRM-1128] - Enhance the plugin's crm-info servlet to support more JIRA fields

Release Notes - CRM Plugin - Version 4.5.1

Bug

• [PLUGINCRM-1114] - Nav bar should not be displayed when editing field mappings

Release Notes - CRM Plugin - Version 4.5

Bug

• [PLUGINCRM-1081] - JIRA issue stays linked to CRM record if issue key is changed in CRM
• [PLUGINCRM-1089] - Issue updated date is incorrect after syncing comment from CRM to JIRA
• [PLUGINCRM-1106] - Multi-value custom fields in JIRA not always set correctly when the issue is linked to more than one CRM record
• [PLUGINCRM-1109] - When creating a new CRM Case from JIRA, a new record in the Case's child object doesn't get created
• [PLUGINCRM-1110] - Unable to link a 2nd JIRA issue to a Case

Improvement

• [PLUGINCRM-1080] - Ability to sort by Salesforce fields when viewing an issue in JIRA
• [PLUGINCRM-1085] - CRM Field Mapping name cannot exceed 50 Characters
• [PLUGINCRM-1087] - Support CRM checkbox fields
• [PLUGINCRM-1102] - Add an issue search feature to the "Link Issue" servlet

New Feature

• [PLUGINCRM-936] - Need a way for CRM users to unlink a Case from a JIRA Issue
• [PLUGINCRM-1074] - Would like plugin to not copy blank values from CRM to JIRA
• [PLUGINCRM-1090] - Improve how edited comments in JIRA are handled
• [PLUGINCRM-1093] - When a JIRA comment is deleted also delete the comment in CRM
• [PLUGINCRM-1099] - New option to add multiple CRM values together and store the sum in JIRA

Release Notes - CRM Plugin - Version 4.4.2

Bug

• [PLUGINCRM-1072] - NullPointerException occurring in JIRA 6.1

Improvement

• [PLUGINCRM-1056] - Add support for copying a JIRA issue's project category to CRM
• [PLUGINCRM-1058] - Ability to open a new tab/window with the JIRA issue after creating it from CRM
• [PLUGINCRM-1068] - Support 15 digit Salesforce IDs when using JIRA's REST API
• [PLUGINCRM-1069] - Better control over the formatting of comment headers

New Feature

• [PLUGINCRM-1071] - Add option to always create a new CRM Case when creating a new JIRA issue
• [PLUGINCRM-1077] - Add option to specify how to update JIRA when an issue is linked to multiple CRM records

Release Notes - CRM Plugin - Version 4.4.1

Bug

• [PLUGINCRM-1049] - Issue is created in JIRA from CRM even if required field is missing a value
• [PLUGINCRM-1052] - Salesforce is reporting the error: '' is not valid for type xsd:boolean, should be '0', '1', 'true' or 'false'
• [PLUGINCRM-1054] - Option to make comments copied to Salesforce public not working
• [PLUGINCRM-1055] - The cron service is not linking newly created issues to CRM

Release Notes - CRM Plugin - Version 4.4

Bug

• [PLUGINCRM-1025] - Renaming the 'Case' custom field does not change the name in JIRA Basic search
• [PLUGINCRM-1026] - Plugin threw an IndexOutOfBoundsException
• [PLUGINCRM-1041] - When syncing values from multiple CRM records to a single JIRA issue, the plugin is treating "A, B" as a different value from "B, A"
• [PLUGINCRM-1046] - The JIRA reporter changes when updating from non-case CRM records
• [PLUGINCRM-1047] - The comment option "Copy back to CRM" does not work when "Send Notifications" is off

Improvement

• [PLUGINCRM-847] - Enhance the crm-info servlet to support displaying values from the plugins's Account, Contact and Case fields
• [PLUGINCRM-1023] - Support for copying JIRA labels to CRM
• [PLUGINCRM-1029] - Need option to make Account search use "starts-with" instead of "contains"

New Feature

• [PLUGINCRM-980] - Option to copy to JIRA only the CRM comments made after the Case is first sync'ed to JIRA
• [PLUGINCRM-995] - Need option to clear JIRA fields other than the Case field when an issue is cloned in JIRA.
• [PLUGINCRM-1017] - Add the ability to manually copy individual comments from JIRA to CRM
• [PLUGINCRM-1018] - Add the ability to have two separate buttons in CRM for creating and updating JIRA issues
• [PLUGINCRM-1019] - Option to unlink the original issue from CRM instead of the new issue after an issue is cloned in JIRA
• [PLUGINCRM-1043] - Need to copy JIRA users Full Name instead of Username to CRM

Release Notes - CRM Plugin - Version 4.3.5

Bug

• [PLUGINCRM-1025] - Renaming the 'Case' custom field does not change the name in JIRA Basic search
• [PLUGINCRM-1026] - Plugin threw an IndexOutOfBoundsException

Improvement

• [PLUGINCRM-847] - Enhance the crm-info servlet to support displaying values from the plugins's Account, Contact and Case fields
• [PLUGINCRM-1029] - Need option to make Account search use "starts-with" instead of "contains"

Release Notes - CRM Plugin - Version 4.3.4

Bug

• [PLUGINCRM-1004] - Value translations not happening when JIRA multi-select fields are updated from multiple CRM records
• [PLUGINCRM-1006] - Error message in CRM logs showing priority instead of project
• [PLUGINCRM-1007] - The plugin's "Max Query Size" is sometimes ignored for Salesforce users which affects performance
• [PLUGINCRM-1010] - Account field contains account id twice separated by an ASCII comma
• [PLUGINCRM-1011] - Can't use the URL to populate CRM plugin custom fields on the CreateIssueDetails page

Release Notes - CRM Plugin - Version 4.3.3

Bug

• [PLUGINCRM-993] - When copying CRM comments from a custom Case field, the cron service also copies regular comments to JIRA
• [PLUGINCRM-998] - After linking a CRM Case to JIRA, a new JIRA record isn't created in the CRM custom object
• [PLUGINCRM-1002] - The JIRA Case field's lookup function fails when the plugin is configured to link multiple JIRA issues to a single Case

Improvement

• [PLUGINCRM-996] - Can't put date into Record Name Field
• [PLUGINCRM-997] - Improve performance when viewing JIRA issues

New Feature

• [PLUGINCRM-1000] - When a comment is copied from SFDC to JIRA from the Case Custom Comment field the plugin is copying the comment back to SFDC

Release Notes - CRM Plugin - Version 4.3.2

Improvement

• [PLUGINCRM-991] - Add support for JIRA Version 6.0

Bug

• [PLUGINCRM-985] - Status change from CRM is happening in JIRA as "Anonymous" user
• [PLUGINCRM-987] - Error: java.lang.IllegalArgumentException: No event type with id
• [PLUGINCRM-990] - Disabled menu items in Case field's drop-down aren't always dimmed

Release Notes - CRM Plugin - Version 4.3.1

Bug

• [PLUGINCRM-992] - Cron service is throwing Salesforce error: "duplicate field selected"

Release Notes - CRM Plugin - Version 4.3

Bug

• [PLUGINCRM-961] - Frequent out of memory issue with the Go2Group plugin
• [PLUGINCRM-972] - JIRA Date is not copying correctly to CRM
• [PLUGINCRM-973] - Searches on CRM fields don't work with the new basic search UI in JIRA 5.2
• [PLUGINCRM-974] - Inconsistent syncing after connection issues

Improvement

• [PLUGINCRM-914] - Remove the requirement that the JIRA key must be stored in CRM
• [PLUGINCRM-940] - JIRA comments longer than 4000 characters are not synced to Salesforce
• [PLUGINCRM-943] - Delay network traffic to CRM server to improve performance
• [PLUGINCRM-946] - Update all fields in CRM for all JIRA events
• [PLUGINCRM-951] - Locate crm-plugin.properties in JIRA_HOME as opposed to JIRA_INSTALL
• [PLUGINCRM-957] - Handle larger number of records when reading Cases from Salesforce

New Feature

• [PLUGINCRM-804] - Create CRM Case/Bug from JIRA without providing Contact details
• [PLUGINCRM-861] - Support copying values between JIRA and any Salesforce object
• [PLUGINCRM-927] - When an issue in JIRA is linked to an existing CRM record, sync the data from that CRM record to JIRA
• [PLUGINCRM-928] - New option for the crm-info servlet to specify a search expression
• [PLUGINCRM-937] - Add the ability to set the CRM plugins custom fields using JIRA's REST API
• [PLUGINCRM-944] - Need a way to trigger a JIRA status change from CRM by specifying a JIRA workflow transition ID
• [PLUGINCRM-954] - Option for comments copied to Salesforce to always be "Public"
• [PLUGINCRM-955] - Support copying values between JIRA and any SugarCRM object
• [PLUGINCRM-958] - Option for copying comments to the Salesforce Case record even when using a custom object to hold data from multiple JIRA issues
• [PLUGINCRM-959] - Need to copy one CRM field to two different JIRA fields
• [PLUGINCRM-977] - Add Salesforce Case Emails as comments in JIRA

Task

• [PLUGINCRM-916] - Remove old CRM Case Number Searcher
• [PLUGINCRM-956] - Update plugin to use version 2 of the SugarCRM web services API

Release Notes - CRM Plugin - Version 4.2.5

Bug

• [PLUGINCRM-921] - Author name not being populated correctly
• [PLUGINCRM-924] - Field from related table not updating Jira field.
• [PLUGINCRM-939] - Javascript error in JIRA

Improvement

• [PLUGINCRM-938] - Add support for JIRA Version Picker fields
• [PLUGINCRM-942] - Improve JIRA performance with SugarCRM

Release Notes - CRM Plugin - Version 4.2.4

Bug

• [PLUGINCRM-912] - Error thrown when copying Salesforce comment to JIRA
• [PLUGINCRM-913] - The Case field in JIRA not indicating when a new Case/Bug will be created

Release Notes - CRM Plugin - Version 4.2.3

Bug

• [PLUGINCRM-894] - Comments from a Salesforce custom field get copied to JIRA but not back to Salesforce
• [PLUGINCRM-904] - Attachments added in JIRA get copied to Salesforce twice
• [PLUGINCRM-906] - SugarCRM error "org.xml.sax.SAXParseException: Content is not allowed in prolog" caused by case sensitive database names on unix servers
• [PLUGINCRM-909] - Attachments fail to copy from Salesforce to JIRA

Improvement

• [PLUGINCRM-873] - Need ability in JIRA to insert a new link to a CRM record without effecting any existing links
• [PLUGINCRM-893] - Only update CRM when the field changed in JIRA is mapped to a CRM field
• [PLUGINCRM-900] - Add ability to link a JIRA issue to one or more existing SugarCRM bugs
• [PLUGINCRM-905] - Improve the HTML layout for CRM Fields in JIRA 5.1
• [PLUGINCRM-908] - When editing a CRM field in JIRA make the search match names containing the search string

New Feature

• [PLUGINCRM-678] - Is there a way to identify which SFDC case a comment comes from when using the LINK feature?
• [PLUGINCRM-903] - New User Interface for selecting CRM fields

Release Notes - CRM Plugin - Version 4.2.2

Bug

• [PLUGINCRM-887] - The author of a comment added to JIRA from CRM is sometimes incorrect
• [PLUGINCRM-892] - Error during JIRA re-index

Improvement

• [PLUGINCRM-874] - When setting the JIRA assignee from CRM, user email addresses should be valid values
• [PLUGINCRM-875] - Add support for copying values from Salesforce fields of type "Picklist (Multi-Select)"
• [PLUGINCRM-879] - Add support for SugarCRM version 6.4
• [PLUGINCRM-882] - Support more than one Contact in SugarCRM Bug records
• [PLUGINCRM-883] - Add the ability to read a SugarCRM Bug's linked accounts
• [PLUGINCRM-884] - Improve the change history for JIRA issues updated from CRM

New Feature

• [PLUGINCRM-880] - For SugarCRM add the ability to read the email address for a Bug's assigned user

Release Notes - CRM Plugin - Version 4.2.1

Bug

• [PLUGINCRM-486] - Changing the issue-type when moving a JIRA issue does not update the issue-type field in CRM
• [PLUGINCRM-584] - Status Field always being set to Open even when past bugs are closed.
• [PLUGINCRM-819] - Duplicate comments being created in JIRA
• [PLUGINCRM-837] - INVALID_FIELD: No such column 'key' on entity 'Case'
• [PLUGINCRM-838] - CRM comment header doesn't show CRM user name
• [PLUGINCRM-855] - Salesforce comments added by the plugin do not trigger Salesforce notifications
• [PLUGINCRM-869] - Moving an issue in JIRA does not update all CRM fields

Improvement

• [PLUGINCRM-566] - When a CRM Account or Contact is changed the JIRA email notification shows the id instead of the name
• [PLUGINCRM-850] - Linking a CRM record to an existing JIRA issue should update the issue
• [PLUGINCRM-856] - Improve the performance of copying CRM comments to JIRA
• [PLUGINCRM-867] - Error : 'isdtp' is not a valid custom field

New Feature

• [PLUGINCRM-685] - JQL searches in JIRA do not work for CRM fields
• [PLUGINCRM-713] - Add other fields to the Account select list when creating/editing a JIRA issue
• [PLUGINCRM-813] - Autoselect Type based on Type from SF when sync button pressed in SF
• [PLUGINCRM-846] - When copying email addresses from CRM to a JIRA User Picker field, convert the email address to matching JIRA user account
• [PLUGINCRM-852] - Fully support setting JIRA custom fields of type "Multi Select" from CRM
• [PLUGINCRM-863] - Add support for copying User Picker values from JIRA to CRM
• [PLUGINCRM-868] - Should be able to set JIRA Security Level for issues from CRM

Release Notes - CRM Plugin - Version 4.2

Bug

• [PLUGINCRM-832] - Sorting of JIRA Issue Navigator column not working with CRM Contact field.

Improvement

• [PLUGINCRM-831] - Add support for JIRA 5.0
• [PLUGINCRM-834] - Improve the search fields on the Issue Navigator screen

Release Notes - CRM Plugin - Version 4.1.5

Bug

• [PLUGINCRM-869] - Moving an issue in JIRA does not update all CRM fields
• [PLUGINCRM-870] - Linking a CRM record to an existing JIRA issue updates the wrong fields
• [PLUGINCRM-871] - When unlinking a JIRA issue from CRM the CRM field containing the issue key isn't cleared
• [PLUGINCRM-872] - CRM connection timeouts aren't automatically reset sometimes

Improvement

• [PLUGINCRM-867] - Error : 'isdtp' is not a valid custom field

Release Notes - CRM Plugin - Version 4.1.4

Bug

• [PLUGINCRM-584] - Status Field always being set to Open even when past bugs are closed.
• [PLUGINCRM-819] - Duplicate comments being created in JIRA
• [PLUGINCRM-832] - Sorting of JIRA Issue Navigator column not working with CRM Contact field.
• [PLUGINCRM-837] - INVALID_FIELD: No such column 'key' on entity 'Case'
• [PLUGINCRM-838] - CRM comment header doesn't show CRM user name
• [PLUGINCRM-855] - Salesforce comments added by the plugin do not trigger Salesforce notifications

Improvement

• [PLUGINCRM-566] - When a CRM Account or Contact is changed the JIRA email notification shows the id instead of the name
• [PLUGINCRM-834] - Improve the search fields on the Issue Navigator screen
• [PLUGINCRM-850] - Linking a CRM record to an existing JIRA issue should update the issue

New Feature

• [PLUGINCRM-685] - JQL searches in JIRA do not work for CRM fields
• [PLUGINCRM-713] - Add other fields to the Account select list when creating/editing a JIRA issue
• [PLUGINCRM-813] - Autoselect Type based on Type from SF when sync button pressed in SF
• [PLUGINCRM-846] - When copying email addresses from CRM to a JIRA User Picker field, convert the email address to matching JIRA user account
• [PLUGINCRM-863] - Add support for copying User Picker values from JIRA to CRM

Release Notes - CRM Plugin - Version 4.1.3

Bug

• [PLUGINCRM-782] - Plugin crashes when linking to a JIRA issue if the Case field is not configured
• [PLUGINCRM-790] - The crm-info servlet HTML not styled correctly
• [PLUGINCRM-797] - When creating or editing a issue in JIRA, selecting a CRM Account sometimes does not populate the Case list
• [PLUGINCRM-807] - JIRA custom fields of type "Cascading Select" throw an error when set to a value from CRM
• [PLUGINCRM-810] - Default Priority not set when creating a JIRA issue from CRM
• [PLUGINCRM-812] - Comment author from SF not copied correctly to JIRA using CRON job
• [PLUGINCRM-816] - Restarting JIRA disables the plugin's cron service
• [PLUGINCRM-822] - Plugin's cron service fails to recover after CRM outage
• [PLUGINCRM-824] - JIRA's Import Project fails to import CRM field values
• [PLUGINCRM-825] - Can't display CRM values in JIRA after restarting JIRA when using the Free License
• [PLUGINCRM-826] - Multiple components cannot be set in JIRA from CRM

Improvement

• [PLUGINCRM-736] - When mapping numeric Priorities in JIRA the CRM plugin interprets the value as a field value ID
• [PLUGINCRM-806] - Make the crm-info servlet use the configured JIRA renderer when displaying values from custom fields

New Feature

• [PLUGINCRM-719] - Add ability to include JIRA customfields on list of JIRA issues displayed in CRM (crm-info servlet) for Accounts, Contacts or Cases
• [PLUGINCRM-727] - Modifications to allow integration of crm-info into SFDC case
• [PLUGINCRM-772] - Utility to convert CustomWare links
• [PLUGINCRM-808] - New option to only copy some attachments from JIRA to Salesforce

Release Notes - CRM Plugin - Version 4.1.2

Bug

• [PLUGINCRM-768] - In JIRA 4.4, Select and Multi Select fields not syncing with CRM
• [PLUGINCRM-773] - When matching JIRA users to email addresses, case should not matter
• [PLUGINCRM-774] - The installation of the plugin's listener is duplicated each time JIRA 4.4 starts
• [PLUGINCRM-776] - Use of angle brackets in summary causes text to be interpreted as a HTML tag

Improvement

• [PLUGINCRM-767] - When copying CRM values to JIRA Select List fields, automatically add new values to options list
• [PLUGINCRM-779] - When copying CRM values to JIRA Multi Select fields, automatically add new values to options list

New Feature

• [PLUGINCRM-772] - Utility to convert CustomWare links

Release Notes - CRM Plugin - Version 4.1.1

Bug

• [PLUGINCRM-747] - Stack trace displayed on view of CRM generic field in jira 4.3.4

New Feature

• [PLUGINCRM-761] - Add support for JIRA Studio
• [PLUGINCRM-763] - Include a free license key with the plugin and make the free license expire on Feb 1, 2013

Release Notes - CRM Plugin - Version 4.1

New Feature

• [PLUGINCRM-728] - Support for JIRA 4.4

Release Notes - CRM Plugin - Version 4.0.2

Bug

• [PLUGINCRM-584] - Status Field always being set to Open even when past bugs are closed.
• [PLUGINCRM-807] - JIRA custom fields of type "Cascading Select" throw an error when set to a value from CRM
• [PLUGINCRM-812] - Comment author from SF not copied correctly to JIRA using CRON job
• [PLUGINCRM-819] - Duplicate comments being created in JIRA
• [PLUGINCRM-822] - Plugin's cron service fails to recover after CRM outage
• [PLUGINCRM-837] - INVALID_FIELD: No such column 'key' on entity 'Case'
• [PLUGINCRM-838] - CRM comment header doesn't show CRM user name
• [PLUGINCRM-855] - Salesforce comments added by the plugin do not trigger Salesforce notifications

Release Notes - CRM Plugin - Version 4.0.1

Bug

• [PLUGINCRM-747] - Stack trace displayed on view of CRM generic field in jira 4.3.4

Improvement

• [PLUGINCRM-767] - When copying CRM values to JIRA Select List fields, automatically add new values to options list

New Feature

• [PLUGINCRM-763] - Include a free license key with the plugin and make the free license expire on Feb 1, 2013
• [PLUGINCRM-772] - Utility to convert CustomWare links

Release Notes - CRM Plugin - Version 4.0

Bug

• [PLUGINCRM-432] - Contact search displaying records twice, listing contacts twice in issue.

New Feature

• [PLUGINCRM-730] - Remove username and password from URL in SFDC to ensure JIRA system security.
• [PLUGINCRM-733] - Make the CRM plugin compatible with JIRA's Universal Plugin Manager

Task

• [PLUGINCRM-734] - Remove support for a permanent license key
• [PLUGINCRM-735] - Add support for a free "limited-functionality" license key