Salesforce Integration Plugin (Jira 7 & earlier)

Version history

• CollapsedExpanded6.6.10-56046Jira Server 7.0.0 - 7.13.182023-09-27Minor bug fixes and improvements

  Version 6.6.10-56046 • Released 2023-09-27 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Minor fixes and improvements

  

• CollapsedExpanded6.6.9-55975Jira Server 7.0.0 - 7.13.182020-12-16Bug fixes and Improvements

  Version 6.6.9-55975 • Released 2020-12-16 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.6.8-55928Jira Server 7.0.0 - 7.13.182020-09-23Fixes and Improvements

  Version 6.6.8-55928 • Released 2020-09-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.6.7-55869Jira Server 7.0.0 - 7.13.182020-07-29Bug fixes and improvements

  Version 6.6.7-55869 • Released 2020-07-29 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.6.6-55836Jira Server 7.0.0 - 7.13.182020-05-20Bug fixes and improvements

  Version 6.6.6-55836 • Released 2020-05-20 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.6.5-55814Jira Server 7.0.0 - 7.13.182020-04-30Bug fixes and improvements

  Version 6.6.5-55814 • Released 2020-04-30 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed

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

  

• CollapsedExpanded6.6.4-55807Jira Server 7.0.0 - 7.13.182020-04-28Bug fixes and improvements

  Version 6.6.4-55807 • Released 2020-04-28 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed

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

  

• CollapsedExpanded6.6.3-55800Jira Server 7.0.0 - 7.13.182020-04-16Bug fixes and improvements

  Version 6.6.3-55800 • Released 2020-04-16 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.6.2-55740Jira Server 7.0.0 - 7.13.182020-01-30Bug fixes and improvements

  Version 6.6.2-55740 • Released 2020-01-30 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.6.1-55692Jira Server 7.0.0 - 7.13.182019-11-26Bug fixes and improvements

  Version 6.6.1-55692 • Released 2019-11-26 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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"

  

• CollapsedExpanded6.6.0-55649Jira Server 7.0.0 - 7.13.182019-09-24New UI on issue screens

  Version 6.6.0-55649 • Released 2019-09-24 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.5.8-55578Jira Server 7.0.0 - 7.13.182019-07-04Bug fixes and improvements

  Version 6.5.8-55578 • Released 2019-07-04 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed

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

  

• CollapsedExpanded6.5.5-55556Jira Server 7.0.0 - 7.13.182019-06-17Bug fixes and improvements

  Version 6.5.5-55556 • Released 2019-06-17 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.5.4-55515Jira Server 7.0.0 - 7.13.182019-05-01Bug fixes and improvements

  Version 6.5.4-55515 • Released 2019-05-01 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.5.3-55501Jira Server 7.0.0 - 7.13.182019-04-04Bug fixes and improvements

  Version 6.5.3-55501 • Released 2019-04-04 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.5.2-55471Jira Server 7.0.0 - 7.13.182019-03-13Minor bug fixes and improvements

  Version 6.5.2-55471 • Released 2019-03-13 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.5.1-55423Jira Server 7.0.0 - 7.13.182019-01-16Bug fixes and improvements

  Version 6.5.1-55423 • Released 2019-01-16 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.5-55406Jira Server 7.0.0 - 7.13.182018-11-29Bug fixes and improvements

  Version 6.5-55406 • Released 2018-11-29 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.12-55371Jira Server 7.0.0 - 7.12.32018-10-24Minor bug fixes and improvements

  Version 6.4.12-55371 • Released 2018-10-24 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.11-55350Jira Server 7.0.0 - 7.12.32018-10-04Minor bug fixes and improvements

  Version 6.4.11-55350 • Released 2018-10-04 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.10-55320Jira Server 7.0.0 - 7.12.32018-08-09Minor bug fixes and improvements

  Version 6.4.10-55320 • Released 2018-08-09 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.9-55305Jira Server 7.0.0 - 7.11.22018-08-02Bug fixes and improvements

  Version 6.4.9-55305 • Released 2018-08-02 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.8-55268Jira Server 7.0.0 - 7.11.22018-06-08Minor bug fixes and improvements

  Version 6.4.8-55268 • Released 2018-06-08 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.7-55223Jira Server 7.0.0 - 7.9.22018-05-09Minor bug fixes and improvements

  Version 6.4.7-55223 • Released 2018-05-09 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.6-55205Jira Server 7.0.0 - 7.9.22018-04-07Bug fixes and improvements

  Version 6.4.6-55205 • Released 2018-04-07 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed

  • Invalid 'crmtoken' error from plugin's servlets

  Added

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

  

