Fixed

• Error updating Salesforce FeedItem (Error while parsing Rich Text Content)

Added

• Support Jira fields of type "Group Picker"
• New Many-to-one option for CRM boolean/checkbox fields

Fixed

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

New

• Changed company name from Go2Group to Goldfinger Holdings
• New ability to filter plugin log messages on the "Error Log" screen
• New status display for the plugin's Cron Service
• When a Jira comment is copied to a SFDC Feed, replies to that comment should get copied back to Jira

Fixed

• Prompt CRM User does not work for Cascading Select field types

Added

• Option to send email when the plugin logs an error
• Include the title from Salesforce Notes that are copied to Jira

New

• Copy all Sprints from a Jira Sprint field to CRM
• Allow having other custom fields in Jira with the same name as the plugin's custom fields
• Improve CRM user lookup
• Restricting the "Sync to CRM" operation in Jira should also affect Jira's bulk change
• Option to hide the Issue Operation "Bulk Link to CRM" on the Jira view issue screen

Fixed

• Error when trying to create a new issue using CRM child records: "not a valid Salesforce ID for the type"

Fixed

• The UI Parent settings in the plugin's CRM Record Definitions are being ignored

Fixed

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

Added

• Ability for the create-issue servlet to display the prompt form to CRM users without showing the project field
• Cron Service ability to create a Jira Issue when seeing new record in CRM child object
• Ability to delete a Salesforce attachment from Jira when it is deleted in Salesforce
• Support copying CRM values to the Jira "Insight Object/s" field type from "Insight - Asset Management" plugin

Fixed

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

Added

• Convert Salesforce chatter comments to Jira wiki format
• Preserve rich-text formatting when coping Jira comments to Salesforce Chatter

Fixed

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

New

• Add ability to truncate long Jira values when copied to CRM
• Honor line-breaks for CRM values on Jira view issue screen
• Support the 3rd party custom field type "Deviniti [Dynamic Forms] - Dynamic Cascading Select"

Fixed

• Handle creating a new CRM record from Jira without unlinking existing records

New

• Improve the select list used in JIRA for the plugin's CRM record fields
• Improve configuration screens to handle large numbers of Jira groups
• Option to delete CRM comments in Jira if they are deleted in CRM
• Add ability to specify what Jira values are displayed in the link-issue search results

Fixed

• A Null Pointer Exception is sometimes thrown when copying a Jira custom field value to CRM

Fixed

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

New

• Support linking multiple Jira issues to a single Dynamics CRM record

Fixed

• Comments in JIRA Duplicating
• Some files synced from Salesforce to Jira contain a double file extension
• The plugin option "Auto-set Account/Contact" sometimes throws an error with SugarCRM
• The fields on the create-issue prompt form are sometimes in an illogical order

Fixed

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

New

• Support using Files for Salesforce Case Email attachments
• New attachments option to limit the size of CRM attachments copied to Jira

Fixed

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

Fixed

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

New

• When using the "Comments" button in JIRA, add ability to download any attachments from the CRM comment
• Ability for JIRA users to see and download CRM attachments directly from CRM
• Option to auto-close the results window when using the "Create/Update JIRA" button in CRM
• Ability to copy JIRA comments to Salesforce Chatter Feed

Fixed

• Draft Salesforce Emails creating new record in JIRA with each save
• SQL error with SQL Server
• Issue reporter sometimes not being set on an issue create

New

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

Fixed

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

Fixed

• When multiple field mappings exist for the same JIRA field, sometimes the wrong mapping is used
• The "Sync to CRM" issue operation in JIRA is not reporting attachment errors to the JIRA user
• The create-issue prompt form sometimes fails to include JIRA fields that should be displayed
• The filtering feature on the "JIRA/CRM Field Mappings" config screen does not always list the correct results
• Sometimes the Issue Type field is not shown on the create-issue servlet prompt form
• Problem with JIRA data being displayed in CRM iframes
• In Dynamics CRM, need the ability to copy JIRA values to CRM Option Set fields

Fixed

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

Fixed

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

Added

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

Fixed

• Authentication failure when using Dynamics CRM UK servers
• CRM record searches from JIRA don't handle special characters

New

