Fixed a bug where export action for data migration failed

Fixed a bug where export action for data migration failed

• Fixed a bug where export action for data migration failed

• Fixed a bug where export action for data migration failed

• Fixed a bug where required Jira fields are not rendered while creating new Jira issue based on a remote object

• Fixed a bug where required Jira fields are not rendered while creating new Jira issue based on a remote object

• Fixed a bug where email notification does not get sent during issue commented and issue comment edited events

• Fixed a bug where email notification does not get sent during issue commented and issue comment edited events

• Fixed a bug where Project Mappings icon overlaps with the title
• Fixed a bug where Project Mapping Scheme is empty in Project Summary screen

• Fixed a bug where Project Mappings icon overlaps with the title
• Fixed a bug where Project Mapping Scheme is empty in Project Summary screen

• Fixed a bug where Remote Object Type list is empty
• Fixed a bug where arrow icon is missing from toggle header
• Fixed a bug where Project Mappings appear empty when the Project is not selected in the Connections Wizard

• Fixed a bug where Remote Object Type list is empty
• Fixed a bug where arrow icon is missing from toggle header

Export Jira project key and field name in the exported data for migration.

Export Jira project key and field name in the exported data for migration.

• Fixed Value Mapping not showing up in table.

• Fixed Value Mapping not showing up in table.

App library updates and security patches.

App library updates and security patches.

Fixed a bug where comments were duplicated intermittently

Fixed a bug where comments were duplicated intermittently.

• General performance improvements and usability enhancements.

• General performance improvements and usability enhancements.

• Fixed a bug where synchronization would not work for custom date picker field.

• Fixed a bug where synchronization would not work for custom date picker field.

• Export Jira issue key instead of Jira issue ID in data migration.

• Export Jira issue key instead of Jira issue ID in data migration.

• Fixed an issue related to how the latest version of Chrome browser handles certain cookies.

• Fixed an issue related to how the latest version of Chrome browser handles certain cookies.

• Fixed a bug where an error is thrown in Data Center while syncing comment updates.

• Fixed a bug where an error is thrown in Data Center while syncing comment updates.

• Fixed a bug where Jira issue could not be synced automatically when fetching a third-party custom field.

• Fixed a bug where Jira issue could not be synced automatically when fetching a third-party custom field.

• Fixed a bug where Jira issue could not be synced automatically when fetching a third-party custom field.

• Fixed a bug where Jira issue could not be synced automatically when fetching a third-party custom field.

• Fixed a bug that prevented creating Jira Issues from within Salesforce when using Salesforce Time fields.

• Fixed a bug that prevented creating Jira Issues from within Salesforce when using Salesforce Time fields.

• Fixed a bug that prevented creating Jira Issues from within Salesforce when using Salesforce Time fields.

• Fixed a bug that prevented creating Jira Issues from within Salesforce when using Salesforce Time fields.

• Made some behind-the-scenes improvements

• Made some behind-the-scenes improvements

• Made some behind-the-scenes improvements

• Made some behind-the-scenes improvements

• Removed a module from the plugin OBR file that was no longer being used by the Connector.

• Removed a module from the plugin OBR file that was no longer being used by the Connector.

• Removed a module from the plugin OBR file that was no longer being used by the Connector.

• Removed a module from the plugin OBR file that was no longer being used by the Connector.

• Fixed a bug where cache would not be refreshed after it expired.

• Fixed a bug where cache would not be refreshed after it expired.

• Fixed a bug where cache would not be refreshed after it expired.

• Fixed a bug where cache would not be refreshed after it expired.

• Fixed a bug where custom fields would not have their default values set when creating a Jira Issue from within Salesforce.

• Fixed a bug where custom fields would not have their default values set when creating a Jira Issue from within Salesforce.

• Fixed a bug where custom fields would not have their default values set when creating a Jira Issue from within Salesforce.

• Fixed a bug where custom fields would not have their default values set when creating a Jira Issue from within Salesforce.

• Fix a bug where application link configuration not propagate to all data center nodes

• Fix a bug where application link configuration not propagate to all data center nodes

• Fix a bug where application link configuration not propagate to all data center nodes

• Fix a bug where application link configuration not propagate to all data center nodes

