Server/Datacenter Version 4.0

Version 4.16 for DC

• Resolved an issue where incoming email attachments stored in the Attachment object were not displaying correctly in the Emails tab.

• Added a configuration option to enable or disable the default value checkbox as editable or non-editable on the bulk creation screen.

Version 4.15 for DC

• Bulk Case Creation of Salesforce Cases: Added an option to create multiple Salesforce Case records simultaneously by uploading a CSV file. Users can map CSV columns to Salesforce Case fields and validate the data before submission, enabling faster case intake and reducing manual effort.

• Resolved an issue where the picklist on the authentication screen did not function as expected when ScriptRunner was installed.

• Minor bug fixes.

Version 4.14 for DC

• Minor bug fixes

Version 4.13 for DC

• Fixed an issue where issue types were not appearing in the dropdown for the restrict issue type feature.

Version 4.12 for DC

• Made the Jira plugin compatible with Jira version 10.

• Auto-Creation of Salesforce Records: Added an option to auto-create Salesforce records based on mapping configuration rules using values from Text Field, Text Area, Checkboxes, Single Select, or Multi-Select Jira fields.

• Enhanced Button Visibility Control: Provided an option to hide the "Create Salesforce Record" button on the Issue screen by restricting it for specific issue types.

• Customizable Field Layout: Added the ability to define the field order and column size on the Salesforce record creation page.

Version 4.11

• Made the plugin compatible with Jira version v9.17.5.

• Updated the correct reference document links.

• Minor UI/UX Fixes.

• Fixed a Bug where the Create screen displayed the error message "Something went wrong. Please try again or contact Sinergify." in the Potential Result section when Number, Checkbox, or Percentage fields are enabled.

• Fixed a bug in the Salesforce Settings screen where an orange bar was displayed at the top, and no saved data was shown after changes made on the Salesforce side, such as the removal or addition of issue types.

• Fixed a bug where the "Error! Something went wrong. Please try again or contact Sinergify" alert was displayed when the Case Description field was mapped with the Jira Description field, and the Jira description contained new lines.

• Resolved an issue where the Create button was not visible in certain scenarios, requiring a page refresh.

• Fixed one scenario with helptext overflowing even when the pointer is away.

• Fixed "Access is denied" Authentication issue.

• Fixed an issue where the Event Configuration screen was not working properly for previous Jira Data Center release v4.10.

Version 4.10

• Made the Jira plugin compatible with the latest Jira Data Center version.

• Minor UI Changes.

Version 4.9

• View Salesforce emails within the Jira plugin along with the option to download attachments, view inline images, and sort by email direction (inbound, outbound, or both).

• Email tab is configurable and can be toggled off from Configuration.

• The Salesforce fields can have a custom label.

• Help text can be added for Salesforce fields on the front end.

• Handled the scenario where checkbox fields were showing as required on the Jira side.

• 'Create Salesforce Record' screen now renders picklist options based on specific Salesforce record type instead of all record types.

Version 4.6.1

• Ability to view the potential results when Creating Salesforce records.

Version 4.6

• Datacentre compatible.

• Added the toggle to control the allowed projects and Issue types on the Configuration and Event configuration screen.

Version 4.5.2

• Minor Fixes.

Version 4.5.1

• Prioritize the display order of fields on the Jira Issue panel and the Salesforce record detail page.

Version 4.5

• Minor Bug Fixes.

Version 4.4

• Set the default values when creating Salesforce records.

Version 4.3

• Removed the deprecated API and added the create metadata API on the create Salesforce Record screen.

Version 4.2

• Minor Bug fixes on the configuration screen.

• Code optimization on the detail screen.

Version 4.1

• Minor Bug fixes.

Version 4.0

Functionality level changes

1. Create Salesforce object records from Jira.

   Once the Admin has configured the Salesforce object fields and Jira project fields with respect to their field types then End users will be able to create a ticket.

   

   

2. The Feed Signature feature is introduced to display the identity of the Jira user who has posted the feed.

   

3. Option to Redirect to a specific Salesforce case from Jira itself.

   

Admin level Changes

1. Enhanced authentication screen:

   1. Option to Enable or Disable the plugin (Ability to manage the firing of events).

   2. Jira Admin will be able to see the Integration User.

   3. Instance Number and Instance Name will be visible on the Authentication Screen itself.

2. Event Configuration screen refinements

   1. Events will be fired with respect to the projects and their issue types.

   2. To display the Salesforce Configuration in Jira, simply click on the sync button.If there are existing projects in Salesforce, this action will lead to the removal of all current configuration.

   3. Events will be fired for work logs.

      Note: Salesforce has certain API limits when integrating with other platforms, and it is necessary to ensure that the API requests meet these limits imposed by Salesforce. To address this issue and enhance security, the Project and issue types are added to optimize the API usage.

      

3. This option will help Admin to see in what all projects and issuetypes are Mapped.

   

   

4. New screen added “Salesforce settings“ which is used to map Salesforce Object fields with Jira project fields to prepopulate the field values on Create Salesforce Record Screen.

   1. Set default values for Case and Lead Assignment Rules which can be modified during record creation.

   2. Option to map salesforce  labels of the selected project fields in Required fields.

   3. Option to map additional Jira fields available in a selected Jira project and also have the option to mark the fields mandatory/required by checking the ‘Required’ box on the fields. The marked fields would require a value while creating a record from Jira.

   4. Option to decide the mapping of picklist values which is applicable only for picklist type fields.