• CollapsedExpanded6.4.4-55162Jira Server 7.0.0 - 7.8.42018-02-28Minor bug fixes and improvements

  Version 6.4.4-55162 • Released 2018-02-28 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.3-55156Jira Server 7.0.0 - 7.8.42018-02-23Minor bug fixes and improvements

  Version 6.4.3-55156 • Released 2018-02-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.2-55149Jira Server 7.0.0 - 7.8.42018-02-20Minor bug fixes and improvements

  Version 6.4.2-55149 • Released 2018-02-20 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4.1-55123Jira Server 7.0.0 - 7.7.42018-01-30Minor bug fixes and improvements

  Version 6.4.1-55123 • Released 2018-01-30 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.4-55090Jira Server 7.0.0 - 7.7.42018-01-12Support using multiple JIRA fields to link to the same CRM object

  Version 6.4-55090 • Released 2018-01-12 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  • 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

  

• CollapsedExpanded6.3.5-55026Jira Server 7.0.0 - 7.6.172017-09-29Bug fix

  Version 6.3.5-55026 • Released 2017-09-29 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed

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

  

• CollapsedExpanded6.3.4-55018Jira Server 7.0.0 - 7.5.42017-09-28Bug fixes and improvements

  Version 6.3.4-55018 • Released 2017-09-28 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.3.3-54951Jira Server 7.0.0 - 7.5.42017-07-27Bug fixes and improvements

  Version 6.3.3-54951 • Released 2017-07-27 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.3.2-54945Jira Server 7.0.0 - 7.4.62017-07-26Minor fixes and improvements

  Version 6.3.2-54945 • Released 2017-07-26 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.3.1-54916Jira Server 7.0.0 - 7.3.92017-06-13Now supports Microsoft Dynamics CRM Cloud

  Version 6.3.1-54916 • Released 2017-06-13 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.2.10-54857Jira Server 7.0.0 - 7.3.92017-04-20Minor fixes and improvements

  Version 6.2.10-54857 • Released 2017-04-20 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.0.11-54889Jira Server 6.3 - 6.4.142017-05-19Bug fixes and improvements

  Version 6.0.11-54889 • Released 2017-05-19 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed

  • Java NullPointerException when coping CRM comments to Jira

  Added

  • Warning when Epic Link field cannot be set from CRM

  

• CollapsedExpanded6.0.10-54838Jira Server 6.3 - 6.4.142017-04-20Minor fixes and improvements

  Version 6.0.10-54838 • Released 2017-04-20 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  • 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

  

• CollapsedExpanded6.2.9-54813Jira Server 7.0.0 - 7.3.92017-03-29Minor fixes and improvements

  Version 6.2.9-54813 • Released 2017-03-29 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed

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

  

• CollapsedExpanded6.2.8-54809Jira Server 7.0.0 - 7.3.92017-03-16Minor fixes and improvements

  Version 6.2.8-54809 • Released 2017-03-16 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.2.7-54754Jira Server 7.0.0 - 7.3.92017-02-07Bug fix to data caching

  Version 6.2.7-54754 • Released 2017-02-07 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed

  • Plugin's data cache not being used

  

• CollapsedExpanded6.2.6-54749Jira Server 7.0.0 - 7.3.92017-01-30Bug fixes and improvements

  Version 6.2.6-54749 • Released 2017-01-30 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.2.5-54707Jira Server 7.0.0 - 7.3.92016-11-08Minor fixes and improvements

  Version 6.2.5-54707 • Released 2016-11-08 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.0.9-54703Jira Server 6.3 - 6.4.142016-11-08Minor fixes and improvements

  Version 6.0.9-54703 • Released 2016-11-08 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  • 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

  

• CollapsedExpanded6.2.4-54669Jira Server 7.0.0 - 7.2.152016-09-19Bug fixes

  Version 6.2.4-54669 • Released 2016-09-19 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  • Some Salesforce field types not being copied to Jira

  