• Support passing CRM user names or email address to CRM user id fields
• Don't wrap field labels in JIRA
• Add support for the Clone Plus plugin

Fixed

• Cron Service fails to copy Salesforce attachments from Task and Event records

Added

• Suppress wiki rendering for CRM comments copied to JIRA
• Ability to collapse table of CRM values in JIRA
• Option to display HTML form to CRM users even when the JIRA project is specified

Fixed

• Invalid 'crmtoken' error from plugin's servlets

Added

• Better explain the Salesforce "FeedItem requires a filter by Id" error.

Fixed

• ActiveObject syntax error when using the PostgreSQL database
• Error when using a "Update JIRA" custom button in CRM on a child record
• JIRA changes failing to get copied to CRM child records

Fixed

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

Fixed

• The JIRA/CRM Field Mapping "JIRA Default Value" for "reporter" field doesn't work as documented
• ActiveObject syntax error when using the PostgreSQL database
• Salesforce error: Maximum number of duplicate updates in one batch
• Miscellaneous security improvements

Fixed

• Unbalanced parenthesis error for Dynamics CRM

New

• Copy images embedded in Salesforce rich-text fields to JIRA as attachments
• Eliminate unnecessary CRM updates
• Use the JIRA comment header for all comments copied to CRM

• Support using more than one JIRA field to link to the same CRM object
• A better way to display large amounts of CRM data in JIRA
• Append Salesforce Chatter Feed responses to JIRA comments
• Translate rich-text CRM fields when copying to JIRA
• Send email notifications if the plugin's Cron Service stops running
• JIRA field that contains the count of CRM records linked to a JIRA issue
• Option to make all CRM comments copied to JIRA "internal" comments
• In JIRA, display CRM date/time values in the default JIRA format
• Need an easy way to link a group of CRM records to one JIRA issue

Fixed

• Fixed bug in recent change to restrict the Jira projects used by the link-issue search

Fixed

• Jira comments copied to CRM are being duplicated in Jira
• The create-issue prompt form does not populate form fields with CRM values

Added

• Option to limit which Jira issues can be updated by the Cron Service
• Option to sync only new Salesforce Case Emails to Jira
• Make it easier for users to set up custom fields for the plugin
• Limit the link-issue search feature to only Jira projects that can be linked to CRM

Fixed

• When defining Jira/CRM Field Mappings, the CRM field name selected is sometimes formatted incorrectly

New

• Option to copy Salesforce Chatter feed comments to Jira

Fixed

• "missing $$$SOURCE_OBJECTS" error when trying to link a case to an existing Jira issue
• The "Link to existing Jira issue" button in CRM not working for additional CRM definitions

Added

• Ability to copy the Jira sum of time-spent (including sub-tasks) to a CRM field
• When there is more than one field mapping for a field always favor project-specific mappings

New

• Add support for the cloud version of Microsoft Dynamics CRM
• Remove Wiki markup from Jira comments copied to CRM
• Support the Jira Sprint field
• Improve the UI for Jira fields on the prompt form presented to CRM users when creating a new Jira issue
• New option to store Salesforce Case Emails in Jira as attachments
• New option to add a Jira comment when the plugin creates a Jira attachment
• Allow users to set a CRM attachment filename prefix that doesn't contain a colon

Fixed

• The plugin sometimes fails to unlink an issue from CRM after a issue move operation
• Cron Service fails to copy comment from Salesforce field to Jira
• Sometimes the Jira issue updated date is not changed after a sync from CRM to Jira

Fixed

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

Added

• New option to copy Salesforce private comments to Jira Service Desk as internal comments
• New option to control the create time for CRM attachments added to Jira

Fixed

• Java NullPointerException when coping CRM comments to Jira

Added

• Warning when Epic Link field cannot be set from CRM

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

Fixed

• java.lang.UnsupportedOperationException when creating a new issue in Jira

Fixed

• The reading of some SugarCRM Case fields is failing
• Long Jira comments copied to Salesforce are sometimes copied back to Jira causing duplicate comments

Added

• New Jira Bulk Change option to re-copy CRM records to Jira
• Javascript error in IE
• Option to disable adding new values to Jira select lists
• New option to only show CRM records to specified Jira users
• When viewing issues in Jira, make fetching of CRM data asynchronous
• The CRM plugin shows an empty table of CRM values in Jira for deleted CRM records