• Standardization of user fields(assignee, reporter, User Picker(single user), User Picker(multiple users)) to synchronize via user key instead of the username. This impacts all customers who have user mapping between Salesforce and Jira. Please refer to the documentation for more information.

• Standardization of user fields(assignee, reporter, User Picker(single user), User Picker(multiple users)) to synchronize via user key instead of the username. This impacts all customers who have user mapping between Salesforce and Jira. Please refer to the documentation for more information.

• Standardization of user fields(assignee, reporter, User Picker(single user), User Picker(multiple users)) to synchronize via user key instead of the username. This impacts all customers who have user mapping between Salesforce and Jira. Please refer to the documentation for more information.

• Standardization of user fields(assignee, reporter, User Picker(single user), User Picker(multiple users)) to synchronize via user key instead of the username. This impacts all customers who have user mapping between Salesforce and Jira. Please refer to the documentation for more information.

New and improved

• Data Center is now supported.

New and improved

• Data Center is now supported.

New and improved

• Data Center is now supported.

New and improved

• Data Center is now supported.

- Fixed synchronization issue with Assignee field when username is changed

- Fixed synchronization issue with Assignee field when username is changed

• Removed the connection cache expiry setting from the Connection Configuration Interface. See the knowledge base article for more information.
• Fixed broken export to cloud feature.

• Removed the connection cache expiry setting from the Connection Configuration Interface. See the knowledge base article for more information.
• Fixed broken export to cloud feature.

- Fixed a performance issue affecting slow loading of Jira issue view.

- Fixed a problem where Remote System Reference is duplicated after upgrading connector version.

- Fixed a performance issue affecting slow loading of Jira issue view.

- Fixed a problem where Remote System Reference is duplicated after upgrading connector version.

Configuration to dispatch issue updated event for associate and unlink action in Manage Application Link.

Configuration to dispatch issue updated event for associate and unlink action in Manage Application Link.

- Minor improvements

- Minor improvements

- Fix duplicate Remote System Reference custom field on Jira project screen tabs

- Fix an issue where Jira required field values does not get recorded in Jira issue when users create issues from Salesforce

- You can now map null values in Jira fields to desired values

- General improvements

Configuration to dispatch issue commented event or issue comment edited event when pulling Salesforce

- Minor improvement

• Now compatible with Jira 7.10

Fixed a problem where if a Multi Remote Object Link field has an invalid Salesforce ID, it will clear all the added links.

New in this release:

• Added support to synchronize files from Salesforce to Jira. This feature can be enabled or disabled on the Mappings screen.

• Compatibility with Jira 7.4
• Fixed an issue creation bug which would happen only when Jira Core is installed and the Sprint field not being available

• Fixed a bug where the Multi Remote Object in Link endpoint would cause duplicate entries in Jira.

• Changes made to Remote Object Links or Multi Remote Object Links via Link Endpoints are now recorded in the Jira Issue History.
• We've included a potential fix for bug where the Connector would suddenly disconnect without giving any warnings. If you still experience issues, please let us know. For more information, view this KB article.

• Remote System Reference table headers are now formatted properly.
• Fixed an issue where it was not possible to add participants in Jira Service Desk issues while the Connector was enabled and if there were any Multi Remote Object Link custom fields created.

• Jira Agile custom fields are now available for mapping configuration.
• Attachment synchronization for Custom Objects are now supported.
• Fixed a bug where email notifications for issue updates from Jira were not being sent after synchronization.

- Fixed a bug where mapped values for checkboxes were not being pushed to Salesforce.

- Evaluators can now reach out to us anytime from within Jira

• Fixed a problem where the remote object's Last Fetch date and time did not reflect the user's local time

New in this release:

• Dual licensing feature now implemented for Jira 6.4.x.
• This means you can use either your existing ServiceRocket license or an Atlassian Marketplace license to continue using this add-on.
• If you have an existing valid ServiceRocket license and want to switch to an Atlassian Marketplace license, you need to uninstall the ServiceRocket license first.
• Likewise, if you have an Atlassian Marketplace license and want to switch to a ServiceRocket license, you will need to uninstall the Atlassian Marketplace license as well.