• CollapsedExpanded6.2.3-54665Jira Server 7.0.0 - 7.2.152016-09-15Bug fixes and improvements

  Version 6.2.3-54665 • Released 2016-09-15 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.2.2-54654Jira Server 7.0.0 - 7.2.152016-08-27Minor fixes

  Version 6.2.2-54654 • Released 2016-08-27 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.2.1-54643Jira Server 7.0.0 - 7.2.152016-08-18Minor fixes and improvements

  Version 6.2.1-54643 • Released 2016-08-18 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.2-54627Jira Server 7.0.0 - 7.1.102016-08-10Project specific field mappings

  Version 6.2-54627 • Released 2016-08-10 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.0.8-54629Jira Server 6.3 - 6.4.142016-08-11Minor fixes and improvements

  Version 6.0.8-54629 • Released 2016-08-11 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.1.4-54540Jira Server 7.0.0 - 7.1.102016-06-24Bug fixes and improvements

  Version 6.1.4-54540 • Released 2016-06-24 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.0.7-54537Jira Server 6.3 - 6.4.142016-06-24Bug fixes and improvements

  Version 6.0.7-54537 • Released 2016-06-24 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.6.8-54474Jira Server 5.0 - 6.2.72017-01-30Bug fixes and improvements

  Version 4.6.8-54474 • Released 2017-01-30 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

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

  

• CollapsedExpanded6.1.3-54427Jira Server 7.0.0 - 7.1.102016-04-01Bug fixes and improvements

  Version 6.1.3-54427 • Released 2016-04-01 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.0.6-54430Jira Server 6.3 - 6.4.142016-04-01Bug fixes and improvements

  Version 6.0.6-54430 • Released 2016-04-01 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.1.2-54224Jira Server 7.0.0 - 7.1.102016-02-02Minor fixes & improvements

  Version 6.1.2-54224 • Released 2016-02-02 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.0.5-54223Jira Server 6.3 - 6.4.142016-02-02Minor fixes & improvements

  Version 6.0.5-54223 • Released 2016-02-02 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.1.1-53959Jira Server 7.0.0 - 7.0.112015-12-02Minor fixes & improvements

  Version 6.1.1-53959 • Released 2015-12-02 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.0.4-53942Jira Server 6.3 - 6.4.142015-12-02Minor fixes & improvements

  Version 6.0.4-53942 • Released 2015-12-02 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial - no charge

  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

  

• CollapsedExpanded6.1-53638Jira Server 7.0.0 - 7.0.112015-10-14Version for Jira 7.0

  Version 6.1-53638 • Released 2015-10-14 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  • Support Jira 7.0

  

• CollapsedExpanded6.0.3-53552Jira Server 6.3 - 6.4.142015-09-25Minor fixes & improvements

  Version 6.0.3-53552 • Released 2015-09-25 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.6.7-53545Jira Server 5.0 - 6.2.72015-09-25Minor fixes & improvements

  Version 4.6.7-53545 • Released 2015-09-25 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded6.0.2-53331Jira Server 6.3 - 6.4.142015-08-24Support for multiple CRM systems simultaneously

  Version 6.0.2-53331 • Released 2015-08-24 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.6.6-53249Jira Server 5.0 - 6.2.72015-08-18Minor fixes & improvements

  Version 4.6.6-53249 • Released 2015-08-18 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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)

  

• CollapsedExpanded5.1.5-52974Jira Server 6.3 - 6.4.142015-06-23Minor fixes & improvements

  Version 5.1.5-52974 • Released 2015-06-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.6.5-52979Jira Server 5.0 - 6.2.72015-06-23Fixed Java Class Not Found exception for older versions of Jira

  Version 4.6.5-52979 • Released 2015-06-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  No release notes.

  

• CollapsedExpanded5.1.4-52717Jira Server 6.3 - 6.4.142015-05-19Minor fixes & improvements

  Version 5.1.4-52717 • Released 2015-05-19 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded5.1.3-52382Jira Server 6.3 - 6.4.142015-04-06Minor fixes & improvements

  Version 5.1.3-52382 • Released 2015-04-06 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.6.4-52373Jira Server 5.0 - 6.2.72015-04-06Minor fixes & improvements

  Version 4.6.4-52373 • Released 2015-04-06 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded5.1.2-52198Jira Server 6.3 - 6.4.142015-03-03Minor fixes & improvements

  Version 5.1.2-52198 • Released 2015-03-03 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.6.3-52023Jira Server 5.0 - 6.2.72015-03-03Minor fixes & improvements

  Version 4.6.3-52023 • Released 2015-03-03 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded5.1.1-51745Jira Server 6.3 - 6.3.152015-01-23Minor fixes & improvements

  Version 5.1.1-51745 • Released 2015-01-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.6.2-51775Jira Server 5.0 - 6.2.72015-01-23Minor fixes & improvements

  Version 4.6.2-51775 • Released 2015-01-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded5.1-51470Jira Server 6.3 - 6.3.152014-12-31Support for Microsoft Dynamics CRM plus some new features and bug fixes

  Version 5.1-51470 • Released 2014-12-31 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.6.1-51466Jira Server 5.0 - 6.2.72014-12-31Minor fixes

  Version 4.6.1-51466 • Released 2014-12-31 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed in this release

  • Cron job turns off when settings are updated

  