Fixed

• Plugin's data cache not being used

Fixed

• Jira comments over 4000 characters get copied back from CRM resulting in duplicate comments in Jira
• Javascript bug in the Chrome browser when adding an additional CRM system to the plugin
• Connection timeouts to CRM can occur when copying Jira attachments to CRM

New

• Option to customize the "CRM" link used to manually copy a Jira comment to CRM
• Selective syncing of Jira attachments to CRM
• New option to copy existing Jira attachments to CRM
• Add support for Jira Service Desk custom field type "Organizations"
• Add support for copying CRM fields from Salesforce to Jira for the custom object used to link multiple Jira issues to one CRM record
• Enhance the response message CRM users see after updating Jira so it is clearer what was updated

Fixed

• 'CRM' link used to manually copy Jira comments to CRM sometimes disappears
• SugarCRM session timeouts not handled correctly by the plugin
• Jira Service Desk private comments are being copied to CRM when they shouldn't be

Added

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

• Ability to copy a Jira issue's linked issues information to a CRM field.
• Option to limit "Sync to CRM" Jira issue operation to only permitted users

• Some Salesforce field types not being copied to Jira

Fixed

• Error copying Jira values to Salesforce date/time fields
• Deleting all field mappings causes an error when trying to add a new mapping
• Unable to login to Salesforce Professional Edition
• Error when unlinking a non-Case record from CRM

Fixed

• When syncing a CRM record to Jira, default values are overriding URL values
• Errors when syncing a non-case record from CRM to Jira

Fixed

• Jira default values in field mappings for a specific project are getting used for for all projects
• Version 6.2 of plugin fails to work with forward proxy server
• Body type not correct error when copying Jira attachments to Salesforce
• Cloning an issue in Jira may not update the issue key value in CRM

Fixed

• The setting to only copy public comments from CRM to Jira is not getting saved

Added

• Support for parent/child relationships for CRM records other than Account
• Add ability to create field mappings that are project specific
• Add ability to change the name of the "CRM-1" configuration settings
• Ability to copy a Salesforce Case Comment to only a specified issue in Jira
• Add option to disable Jira email notifications for attachments copied from CRM
• On the Jira Issue Navigator screen, add a new Bulk Change operation for re-syncing Jira issues to CRM
• Replace the use of Apache's AXIS libraries for SOAP connections to CRM systems
• Use CRM create date when adding CRM attachments to Jira

Fixed

• The setting to only copy public comments from CRM to Jira is not getting saved

Added

• Add option to disable Jira email notifications for attachments copied from CRM
• Use CRM create date when adding CRM attachments to Jira

Fixed

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

Added

• Ability to restrict which Jira users are allowed to edit the plugins custom fields
• Add option to limit the time the plugin's cron service runs

Fixed

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

Added

• Add option to limit the time the plugin's cron service runs
• Ensure plugin works with Salesforce servers that no longer support TLS 1.0

• Fix for Salesforce error : 'UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization

Fixed

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

New

• Add option to auto-set Account and Contact for all issues created in Jira
• Support the first and last linked many-to-one field mapping option even when records are linked to Jira at the same time

Fixed

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

New

• Add option to auto-set Account and Contact for all issues created in Jira
• Support the first and last linked many-to-one field mapping option even when records are linked to Jira at the same time

Fixed

• Concurrent Modification Exception when linking an existing Jira issue to a CRM record

New Features

• Add support for timing out network connections to the CRM server
• Support the new Salesforce Notes feature
• Copying comments & attachments to Jira - prevent CRM user match to Jira
• Support Jira Project Picker fields
• Need ability for CRM users to create multiple Jira issues from one CRM record
• Jira comments created by the plugin should only use valid Jira users as the author of the comments
• When multiple CRM attachments are copied to Jira, multiple email notifications are sent
• Allow greater control of the URL used to link to CRM records from Jira.
• The HTML form used to prompt CRM users when creating a new Jira issue should not list invalid projects/issue-types

Fixed

• Concurrent Modification Exception when linking an existing Jira issue to a CRM record

New Features