• Admins can now set the maximum number of results that are returned by SOQL when searching with JQL. View the documentation for more details.

• Now compatible with Jira 7.3

Say goodbye to the old UI and say hello to a more streamlined and friendly user interface that adheres to Atlassian UI guidelines. We've overhauled the Connector so that endpoint and feature configuration pages are now updated with a sleek interface and a look you'll be more familiar with.

Say goodbye to the old UI and say hello to a more streamlined and friendly user interface that adheres to Atlassian UI guidelines. We've overhauled the Connector so that endpoint and feature configuration pages are now updated with a sleek interface and a look you'll be more familiar with.

• Improve export fuctionality

• Improved data exporter

• Improved data exporter

• Salesforce comments that have been pulled into Jira can now be edited and have those edits be reflected back in Salesforce.
• This feature is disabled by default and can be enabled by the Administrator

• Salesforce comments that have been pulled into Jira can now be edited and have those edits be reflected back in Salesforce.
• This feature is disabled by default and can be enabled by the Administrator

• Fixed an issue where the custom Cascading List fields would not appear properly, preventing users from creating issues.

• Fixed an issue where reporter would appear as an unknown user if the Jira user account had an edited username.

• Added a DEBUG logging to provide more information in troubleshooting problems related to [The Connector Has Suddenly Stopped Working] issues.

• Fixed an issue where the custom Cascading List fields would not appear properly, preventing users from creating issues.

• The new dropdown menu for Associate Issues Endpoint was causing issues for certain users so we have reverted back to the old menu for now.

• Fixed an issue where reporter would appear as an unknown user if the Jira user account had an edited username.

• Improved data exporter
• Fixed memory leak

New in this release:

• Dual licensing feature now implemented.
• This means you can use either your existing ServiceRocket license or an Atlassian Marketplace license to continue using this add-on.
• If you have an existing valid ServiceRocket license and want to switch to an Atlassian Marketplace license, you need to uninstall the ServiceRocket license first.
• Likewise, if you have an Atlassian Marketplace license and want to switch to a ServiceRocket license, you will need to uninstall the Atlassian Marketplace license as well.

• Data exporter to assist migration to Salesforce & Jira Cloud Connector (Connection, Mapping and Association).

• Now compatible with Jira 7.0
• Fixed an issue where the Synchronize attachments from Remote System option would be disabled, but it was still syncing.

• Now features Data Center compatibility.

• Fixed a bug causing duplicate attachments for certain file types when pulling changes to Jira.

• Fixed duplicate actions from happening when user clicks on the Associate/Create button multiple times in the Create/Associate endpoint page.

• Custom fields are now importable via Project Import

• Fixed a bug resulting in duplicated comments after deleting Jira comments.
• Fixed a concurrency issue resulting in duplicated comments when multiple requests are pulling comments from Salesforce at the same time.

New in this release:

• Fixed an issue preventing users from creating issue from Create endpoint if a Version Picker field is required.

New in this release:

• Fixed inconsistency when editing connections if the Jira Service Desk add-on is installed on the same Jira instance.

New in this release:

• Fixed an issue that made it impossible to remove AppLinks.

New in this release:

• Fixed broken remote system id custom field when the remote object's subject is empty.

New in this release:

• Removes the limitation of only 13 associated remote objects. Refer to the KB article. (Also affects other Connectors that use the Core Connector plugin).

New in this release:

• Fixes the time-zone problem when syncing "Created" and "Updated" fields.

New in this release:

• Fixed an error when creating issue via REST endpoint.

New in this release:

• Fixed the Clear Cache button on the Mapping Configurations page not functioning as designed.

New in this release:

• Syncing when editing issue components should now work properly.

• Fixed broken cache for remote field list when upgrading the connector

• Fixed missing Connector icon after creating or editing comments.

• Fixed a problem when providing multiple fix versions fields when creating an issue from a remote object if fix versions is a required field.

• Fixed an unhandled error being triggered when remote attachment tabs are not configured.
• Fixed duplicated attachments when syncing simultaneously.
• Fixed failure upon publishing email during comment synchronization.

• Fixed searching with JQL remoteObjects when there are no operators specified.
• Fixed comment duplication when username is changed