• CollapsedExpanded4.6-51390Jira Server 5.0 - 6.2.72014-12-18Support for Microsoft Dynamics CRM plus some new features and bug fixes

  Version 4.6-51390 • Released 2014-12-18 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded5.0.3-50834Jira Server 6.3 - 6.3.152014-11-19Minor fixes & improvements

  Version 5.0.3-50834 • Released 2014-11-19 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded5.0.2-50242Jira Server 6.3 - 6.3.152014-09-30Minor fixes & improvements

  Version 5.0.2-50242 • Released 2014-09-30 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.5.8-50050Jira Server 5.0 - 6.2.72014-09-18Minor fixes & improvements

  Version 4.5.8-50050 • Released 2014-09-18 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded5.0.1-49809Jira Server 6.3 - 6.3.152014-09-02Minor fixes & improvements

  Version 5.0.1-49809 • Released 2014-09-02 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.5.7-49757Jira Server 5.0 - 6.3.152014-08-27Minor fixes & improvements

  Version 4.5.7-49757 • Released 2014-08-27 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded5.0-49580Jira Server 6.3 - 6.3.152014-08-19Added support for Jira Data Center

  Version 5.0-49580 • Released 2014-08-19 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.5.4-48558Jira Server 5.0 - 6.3.152014-06-05Minor fixes & improvements

  Version 4.5.4-48558 • Released 2014-06-05 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.5.3-48270Jira Server 5.0 - 6.3.152014-04-30Minor fixes & improvements

  Version 4.5.3-48270 • Released 2014-04-30 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.5.2-47891Jira Server 5.0 - 6.2.72014-03-25Minor fixes & improvements

  Version 4.5.2-47891 • Released 2014-03-25 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded4.5.1-47492Jira Server 5.0 - 6.2.72014-02-20The plugin's setup dialogs should not display a nav bar in Jira 6

  Version 4.5.1-47492 • Released 2014-02-20 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Fixed in this release

  
  

  Nav bar should not be displayed when editing field mappings in Jira 6.x

  
  
  

  

• CollapsedExpanded4.5-47430Jira Server 5.0 - 6.1.92014-02-11Improved handling of edited comments and issue linking/unlinking

  Version 4.5-47430 • Released 2014-02-11 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  New in this release

  
  

  Jira issues can now be unlinked by CRM users

  Comments editing or deleted in Jira are edited or deleted in CRM

  
  
  

  

• CollapsedExpanded4.4.2-46836Jira Server 5.0 - 6.1.92013-12-09Minor improvements & bug fixes

  Version 4.4.2-46836 • Released 2013-12-09 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  New in this release

  
  

  * Add support for copying a Jira issue's project category to CRM

  * Ability to open a new tab/window with the Jira issue after creating it from CRM

  * Support 15 digit Salesforce IDs when using Jira's REST API

  * Better control over the formatting of comment headers

  * Add option to always create a new CRM Case when creating a new Jira issue

  * Add option to specify how to update Jira when an issue is linked to multiple CRM records

  
  
  

  Fixed in this release

  
  

  * NullPointerException occurring in Jira 6.1

  
  
  

  

• CollapsedExpanded4.4.1-45710Jira Server 5.0 - 6.1.92013-09-23Minor bug fixes

  Version 4.4.1-45710 • Released 2013-09-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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

  

  Read the full release notes »
  

• CollapsedExpanded4.4-45582Jira Server 5.0 - 6.0.82013-09-09Ability to manually copy individual comments from Jira to CRM and other improvements/fixes

  Version 4.4-45582 • Released 2013-09-09 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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
  

  
  

  

  Read the full release notes »
  

• CollapsedExpanded4.3.5-44907Jira Server 5.0 - 6.0.82013-07-23Minor improvements & bug fixes

  Version 4.3.5-44907 • Released 2013-07-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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"
  
  

  

  Read the full release notes »
  

• CollapsedExpanded4.3.4-44081Jira Server 5.0 - 6.0.82013-06-10Minor bug fixes

  Version 4.3.4-44081 • Released 2013-06-10 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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
  
  

  

  Read the full release notes »
  

• CollapsedExpanded4.3.3-43870Jira Server 5.0 - 6.0.82013-05-30Performance & minor bug fixes

  Version 4.3.3-43870 • Released 2013-05-30 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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.
  
  

  

  Read the full release notes »
  