• Add support for timing out network connections to the CRM server
• Support the new Salesforce Notes feature
• Copying comments & attachments to Jira - prevent CRM user match to Jira
• Support Jira Project Picker fields
• Need ability for CRM users to create multiple Jira issues from one CRM record
• Jira comments created by the plugin should only use valid Jira users as the author of the comments
• When multiple CRM attachments are copied to Jira, multiple email notifications are sent
• Allow greater control of the URL used to link to CRM records from Jira.
• The HTML form used to prompt CRM users when creating a new Jira issue should not list invalid projects/issue-types

Fixed

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

New Features

• Add ability to copy Salesforce Chatter attachments from CRM to Jira
• Option to copy CRM attachments from Salesforce Case Emails to Jira
• Improve "No CRM record could be found" message when creating a Jira issue for a filtered CRM record
• Handle license keys that contain invalid characters

Fixed

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

New Features

• Add ability to copy Salesforce Chatter attachments from CRM to Jira
• Option to copy CRM attachments from Salesforce Case Emails to Jira
• Improve "No CRM record could be found" message when creating a Jira issue for a filtered CRM record
• Handle license keys that contain invalid characters

• Support Jira 7.0

Fixed

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

New Features

• Support linking more than one Jira issue to a single custom object record
• Ability to copy only selected CRM comments to Jira

Fixed

• The plugin sometimes fails to recover from a CRM session timeout
• The Comments Option to copy "All" Jira comments to CRM fails sometimes to copy comments to CRM

New

• Support two or more CRM systems sharing data with the same Jira system
• Add additional fields to the HTML issue create screen
• Ability to resync Jira issues to CRM
• Ability to map CRM field to Epic Link field in Jira (Agile)

Fixed

• Adding a comment in Jira doesn't update CRM with new issue-updated value
• After an issue unlink from CRM the Jira history sometimes uses "Anonymous" even though a "modifying-user" is specifie
• link-issue stopped working with non-case records in V6.0
• Sometimes cron service fails to copy comments from CRM to Jira
• The create-issue servlet sometimes fails to prompt for issue-type

Fixed

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

New

• Ability to map CRM field to Epic Link field in Jira (Agile)

Fixed

• Comments added after link-issue operation are not copied to CRM
• Vulnerability of plugin services to XSS attack
• Salesforce comments from some custom objects are not copied to Jira

Improved

• Plugin should not report a warning when a blank resolution is copied from CRM to Jira

Fixes

• Using MS Dynamics CRM, Jira comments get duplicated in Jira
• Unable to set "Where Clause" for CRM Record Definitions
• New Advanced Settings option to avoid duplicate issues created in Jira from CRM records

Fixes

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

Fixes

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

Fixed

• Edit comment links pulls up Copy to CRM dialog box
• When multiple field mappings are used for a Jira field, sometimes the wrong set of value translations is used
• Jira CRM fields excessively wrap in some browsers

Improvements

• Both issues are linked to CRM custom object after cloning
• No error reported when Jira field used for linking to CRM is out of context

Fixed

• Edit comment links pulls up Copy to CRM dialog box
• When multiple field mappings are used for a Jira field, sometimes the wrong set of value translations is used

Improved

• Both issues are linked to CRM custom object after cloning
• No error reported when Jira field used for linking to CRM is out of context

Fixed in this release

• Errors when creating issues through email (JEMH)
• Cron service incorrectly using Default Values when syncing from CRM
• Cron service sometimes throws an INVALID_FIELD/duplicate field error

New in this release

• Field mapping option to clear a Jira or CRM field when records are unlinked or an issue is deleted
• Add option to Limit Record fields (ie, Salesforce Account, Salesforce Contact) to 1 entry

Fixed in this release

• Errors when creating issues through email (JEMH)

New in this release

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

Fixed in this release

• Duplicate issues are being created in Jira
• Cron job turns off when settings are updated

New in this release

• Add support for Microsoft Dynamics CRM
• Fully support mapping a Jira field to different CRM fields
• When editing an issue in Jira the Case is changed from "New Case" to "none" when Account or Contact added
• From CRM when linking to an existing Jira issue, copy existing comments/attachments from Jira to CRM
• New option to specify the filename prefix used for attachments copied to Jira from CRM
• New option to only copy public CRM comments to Jira
• Add support for setting Jira fields of type "Labels" from CRM
• New Many-to-one field mapping option to only use the value from the last CRM record linked to Jira

