|
|
The following updates relate to the most recently released versions
Release Notes - Go2Group CRM Plugin - Version 4.2
Bug
- [PLUGINCRM-832] - Sorting of JIRA Issue Navigator column not working with CRM Contact field.
Improvement
Release Notes - Go2Group 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 - Go2Group 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 - Go2Group 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
Release Notes - Go2Group 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 - Go2Group CRM Plugin - Version 4.1
New Feature
Release Notes - Go2Group 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 - Go2Group 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 - Go2Group 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
Release Notes - Go2Group CRM Plugin - Version 3.3.6
Bug
- [PLUGINCRM-782] - Plugin crashes when linking to a JIRA issue if the Case field is not configured
- [PLUGINCRM-817] - The "Attachment Prefix" config setting is lost when JIRA is restarted
Release Notes - Go2Group CRM Plugin - Version 3.3.5
Bug
- [PLUGINCRM-782] - Plugin crashes when linking to a JIRA issue if the Case field is not configured
- [PLUGINCRM-817] - The "Attachment Prefix" config setting is lost when JIRA is restarted
Release Notes - Go2Group CRM Plugin - Version 3.3.5
Bug
- [PLUGINCRM-716] - It should not be possible to link a new JIRA issue with a CRM case that is already linked to JIRA.
- [PLUGINCRM-750] - Changed javascript to workaround a bug in IE 9
- [PLUGINCRM-755] - Creating an issue in JIRA sometimes throws a Null Pointer Exception
Improvement
- [PLUGINCRM-767] - When copying CRM values to JIRA Select List fields, automatically add new values to options list
Release Notes - Go2Group CRM Plugin - Version 3.3.4
Bug
- [PLUGINCRM-715] - The JIRA time-spent value is not copied to CRM when the Issue's work-log is changed.
- [PLUGINCRM-716] - It should not be possible to link a new JIRA issue with a CRM case that is already linked to JIRA.
- [PLUGINCRM-718] - Salesforce case ID is "lost" when creating a new issue from Salesforce if an Account field is mapped to a JIRA field.
- [PLUGINCRM-720] - Searching for issues matching a CRM Case Number does not work
- [PLUGINCRM-732] - Editing a JIRA issue linked to Salesforce can sometimes erase the JIRA issue key from the Salesforce field.
- [PLUGINCRM-737] - When creating new issues from CRM, the HTML screen that prompts for the project sometimes contains bad HTML
- [PLUGINCRM-738] - When creating new issues from CRM, the HTML screen that prompts for the project sometimes shows duplicate Issue Types
Improvement
- [PLUGINCRM-724] - The JIRA "Environment" field should be writable from CRM
- [PLUGINCRM-729] - Add field mapping support for fields of any Salesforce object related to the Case object
New Feature
- [PLUGINCRM-711] - Make URLs and email addresses in Account and Contact fields "clickable"
- [PLUGINCRM-717] - Eliminate the confusion over which Record Definition templates are used
|