• Fixed a sync problem when moving an issue to a different project or issue type.
• Added an option to merge values of a remote object custom field into a single table.

• Fixed a comment sync problem during workflow transitions.

New in this release:

• Fixed invalid query construction when using the 'in' operator via JQL.
• Fixed Salesforce objects not syncing when only custom fields are updated while editing a Jira Issue.
• Now supports the '~' operator as an alias of the 'LIKE' operator in JQL.
• Fixed Due Date field synchronization problem between Jira and Salesforce.
• Fixed synchronization problem when updating some Jira issue fields.
• Fixed failure on Jira issue creation when field issue validation is enabled.
• Fixed unlink action error if the remote object type is not supported.
• Fixed error when user associate object type more than default limit length.

New in this release:

• Updated old logo with current ServiceRocket logo
• Added configuration for visibility of available association options (Pull, Push, Associate only)
• Fixed Endpoints breaking when creating and synchronizing from remote objects

• Fixed a compatibility issue with Jira 6.3-OD-07 regarding an INVALID_QUERY_FILTER_OPERATOR error when accessing an issue with Multi Remote Object Link field.
• Fixed missing field values when validating required fields is enabled during issue creation.
• Related to Connector for Salesforce and Jira: Support for cache expiry for Remote Object Link and Multi Remote Object Link custom fields in the Admin page and on the View Issue screen.
• Fix invalid Salesforce Object Query.

• Fixed broken case reference link in Jira issue screen when it has "[" and "]" in the summary of a case.
• Created an option to enable syncing of only public, only private or all comments.

- Fix unsorted Comments issue.

- Add an option to sync/not sync data with "Associate" screen.

Salesforce Connector
=================

2013-06-25, 5.3.1, 6.0
-------------------------------
- Fix timezone issue in date and time field value synchronization between Jira and Salesforce

Release 5.3.0 - April, 2013

This release comes with a few new features!

New Features

• Attachment synchronization from Salesforce to Jira (uni-directional)
• Salesforce comment timestamp and commenter name appended to Jira
• Support for Jira select-ist mapping
• Support for Jira multi-select-list mapping (for non required field)

Improvements

• Project structure refactoring 

New Features

• Provide fields for missing required values
• Fasten query by including fields mapped in the configuration 
• Add Toggle to restrict comments to be pushed across based on role/group level  of comment
• Group into a collapsible section the settings under the mappings page
• Associate Endpoint lists all Jira Issues
• Comment synchronization control from Salesforce to Jira

Bugs Fixed

• Salesforce Connector Issue - Malformed_Query due to select statement over 10,000 characters
• Remote Object Link breaks
• Creating Jira Issues from Salesforce Cases always assigns Issue to the first default component assignee, even though there is no component passed
• Setting default issue priority in Jira from the Salesforce-Jira connector
• SFJira License module - java.util.MissingResourceException: Can't find resource for bundle - when install an upgraded Connector license in an upgraded Jira license type instance
• Synchronize the empty value from Salesforce to Jira

Improvements

• Multiple notifications sent if create a Jira Issue from Salesforce
• Set default assignee from Components Lead if exists

Bug

• Link to download an evaluation license points to wrong URL
• Issue with mapping a custom date field in Jira
• Unable to open Remote Attachments from Jira

Improvement

• Use HttpClient request to stream attachments

A lot of new features backported for Jira 4 support! Multi-sync, attachments and some minor improvements. A lot of bug fixes as well, see below:

Jira Issues

Improvement

• [AN105-629] - Issue creation respect the Jira security level set
• [AN105-612] - Create method to check if plugin supports multi-sync
• [AN105-410] - Provide support for attachments
• [AN105-614] - Remove event firing during issue created, commented and updated from Remote System

Task

• [AN105-626] - Error after click "Export" on Cloud Connector Mapping screen

Improvement

• [AN105-625] - Sort project list on create endpoint servlet
• [AN105-612] - Create method to check if plugin supports multi-sync

Task

• [AN105-622] - Associate endpoint updates Jira Issues on 2nd associate
• [AN105-619] - Create a "Pull Update" end point for remote object update from external
• [AN105-617] - Support Tempo Account Custom Field for Mapping

Bug