Fixed in this release

• Cron job turns off when settings are updated

New

• Add support for Microsoft Dynamics CRM
• From CRM when linking to an existing Jira issue, copy existing comments/attachments from Jira to CRM
• Support setting a default value for CRM Generic Field types
• New option to only copy public CRM comments to Jira
• New Many-to-one field mapping option to only use the value from the last CRM record linked to Jira

Fixed

• Jira issues not updated when unlinked from non-Case records
• The comment option "Copy back to CRM" sometimes doesn't copy the comment back to CRM
• Jira custom fields of type "Text Field (read only)" can't be set to a blank value
• Can't update license key when more than one Account field exists
• The "CRM" link used to copy individual Jira comments to CRM doesn't work from some Jira screens
• Duplicate issues are being created in Jira
• When using the cron job with filter to create Jira issues from CRM, old CRM comments are not copied to Jira
• When editing a Jira issue, Case is changed from "New Case" to "none" when Account or Contact added

Fixed in this release

• Unable to turn off public Salesforce comments option
• Jira issues not updated when unlinked from non-Case records
• The comment option "Copy back to CRM" sometimes doesn't copy the comment back to CRM
• Jira custom fields of type "Text Field (read only)" cannot be set to a blank or empty value
• The "CRM" link used to copy individual Jira comments to CRM doesn't work from some Jira screens
• Can't update license key when more than one Account field exists

Fixed in this release

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

New in this release

• New option on the "Initial Setup" screen to specify the cron service run interval
• Ability to limit the number of CRM records returned by a database query

Fixed in this release

• Cron service is copying CRM Attachments to Jira even though setting is disabled
• Attachments are sometimes copied multiple times from CRM to Jira

New in this release

• Need ability to limit the number of CRM records returned by a database query

Fixed in this release

• CRM values are being copied to Jira even when field mapping is set for new issues only
• When unlinking an issue from CRM the issue key is not cleared from the CRM field

New in this release

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

Fixed in this release

• CRM values are being copied to Jira even when field mapping is set for new issues only
• When unlinking an issue from CRM the issue key is not cleared from the CRM field

New in this release

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

New in version 5.0

• Support Jira Data Center
• Jira Updated Date field is no longer set when sync'ing from CRM if no changes are made

Fixed in this release

• Comments from Salesforce custom object not being copied to Jira
• SugarCRM comments & attachments are sometimes not copied to Jira
• New Jira issues created from CRM are sometimes incorrectly assigned

New in this release

• Unrecognized Jira field errors for 'nonce' and 'sfdcIFrameOrigin'
• Option to allow blank values in Jira required fields
• Syncing only certain values between Jira and CRM

Fixed in this release

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

Fixed in this release

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

Improved in this release

• New option to speed up CRM record searches
• Add Salesforce Case URL to Issue Created/Updated results screen
• Enhance the plugin's crm-info servlet to support more Jira fields

** Bug
* Issue is created in Jira from CRM even if required field is missing a value
* Salesforce is reporting the error: '' is not valid for type xsd:boolean, should be '0', '1', 'true' or 'false'
* Option to make comments copied to Salesforce public not working
* The cron service is not linking newly created issues to CRM

** Improvement
  * Enhance the crm-info servlet to support displaying values from the plugins's Account, Contact and Case fields
  * Support for copying Jira labels to CRM
  * Need option to make Account search use "starts-with" instead of "contains"

** New Feature
  * Option to copy to Jira only the CRM comments made after the Case is first sync'ed to Jira
  * Need option to clear Jira fields other than the Case field when an issue is cloned in Jira.
  * Add the ability to manually copy individual comments from Jira to CRM
  * Add the ability to have two separate buttons in CRM for creating and updating Jira issues
  * Option to unlink the original issue from CRM instead of the new issue after an issue is cloned in Jira
  * Need to copy Jira users Full Name instead of Username to CRM

** Bug
  * Renaming the 'Case' custom field does not change the name in Jira Basic search
  * Plugin threw an IndexOutOfBoundsException
  * 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"
  * The Jira reporter changes when updating from non-case CRM records
  * The comment option "Copy back to CRM" does not work when "Send Notifications" is off