• CollapsedExpanded4.3.2-43692Jira Server 5.0 - 6.02013-05-23Suport for Jira 6.0

  Version 4.3.2-43692 • Released 2013-05-23 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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
  
  
  

  

  Read the full release notes »
  

• CollapsedExpanded4.3.1-43517Jira Server 5.0 - 5.2.112013-05-16Minor bug fix

  Version 4.3.1-43517 • Released 2013-05-16 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

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

  

  Read the full release notes »
  

• CollapsedExpanded4.2.5-41372Jira Server 5.0 - 5.2.112013-01-28Minor bug fixes & enhancements

  Version 4.2.5-41372 • Released 2013-01-28 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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
  
  

  

  Read the full release notes »
  

• CollapsedExpanded4.2.4-39804Jira Server 5.0 - 5.2.112012-09-25SQL error fix

  Version 4.2.4-39804 • Released 2012-09-25 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

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

  

  Read the full release notes »
  

• CollapsedExpanded4.2.3-39712Jira Server 5.0 - 5.1.82012-09-21Jira UI improvements; Bug fixes

  Version 4.2.3-39712 • Released 2012-09-21 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  ** 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

  

  Read the full release notes »
  

• CollapsedExpanded4.2.2-38757Jira Server 5.0 - 5.1.82012-07-18SugarCRM 6.4 support; Bug Fixes

  Version 4.2.2-38757 • Released 2012-07-18 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  ** 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

  

  Read the full release notes »
  

• CollapsedExpanded4.2.1-38121Jira Server 5.0 - 5.12012-06-11New Features / Bug Fixes

  Version 4.2.1-38121 • Released 2012-06-11 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  ** 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

  

• CollapsedExpanded4.1.5-38113Jira Server 4.4 - 4.4.52012-06-11Bug fixes

  Version 4.1.5-38113 • Released 2012-06-11 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  ** 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

  

  Read the full release notes »
  

• CollapsedExpanded4.1.4-37167Jira Server 4.4 - 4.4.52012-05-10JQL search support / Bug fixes

  Version 4.1.4-37167 • Released 2012-05-10 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  ** 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
  
  

  

  Read the full release notes »
  

• CollapsedExpanded3.3.6Jira Server 4.0 - 4.2.42012-04-11Minor bug fixes

  Version 3.3.6 • Released 2012-04-11 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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

  

• CollapsedExpanded4.0.2-36143Jira Server 4.3 - 4.3.42012-04-05Minor Bug Fixes

  Version 4.0.2-36143 • Released 2012-04-05 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  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
  
  
  

  

• CollapsedExpanded4.2-35064Jira Server 5.0 - 5.0.72012-02-23Jira 5.0 Version

  Version 4.2-35064 • Released 2012-02-23 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  ** 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.

  

• CollapsedExpanded4.1.3-34755Jira Server 4.4 - 4.4.52012-02-10Bug fixes and improvements

  Version 4.1.3-34755 • Released 2012-02-10 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  ** 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

  

• CollapsedExpanded4.1.2-32489Jira Server 4.4 - 4.4.52011-11-10Minor bug fixes and improvements

  Version 4.1.2-32489 • Released 2011-11-10 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  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

  

  Read the full release notes »
  

• CollapsedExpanded4.0.1-32372Jira Server 4.3 - 4.3.42011-11-07Now includes a free license key and utility toconvert from CustomWare'sSalesforce plugin

  Version 4.0.1-32372 • Released 2011-11-07 • Supported By Goldfinger Holdings, Inc. • Free • Commercial - no charge

  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

  

• CollapsedExpanded3.3.5Jira Server 4.0 - 4.2.42011-11-04Minor bug fixes and improvements

  Version 3.3.5 • Released 2011-11-04 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  ** 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

  

• CollapsedExpanded4.1.1-32184Jira Server 4.4 - 4.4.52011-10-27Now includes a free license key and support for Jira Studio

  Version 4.1.1-32184 • Released 2011-10-27 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  No release notes.

  

• CollapsedExpanded4.1-31479Jira Server 4.4 - 4.4.52011-09-27Jira 4.4 version

  Version 4.1-31479 • Released 2011-09-27 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  Support for Jira 4.4

  

• CollapsedExpanded4.0-31449Jira Server 4.3 - 4.3.42011-09-26Atlassian V2 plugin

  Version 4.0-31449 • Released 2011-09-26 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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

  

• CollapsedExpanded3.3.4Jira Server 4.0 - 4.3.42011-08-08Jira 4.3 version

  Version 3.3.4 • Released 2011-08-08 • Supported By Goldfinger Holdings, Inc. • Paid via Vendor • Commercial

  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