• [AN105-553] - Bulk Operation ignores permission on Issue.
• [AN105-608] - Fix duplication of comments in remote system in synch
• [AN105-613] - Send email notification on Issue create and commented from Remote System

Release 5.2.0 — June, 2012

• Improvement
  • [AN105-410] - Provide support for attachments
  • [AN105-612] - Create method to check if plugin supports multi-sync 
• Bug [Jira connector Plugin 1.2.0]
  • [AN105-608] - Fix duplication of comments in remote system in synch
  • [AN105-613] - Send email notification on Issue create and commented from Remote System
• Improvement [Jira connector Plugin 1.2.0]
  • [AN105-410] - Provide support for attachments
  • [AN105-612] - Create method to check if plugin supports multi-sync
  • [AN105-614] - Remove event firing during issue created, commented and updated from Remote System

Salesforce Connector Plugin 5.1 Release Notes:

This release targets Jira 5 compatibility
 
System Requirements

• Jira 5
• Not compatible with Jira 4; For Jira 4 compatible version please use Salesforce Connector Plugin version 5.0.3 and below (5.0.X)
  
• Does support Active Objects 0.15 up to 0.18

New features

• New functionality to synchronize/associate mutliple Salesforce Objects to Jira Issues
• Improvement on Manage Application Links interface for associating multiple Salesforce Objects
• Comments synchronization between multiple Salesforce Objects and a Jira Issue
• Administration module to enable or disable automatic synchronization for Issues with multiple Salesforce Objects
• New functioanlity to link (reference) multiple Salesforce Objects to Jira Issues
• Required fields check when creating an issue from Salesforce
• Administration module to enable or disable checking of required fields checking on Issue creation from Salesforce

Fixes

• Fixed Error status 422 for fields containing chars while synch
• Fixed No E-mail notifications form Jira when update from SF
• Fixed Default Assignee not being assigned to Issue on Issue creation from Salesforce to Jira
• Fixed issue of unable to search Remote or Multiple Remote Object Link with 18 char ID in Issue Navigator
• Validated and fixed all remote ID lookup to pull and index ID18 format from SF

Salesforce Connector Plugin 5.0.3 Release Notes:
 
This release targets backwards compatibility of version 5.1.1
 
System Requirements

• Jira 4
• Not compatible with Jira 5; For Jira 5 compatible version please use Salesforce Connector Plugin version 5.1 and above
• Does support Active Objects 0.15 up to 0.18

New features

• New functionality to synchronize/associate mutliple Salesforce Objects to Jira Issues
• Improvement on Manage Application Links interface for associating multiple Salesforce Objects
• Comments synchronization between multiple Salesforce Objects and a Jira Issue
• Administration module to enable or disable automatic synchronization for Issues with multiple Salesforce Objects
• New functioanlity to link (reference) multiple Salesforce Objects to Jira Issues
• Required fields check when creating an issue from Salesforce
• Administration module to enable or disable checking of required fields checking on Issue creation from Salesforce

Fixes

• Fixed Error status 422 for fields containing chars while synch
• Fixed No E-mail notifications form Jira when update from SF
• Fixed Default Assignee not being assigned to Issue on Issue creation from Salesforce to Jira
• Fixed issue of unable to search Remote or Multiple Remote Object Link with 18 char ID in Issue Navigator
• Validated and fixed all remote ID lookup to pull and index ID18 format from SF

Salesforce Connector Plugin 5.1 Release Notes:

This release targets Jira 5 compatibility

System Requirements:

• Jira 5 (rc) and above
• Not compatible with Jira 4.x.x; for Jira 4.x.x compatible version please use Salesforce Connector Plugin version 5.0.x
• Requires Active object version 0.19 and above; bundled in Jira 5 and above

• Make use of Remote Issue Link feature in Jira 5
• Add some way to display additional information from related entities
• Add support for "boolean" fields in Salesforce.com queries
• Update Case lookup to work with "subject" and "number"
• Improve "Manage Application Link" to use auto-complete interface
• Add limit on auto-complete searches
• Improve JQL function to handle complex queries. 

Fixes:

• Fixed security issue
• Fixed icon disappearing problem
• Fixed CSS confict issue
• Fixed mapping of "Unresolved" state when reopen an issue