** Bug
  * Renaming the 'Case' custom field does not change the name in Jira Basic search
  * Plugin threw an IndexOutOfBoundsException

** Improvement
  * Enhance the crm-info servlet to support displaying values from the plugins's Account, Contact and Case fields
  * Need option to make Account search use "starts-with" instead of "contains"

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

** Bug
  * When copying CRM comments from a custom Case field, the cron service also copies regular comments to Jira
  * After linking a CRM Case to Jira, a new Jira record isn't created in the CRM custom object
  * The Jira Case field's lookup function fails when the plugin is configured to link multiple Jira issues to a single Case

** Improvement
  * Ability to add date fields to CRM Record Names
  * Improve performance when viewing Jira issues

** New Feature
  * New option to control if a comment from a CRM custom field is sent back to CRM.

** Improvement
  * Add support for Jira Version 6.0

** Bug
  * Status change from CRM is happening in Jira as "Anonymous" user
  * Error: java.lang.IllegalArgumentException: No event type with id
  * Disabled menu items in Case field's drop-down aren't always dimmed

** Bug
  * Fixed SQL error "duplicate field selected"

** Bug
  * Comment author name not being set correctly
  * Field from Salesforce related table not updating Jira field.
  * Javascript error in Jira

** Improvement
  * Add support for Jira Version Picker fields
  * Improve Jira performance with SugarCRM

** Bug
    * Error thrown when copying Salesforce comment to Jira
    * The Case field in Jira not indicating when a new Case/Bug will be created

** Bug
    * Comments from a Salesforce custom field get copied to Jira but not back to Salesforce
    * Attachments added in Jira get copied to Salesforce twice
    * SugarCRM error "org.xml.sax.SAXParseException: Content is not allowed in prolog" caused by case sensitive database names on unix servers
    * Attachments fail to copy from Salesforce to Jira

** Improvement
    * Need ability in Jira to insert a new link to a CRM record without effecting any existing links
    * Only update CRM when the field changed in Jira is mapped to a CRM field
    * Add ability to link a Jira issue to one or more existing SugarCRM bugs
    * Improve the HTML layout for CRM Fields in Jira 5.1
    * When editing a CRM field in Jira make the search match names containing the search string

** New Feature
    * Added a way to identify which CRM case/bug a Jira comment comes from
    * New User Interface for selecting CRM fields

** Bug
    * The author of a comment added to Jira from CRM is sometimes incorrect
    * Error during Jira re-index

** Improvement
    * When setting the Jira assignee from CRM, user email addresses should be valid values
    * Add support for copying values from Salesforce fields of type "Picklist (Multi-Select)"
    * Add support for SugarCRM version 6.4
    * Support more than one Contact in SugarCRM Bug records
    * Add the ability to read a SugarCRM Bug's linked accounts
    * Improve the change history for Jira issues updated from CRM

** New Feature
    * For SugarCRM add the ability to read the email address for a Bug's assigned user

** Bug
    * Changing the issue-type when moving a Jira issue does not update the issue-type field in CRM
    * Status Field always being set to Open even when past bugs are closed.
    * Duplicate comments being created in Jira
    * INVALID_FIELD: No such column 'key' on entity 'Case'
    * CRM comment header doesn't show CRM user name
    * Salesforce comments added by the plugin do not trigger Salesforce notifications
    * Moving an issue in Jira does not update all CRM fields

** Improvement
    * When a CRM Account or Contact is changed the Jira email notification shows the id instead of the name
    * Linking a CRM record to an existing Jira issue should update the issue
    * Improve the performance of copying CRM comments to Jira
    * Error : 'isdtp' is not a valid custom field

** New Feature
    * JQL searches in Jira do not work for CRM fields
    * Add other fields to the Account select list when creating/editing a Jira issue
    * Autoselect Type based on Type from SF when sync button pressed in SF
    * When copying email addresses from CRM to a Jira User Picker field, convert the email address to matching Jira user account
    * Fully support setting Jira custom fields of type "Multi Select" from CRM
    * Add support for copying User Picker values from Jira to CRM
    * Should be able to set Jira Security Level for issues from CRM

** Bug
    * Moving an issue in Jira does not update all CRM fields
    * Linking a CRM record to an existing Jira issue updates the wrong fields
    * When unlinking a Jira issue from CRM the CRM field containing the issue key isn't cleared
    * CRM connection timeouts aren't automatically reset sometimes

** Improvement
    * Correct "'isdtp' is not a valid custom field" message from Salesforce

** Bug
    * Status Field always being set to Open even when past bugs are closed.
    * Duplicate comments being created in Jira
    * Sorting of Jira Issue Navigator column not working with CRM Contact field.
    * INVALID_FIELD: No such column 'key' on entity 'Case'
    * CRM comment header doesn't show CRM user name
    * Salesforce comments added by the plugin do not trigger Salesforce notifications

** Improvement
    * When a CRM Account or Contact is changed the Jira email notification shows the id instead of the name
    * Improve the search fields on the Issue Navigator screen
    * Linking a CRM record to an existing Jira issue should update the issue

** New Feature
    * JQL searches in Jira do not work for CRM fields
    * Add other fields to the Account select list when creating/editing a Jira issue
    * Autoselect Type based on Type from SF when sync button pressed in SF
    * When copying email addresses from CRM to a Jira User Picker field, convert the email address to matching Jira user account
    * Add support for copying User Picker values from Jira to CRM

** Bug
    * Plugin crashes when linking to a Jira issue if the Case field is not configured
    * The "Attachment Prefix" config setting is lost when Jira is restarted

Release Notes - Go2Group CRM Plugin - Version 4.0.2


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

** Improvement
    * Add support for Jira 5.0
    * Improve the search fields on the Issue Navigator screen

** Bug
    * Sorting of Jira Issue Navigator column not working with CRM Contact field.

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

** Improvement
    * When mapping numeric Priorities in Jira the CRM plugin interprets the value as a field value ID
    * Make the crm-info servlet use the configured Jira renderer when displaying values from custom fields

** New Feature
    * Add ability to include Jira customfields on list of Jira issues displayed in CRM (crm-info servlet) for Accounts, Contacts or Cases
    * Modifications to allow integration of crm-info into SFDC case
    * Utility to convert CustomWare links
    * New option to only copy some attachments from Jira to Salesforce

Release Notes - Go2Group CRM Plugin - Version 4.1.2

** Bug
    * In Jira 4.4, Select and Multi Select fields not syncing with CRM
    * When matching Jira users to email addresses, case should not matter
    * The installation of the plugin's listener is duplicated each time Jira 4.4 starts
    * Use of angle brackets in summary causes text to be interpreted as a HTML tag

** Improvement
    * When copying CRM values to Jira Select List fields, automatically add new values to options list
    * When copying CRM values to Jira Multi Select fields, automatically add new values to options list

** New Feature
    * Utility to convert CustomWare links

Release Notes - Go2Group CRM Plugin - Version 4.0.1

** Bug
    * Stack trace displayed on view of CRM generic field in jira 4.3.4

** Improvement
    * When copying CRM values to Jira Select List fields, automatically add new values to options list

** New Feature
    * Include a free license key with the plugin and make the free license expire on Feb 1, 2013
    * Utility to convert CustomWare links

** Bug

    * It should not be possible to link a new Jira issue with a CRM case that is already linked to Jira.
    * Changed javascript to workaround a bug in IE 9
    * Creating an issue in Jira sometimes throws a Null Pointer Exception

** Improvement
    * When copying CRM values to Jira Select List fields, automatically add new values to options list

Support for Jira 4.4

Bug Fixes
    Contact search displaying records twice, listing contacts twice in issue.

New Features
    Make the CRM plugin compatible with Jira's Universal Plugin Manager
    Remove username and password from URL in SFDC to ensure Jira system security.
    Remove support for a permanent license key
    Add support for a free "limited-functionality" license key

Bugs
    * create-issue servlet sometimes shows a blank screen instead of an error message
    * The "search for" box sometimes fails to work for CRM Generic Fields
    * Null Pointer Exception thrown sometimes when using Jira SOAP API
    * When using Jira 4.3, attachments fail to copy from Salesfore to Jira

Improvements
    * On the setup screens, display Value Translations for Jira/CRM Field Mappings in alphabetical order
    * Add field mapping support for fields of the Salesforce Account object