We’ve redesigned our logo for Elements Connect to reflect the maturity of our offering, while keeping our iconic visual system based on primary shapes that evokes the idea of elements you assemble together.

Key versions history:

2022/07/04 - UX configuration enhancements in Elements Connect global admin

2022/05/14 - Display data from nested attributes and objects in dependent connected items

2022/04/12 - Queries based on request type attributes, plus UX improvements & a security fix

2022/03/24 - Mirror fields can be moved to trash & minor bug fixes

2022/03/17 - Queries using issue type attributes are now possible

2022/03/03 - REST APIs datasources available for everyone

2022/02/15 - New authentication mode on REST API datasources: API Key

2022/02/10 - Dynamic queries based on current project

2022/01/31 - Basic authentication available for REST API Beta program

Migrating to Cloud? Help us help you: tell us about your current set up.

We’ve redesigned our logo for Elements Connect to reflect the maturity of our offering, while keeping our iconic visual system based on primary shapes that evokes the idea of elements you assemble together.

🚀 See Elements Connect in action on our public Demo Platform

Migrating to Cloud? Help us help you: tell us about your current set up.

We’ve redesigned our logo for Elements Connect to reflect the maturity of our offering, while keeping our iconic visual system based on primary shapes that evokes the idea of elements you assemble together.

🚀 See Elements Connect in action on our public Demo Platform

Migrating to Cloud? Help us help you: tell us about your current set up.

This version fixes 1 bug:

• CO-3934 Disappearing datasources in Elements Connect administration

🚀 See Elements Connect in action on our public Demo Platform

Migrating to Cloud? Help us help you: tell us about your current set up.

This version fixes 1 bug:

• CO-3934 Disappearing datasources in Elements Connect administration

🚀 See Elements Connect in action on our public Demo Platform

Migrating to Cloud? Help us help you: tell us about your current set up.

This version fixes 1 bug:

• CO-3924 SQL & JNDI DS - There shall be no "Connection timeout" when the "Timeout" option is not checked

🚀 See Elements Connect in action on our public Demo Platform

Migrating to Cloud? Help us help you: tell us about your current set up.

This version fixes 1 bug:

• CO-3924 SQL & JNDI DS - There shall be no "Connection timeout" when the "Timeout" option is not checked

🚀 See Elements Connect in action on our public Demo Platform

Migrating to Cloud? Help us help you: tell us about your current set up.

This version fixes 3 bugs:

• CO-3922 Elements Connect user field is emptied on the issue update
• CO-3923 Live fields values lost on edition when option contains leading or trailing space
• CO-3776 Connect fields with default value set are preselected in Bulk Edit

⚠️ You can’t upgrade directly from Elements Connect 5.x.

🚀 See Elements Connect in action on our public Demo Platform

Migrating to Cloud? Help us help you: tell us about your current set up.

This version fixes 3 bugs:

• CO-3922 Elements Connect user field is emptied on the issue update
• CO-3923 Live fields values lost on edition when option contains leading or trailing space
• CO-3776 Connect fields with default value set are preselected in Bulk Edit

⚠️ You can’t upgrade directly from Elements Connect 5.x.

🚀 See Elements Connect in action on our public Demo Platform

Migrating to Cloud? Help us help you: tell us about your current set up.

This version fixes 2 bugs:

• CO-3880 Datasources of the target instance are overwritten when using Configuration Manager for Jira

  CO-3809 Datasources duplication when using Configuration Manager for Jira

⚠️ You can’t upgrade directly from Elements Connect 5.x.

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3880 Datasources of the target instance are overwritten when using Configuration Manager for Jira

  CO-3809 Datasources duplication when using Configuration Manager for Jira

⚠️ You can’t upgrade directly from Elements Connect 5.x.

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3912 Snapshot fields values lost on edition when option contains leading or trailing space
• CO-3828 The Restore function doesn't check the Backup file authenticity

⚠️ You can’t upgrade directly from Elements Connect 5.x.

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3912 Snapshot fields values lost on edition when option contains leading or trailing space
• CO-3828 The Restore function doesn't check the Backup file authenticity

⚠️ You can’t upgrade directly from Elements Connect 5.x.

🚀 See Elements Connect in action on our public Demo Platform

This version updates server side libraries and fixes 2 bugs:

• CO-3894 - When display query ignores currentCustomfieldValue, empty fields have a value in a Jira CSV export
• CO-3802 - "Copy display value" and "Copy field key" post function shall trim Connect fields display value

⚠️ You can’t upgrade directly from Elements Connect 5.x.

🚀 See Elements Connect in action on our public Demo Platform

This version updates server side libraries and fixes 2 bugs:

• CO-3894 - When display query ignores currentCustomfieldValue, empty fields have a value in a Jira CSV export
• CO-3802 - "Copy display value" and "Copy field key" post function shall trim Connect fields display value

⚠️ You can’t upgrade directly from Elements Connect 5.x.

🚀 See Elements Connect in action on our public Demo Platform

Performance is critical for us, for that reason it is now possible to configure an optional timeout on LDAP and SQL datasources. Read the documentation to learn more about this feature.

This version also fixes 2 bugs:

• CO-3781 Label custom fields return a Velocity error when they are empty
• CO-3896 Since Jira 8.6, the Table editor is no longer properly displayed in a JSM portal

🚀 See Elements Connect in action on our public Demo Platform

Performance is critical for us, for that reason it is now possible to configure an optional timeout on LDAP and SQL datasources. Read the documentation to learn more about this feature.

This version also fixes 2 bugs:

• CO-3781 Label custom fields return a Velocity error when they are empty
• CO-3896 Since Jira 8.6, the Table editor is no longer properly displayed in a JSM portal

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 1 bug:

• CO-3909 - Snapshot DateTime fields with dependency are not holding values on create screen

If you're upgrading from Elements Connect v5, read this release note carefully!🚀 See Elements Connect in action on our public Demo Platform

This version fixes 1 bug:

• CO-3909 - Snapshot DateTime fields with dependency are not holding values on create screen

If you're upgrading from Elements Connect v5, read this release note carefully!🚀 See Elements Connect in action on our public Demo Platform

This version fixes two bugs:

• CO-3906 - Error when saving a Snapshot Date field from a JSM portal
• CO-3886 - Elements Connect logging is too verbose when an LDAP query has a syntax error

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes two bugs:

• CO-3906 - Error when saving a Snapshot Date field from a JSM portal
• CO-3886 - Elements Connect logging is too verbose when an LDAP query has a syntax error

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 1 bug:

• CO-3903 - Live User fields don't work anymore after upgrading Jira to version 8.21

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 1 bug:

• CO-3903 - Live User fields don't work anymore after upgrading Jira to version 8.21

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 1 bug:

• CO-3903 - Live User fields don't work anymore after upgrading Jira to version 8.21

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 1 bug:

• CO-3903 - Live User fields don't work anymore after upgrading Jira to version 8.21

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 3 bugs:

• CO-3844 - Since version 6.7.4, the Max Suggestions option works inconsistently when the Connect field depends on another field in the Create screen
• CO-3892 - Unable to set all Connect values via behaviour script when coming from large dataset
• CO-3898 - Move issue blocked by Elements Connect

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 3 bugs:

• CO-3844 - Since version 6.7.4, the Max Suggestions option works inconsistently when the Connect field depends on another field in the Create screen
• CO-3892 - Unable to set all Connect values via behaviour script when coming from large dataset
• CO-3898 - Move issue blocked by Elements Connect

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3893 - Can't select values located outside of the original result set in Snapshot fields
• CO-3810 - When the "Only display distinct values" option is enabled in the Search view, the ~ search may not return results if multiple options have the same display but different keys.

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3893 - Can't select values located outside of the original result set in Snapshot fields
• CO-3810 - When the "Only display distinct values" option is enabled in the Search view, the ~ search may not return results if multiple options have the same display but different keys.

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀See Elements Connect in action on our public Demo Platform

This version brings a long-awaited feature: it is now possible to set the values of Elements Connect fields with Behaviours! Read our documentation to learn more about this integration.

If you're upgrading from Elements Connect v5, read this release note carefully! See Elements Connect in action on our public Demo Platform.

Known Issues

• CO-3892 : An error prevents the correct setting of Elements Connect values when they are not part of the currently displayed options in the field
• CO-3817 - Behaviour is not functioning properly on Portal side

This version brings a long-awaited feature: it is now possible to set the values of Elements Connect fields with Behaviours! Read our documentation to learn more about this integration.

If you're upgrading from Elements Connect v5, read this release note carefully! See Elements Connect in action on our public Demo Platform.

Known Issues

• CO-3892 : An error prevents the correct setting of Elements Connect values when they are not part of the currently displayed options in the field
• CO-3817 - Behaviour is not functioning properly on Portal side

This version fixes 2 bugs:

• CO-3885 - Anonymous user is used as author when updating a Connect field through the "Set Elements Connect field value" action
• CO-3890 - Empty option list when editing a field from a Rich filter gadget if a field dependency is not on the edit screen

If you're upgrading from Elements Connect v5, read this release note carefully! See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3885 - Anonymous user is used as author when updating a Connect field through the "Set Elements Connect field value" action
• CO-3890 - Empty option list when editing a field from a Rich filter gadget if a field dependency is not on the edit screen

If you're upgrading from Elements Connect v5, read this release note carefully! See Elements Connect in action on our public Demo Platform

This version fixes 3 bugs:

• CO-3864 - /createmeta returns a "400 Bad Request" error when a Connect field query cannot be executed
• CO-3887 - The message "Please, type at least x characters" behaves like an option and can be selected, on multi value autocompletes
• CO-3884 - Error 500 on /createmeta when a not configured Live User field is on an Issue creation screen

If you're upgrading from Elements Connect v5, read this release note carefully! See Elements Connect in action on our public Demo Platform

This version fixes 3 bugs:

• CO-3864 - /createmeta returns a "400 Bad Request" error when a Connect field query cannot be executed
• CO-3887 - The message "Please, type at least x characters" behaves like an option and can be selected, on multi value autocompletes
• CO-3884 - Error 500 on /createmeta when a not configured Live User field is on an Issue creation screen

If you're upgrading from Elements Connect v5, read this release note carefully! See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3883 - LDAP queries broken when search scope is used
• CO-3803 - Since version 6.4.6, it's not possible to select a value in a User Picker field when moving a specific issue
• CO-3811 - Error 500 if a user selected in an Elements Connect User field has its username renamed

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3883 - LDAP queries broken when search scope is used
• CO-3803 - Since version 6.4.6, it's not possible to select a value in a User Picker field when moving a specific issue
• CO-3811 - Error 500 if a user selected in an Elements Connect User field has its username renamed

If you're upgrading from Elements Connect v5, read this release note carefully!

🚀 See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3839 - Live Fields are creating duplicate lines in the Lucene index
• CO-3843 - Limit the results returned by a LDAP query

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes 2 bugs:

• CO-3839 - Live Fields are creating duplicate lines in the Lucene index
• CO-3843 - Limit the results returned by a LDAP query

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes one bug :

CO-3875 - "401 error" on Jira REST API datasource when "Traffic distribution" is enabled

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes one bug :

CO-3875 - "401 error" on Jira REST API datasource when "Traffic distribution" is enabled

If you're upgrading from Elements Connect v5, read this release note carefully!

This version brings the maximum number of results that can be displayed in the Table editor to 1,000 per page.

If you're upgrading from Elements Connect v5, read this release note carefully!

This version brings the maximum number of results that can be displayed in the Table editor to 1,000 per page.

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes 5 bugs, mostly related to the autocomplete editor:

• CO-3859 - Since version 6.7.4, it's no longer possible to select identical displayed values
• CO-3842 - [Autocomplete] Selected value is centered-aligned while it should be top-aligned
• CO-3838 - Since version 6.7.4, the "Min characters" option prevents new values from being entered in Connect fields that are already populated
• CO-3867 - Autocomplete - Selecting a value will mark all values with the same display as selected
• CO-3837 - Read Timeout max value on URL datasource shall be 10 minutes

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes 5 bugs, mostly related to the autocomplete editor:

• CO-3859 - Since version 6.7.4, it's no longer possible to select identical displayed values
• CO-3842 - [Autocomplete] Selected value is centered-aligned while it should be top-aligned
• CO-3838 - Since version 6.7.4, the "Min characters" option prevents new values from being entered in Connect fields that are already populated
• CO-3867 - Autocomplete - Selecting a value will mark all values with the same display as selected
• CO-3837 - Read Timeout max value on URL datasource shall be 10 minutes

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes 5 bugs:

• CO-3620 - Issues not visible in the Issue navigator when visibility is restricted by a Connect field (Jira 8)
• CO-3845 - The type of Snapshot Text fields specified in the /createmeta response should be a string and not an array
• CO-3711 - Non admin users cannot use the Elements Connect REST API
• CO-3850 - Connect "Live text" fields should not be selectable for project permissions
• CO-3851 - Legacy Connect field should return fields options for /createmeta when option is selected

How to delegate select list options configuration to business users? Set it up in a dedicated Jira project and use Elements Connect to get data from Jira: Read the tutorial

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes 5 bugs:

• CO-3620 - Issues not visible in the Issue navigator when visibility is restricted by a Connect field (Jira 8)
• CO-3845 - The type of Snapshot Text fields specified in the /createmeta response should be a string and not an array
• CO-3711 - Non admin users cannot use the Elements Connect REST API
• CO-3850 - Connect "Live text" fields should not be selectable for project permissions
• CO-3851 - Legacy Connect field should return fields options for /createmeta when option is selected

How to delegate select list options configuration to business users? Set it up in a dedicated Jira project and use Elements Connect to get data from Jira: Read the tutorial

If you're upgrading from Elements Connect v5, read this release note carefully!

This version improves the compatibility with the /createmeta Jira endpoint. From now on, the /createmeta endpoint will return all field options even if "Max suggestions" parameter is set on the field. It makes more sense as the autocomplete feature might not be available on all external services using this API. See CO-3821 and have a look at the documentation for more details.

We have also fixed 2 bugs:

• CO-3813 - Getting "403 Forbidden" when connecting to some URL datasources when the "User-Agent" header is not configured
• CO-3653 - Configuration tester is broken in the display tab if a field name contains ' or " or if it's translated

If you're upgrading from Elements Connect v5, read this release note carefully!

This version improves the compatibility with the /createmeta Jira endpoint. From now on, the /createmeta endpoint will return all field options even if "Max suggestions" parameter is set on the field. It makes more sense as the autocomplete feature might not be available on all external services using this API. See CO-3821 and have a look at the documentation for more details.

We have also fixed 2 bugs:

• CO-3813 - Getting "403 Forbidden" when connecting to some URL datasources when the "User-Agent" header is not configured
• CO-3653 - Configuration tester is broken in the display tab if a field name contains ' or " or if it's translated

If you're upgrading from Elements Connect v5, read this release note carefully!

This new version of Elements Connect brings a long-awaited feature: it is now possible to get Elements Connect fields rendered value using Jira REST API (/issue and /search endpoints). As a consequence, third-party software like EazyBI and TestRails are now able to display Elements Connect field values.See CO-2662 and have a look at the documentation for more details.

If you're upgrading from Elements Connect v5, read this release note carefully!

💡 See Elements Connect in action on our public Demo Platform

This new version of Elements Connect brings a long-awaited feature: it is now possible to get Elements Connect fields rendered value using Jira REST API (/issue and /search endpoints). As a consequence, third-party software like EazyBI and TestRails are now able to display Elements Connect field values.See CO-2662 and have a look at the documentation for more details.

If you're upgrading from Elements Connect v5, read this release note carefully!

💡 See Elements Connect in action on our public Demo Platform

This version improves the performances of the autocomplete editor and fixes 3 bugs:

• CO-3701 - Microsoft Surface / Chrome - Unable to select Elements Connect field, Autocomplete Editor
• CO-3764 - Ipad - Unable to select Elements Connect field, Autocomplete Editor
• CO-3769 - Vertical blue stripes when editing Elements Connect field in Chrome

We've also updated the Javascript library used by Elements Connect.

If you're upgrading from Elements Connect v5, read this release note carefully!

💡See Elements Connect in action on our public Demo Platform

This version improves the performances of the autocomplete editor and fixes 3 bugs:

• CO-3701 - Microsoft Surface / Chrome - Unable to select Elements Connect field, Autocomplete Editor
• CO-3764 - Ipad - Unable to select Elements Connect field, Autocomplete Editor
• CO-3769 - Vertical blue stripes when editing Elements Connect field in Chrome

We've also updated the Javascript library used by Elements Connect.

If you're upgrading from Elements Connect v5, read this release note carefully!

See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3827 - Missing field configuration after importing a snapshot with Configuration Manager
• CO-3771 - Sorting a Snapshot field doesn't work properly

If you're upgrading from Elements Connect v5, read this release note carefully!

See Elements Connect in action on our public Demo Platform

This version fixes 2 bugs:

• CO-3827 - Missing field configuration after importing a snapshot with Configuration Manager
• CO-3771 - Sorting a Snapshot field doesn't work properly

If you're upgrading from Elements Connect v5, read this release note carefully!

See Elements Connect in action on our public Demo Platform

• CO-3824 - When creating a sub-task, Elements Connect fields editor might not appear
• CO-3816 - Elements Connect field using the Jira REST Datasource gets 401 errors

If you're upgrading from Elements Connect v5, read this release note carefully!

💡 See Elements Connect in action on our public Demo Platform

• CO-3824 - When creating a sub-task, Elements Connect fields editor might not appear
• CO-3816 - Elements Connect field using the Jira REST Datasource gets 401 errors

If you're upgrading from Elements Connect v5, read this release note carefully!

💡 See Elements Connect in action on our public Demo Platform

This version fixes one bug related to the Live User field:

CO-3773 - The User field provided by Elements Connect doesn't work in JQL queries which are generated from "Issue Statistics" gadget

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes one bug related to the Live User field:

CO-3773 - The User field provided by Elements Connect doesn't work in JQL queries which are generated from "Issue Statistics" gadget

If you're upgrading from Elements Connect v5, read this release note carefully!

Timeouts on URL datasources

We have added two timeout on URL datasources: connect & read timeouts.

Our goal is to reduce the impact on issue loading and field edition when a datasource is not reachable or slow to respond.

Read more about this new feature in the product documentation.See also CO-3761

/createmeta compliance

Elements Connect is now compliant with the /createmeta endpoint of Jira REST API.

It is now possible to set the value of Elements Connect fields while creating issues from external tools like TestRail.

Read this page (Jira REST API) and this page (TestRail) in our documentation to learn more.

Bug fixes

We have fixed a bug related to OAuth authentication on URL datasources (see CO-3787 and CO-3807).

It's now possible to connect fields to more REST APIs like Microsoft Azure or ApiGee.

Upgrading from Elements Connect 5

If you're upgrading from Elements Connect v5, read this release note carefully!

Timeouts on URL datasources

We have added two timeout on URL datasources: connect & read timeouts.

Our goal is to reduce the impact on issue loading and field edition when a datasource is not reachable or slow to respond.

Read more about this new feature in the product documentation.See also CO-3761

/createmeta compliance

Elements Connect is now compliant with the /createmeta endpoint of Jira REST API.

It is now possible to set the value of Elements Connect fields while creating issues from external tools like TestRail.

Read this page (Jira REST API) and this page (TestRail) in our documentation to learn more.

Bug fixes

We have fixed a bug related to OAuth authentication on URL datasources (see CO-3787 and CO-3807).

It's now possible to connect fields to more REST APIs like Microsoft Azure or ApiGee.

Upgrading from Elements Connect 5

If you're upgrading from Elements Connect v5, read this release note carefully!

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes the below bug:

CO-3700 - Error "Forbidden (403)" on contextualized fields in search for non-admin users

If you're upgrading from Elements Connect v5, read this release note carefully!

This version fixes the below bug:

CO-3700 - Error "Forbidden (403)" on contextualized fields in search for non-admin users

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3801 - Deleting a Connect field from Jira prevents the generation of dump file
• CO-3791 - Automation - ScriptRunner 6.16+ breaks the "Action" page if Elements Connect is installed

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3801 - Deleting a Connect field from Jira prevents the generation of dump file
• CO-3791 - Automation - ScriptRunner 6.16+ breaks the "Action" page if Elements Connect is installed

If you're upgrading from Elements Connect v5, read this release note carefully!

We've added more information to the Elements Connect support dump, like dependency usage or field name in order to improve the quality of our support.The Support dump is an anonymized version of your Elements connect configuration that may be asked by our support team in order to understand how the app is configured on your instance. It does not contain any sensitive data.

If you're upgrading from Elements Connect v5, read this release note carefully!

We've added more information to the Elements Connect support dump, like dependency usage or field name in order to improve the quality of our support. The Support dump is an anonymized version of your Elements connect configuration that may be asked by our support team in order to understand how the app is configured on your instance. It does not contain any sensitive data.

If you're upgrading from Elements Connect v5, read this release note carefully!

Configuration Manager is an app developed by Botron that automates the transfer of Jira configuration and data between different Jira servers. This encompasses Jira Core, Jira Software, Jira Service Management and 3rd party apps.

We are happy to announce that Elements Connect is now compatible with Configuration Manager!

If you're upgrading from Elements Connect v5, read this release note carefully!

Configuration Manager is an app developed by Botron that automates the transfer of Jira configuration and data between different Jira servers. This encompasses Jira Core, Jira Software, Jira Service Management and 3rd party apps.

We are happy to announce that Elements Connect is now compatible with Configuration Manager!

If you're upgrading from Elements Connect v5, read this release note carefully!

CO-3774 - Fields with the same query and datasource do not share cache when they are edited simultaneously

If you're upgrading from Elements Connect v5, read this release note carefully!

CO-3774 - Fields with the same query and datasource do not share cache when they are edited simultaneously

If you're upgrading from Elements Connect v5, read this release note carefully!

• To help new users of Elements Connect get off a good start, we have embedded the Elements Connect getting started guide in the app. This comprehensive guide helps admins set-up their first connected fields, from connecting to a datasource to retrieving external data and customizing how it's displayed in custom fields.
• CO-3780 - Cache shall be active when configuring a new field

If you're upgrading from Elements Connect v5, read this release note carefully!

• To help new users of Elements Connect get off a good start, we have embedded the Elements Connect getting started guide in the app. This comprehensive guide helps admins set-up their first connected fields, from connecting to a datasource to retrieving external data and customizing how it's displayed in custom fields.
• CO-3780 - Cache shall be active when configuring a new field

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3767 Elements Connect configuration is lost when upgrading from v5 to v6.5
• CO-3748 Exceptions (WARN) while parsing Elements Connect field values

🚀Learn quickly how to configure Elements Connect with your new getting-started guide.

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3767 Elements Connect configuration is lost when upgrading from v5 to v6.5
• CO-3748 Exceptions (WARN) while parsing Elements Connect field values

🚀Learn quickly how to configure Elements Connect with your new getting-started guide.

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3754: [Velocity] Unable to retrieve the attributes of a User Custom field
• CO-3753: Some functions are not suggested in the autocomplete for $currentCustomfieldValue
• CO-3736: When a custom view is disabled, it disables all other views.

Elements Connect for Jira Cloud is now in beta and free for a limited time Try it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3754: [Velocity] Unable to retrieve the attributes of a User Custom field
• CO-3753: Some functions are not suggested in the autocomplete for $currentCustomfieldValue
• CO-3736: When a custom view is disabled, it disables all other views.

Elements Connect for Jira Cloud is now in beta and free for a limited time Try it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

CO-3759: Access Token not refreshed

Elements Connect for Jira Cloud is now in beta and free for a limited timeTry it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

CO-3759: Access Token not refreshed

Elements Connect for Jira Cloud is now in beta and free for a limited timeTry it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

Elements Connect is now compatible with Jira 8.12

Elements Connect for Jira Cloud is now in beta and free for a limited time

Try it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

Elements Connect is now compatible with Jira 8.12

Elements Connect for Jira Cloud is now in beta and free for a limited time

Try it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3750 - XLM to JSON migration locked if Jira is restarted during a migration
• CO-3676 - "Copy display value" and "Copy key value" post-functions don't work on the Create transition
• CO-3744 - [Jira DC] Restoring a backup file in Elements Connect doesn't affect all nodes
• CO-3749 - Elements Connect does not follow redirect (3xx + 'Location' header) if the protocol changes (ex: http to https)

Elements Connect for Jira Cloud is now in beta and free for a limited time

Try it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3750 - XLM to JSON migration locked if Jira is restarted during a migration
• CO-3676 - "Copy display value" and "Copy key value" post-functions don't work on the Create transition
• CO-3744 - [Jira DC] Restoring a backup file in Elements Connect doesn't affect all nodes
• CO-3749 - Elements Connect does not follow redirect (3xx + 'Location' header) if the protocol changes (ex: http to https)

Elements Connect for Jira Cloud is now in beta and free for a limited time

Try it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3719 - Empty rows are automatically selected in Autocomplete Connect fields with multiple values
• CO-3702 - "No duplicates" and "Sort" options have no effect when searching on a Connect field in advanced mode

Exciting news: Elements Connect for Jira Cloud is now in beta and free for a limited time. Try it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3719 - Empty rows are automatically selected in Autocomplete Connect fields with multiple values
• CO-3702 - "No duplicates" and "Sort" options have no effect when searching on a Connect field in advanced mode

Exciting news: Elements Connect for Jira Cloud is now in beta and free for a limited time. Try it now!

If you're upgrading from Elements Connect v5, read this release note carefully!

CO-3739 - All Connect fields depending on $issue.project are displayed during the move operation

If you're upgrading from Elements Connect v5, read this release note carefully!

CO-3739 - All Connect fields depending on $issue.project are displayed during the move operation

This version enables you to easily configure connected custom fields fetching their values from two tools from Zendesk, the famous customer support ticket system, and sales CRM company: Zendesk Support and Zendesk Sell.

If you're upgrading from Elements Connect v5, read this release note carefully!

New features

• Add your Zendesk Support datasource - tutorial available here.
• Add your Zendesk Sell CRM datasource - tutorial available here.

Bug fix

• Some v5 fields are not detected when migrating to JSON format

This version enables you to easily configure connected custom fields fetching their values from two tools from Zendesk, the famous customer support ticket system, and sales CRM company: Zendesk Support and Zendesk Sell.

If you're upgrading from Elements Connect v5, read this release note carefully!

New features

• Add your Zendesk Support datasource - tutorial available here.
• Add your Zendesk Sell CRM datasource - tutorial available here.

Bug fix

• Some v5 fields are not detected when migrating to JSON format

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3724 - Error messages while indexing field values stored in XML

We are working on our next project: Elements Connect for Jira Cloud! ☁️If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3724 - Error messages while indexing field values stored in XML

We are working on our next project: Elements Connect for Jira Cloud! ☁️If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3714 - Can't configure a connection to a okta application with oauth2
• CO-3723 - HTTP 401 Error in Elements Connect fields for Jira Data Center instance
• CO-3622 - Impossible to set a Snapshot Date field because of an inconsistency between formats
• CO-3683 - Checkboxes & radio buttons not visible when configuring a new Elements Connect field (>Jira 8.4)

We are working on our next project: Elements Connect for Jira Cloud! ☁️If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from Elements Connect v5, read this release note carefully!

• CO-3714 - Can't configure a connection to a okta application with oauth2
• CO-3723 - HTTP 401 Error in Elements Connect fields for Jira Data Center instance
• CO-3622 - Impossible to set a Snapshot Date field because of an inconsistency between formats
• CO-3683 - Checkboxes & radio buttons not visible when configuring a new Elements Connect field (>Jira 8.4)

We are working on our next project: Elements Connect for Jira Cloud! ☁️If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from Elements Connect v5, read this release note carefully!

Admin tool

• CO-3684 - New tool to fix values corrupted by v. 6.1.2 / 6.1.3. Learn more in the documentation.
• We optimized the XML to JSON data migration tool released in v. 6.2.0. Reindexation to do manually after migration. Learn more in the documentation.

Improvements

• CO-3703 - New option to hide a read-only Connect field on create, edit and transition issue screens
• Increased security of the data sources passwords stored in Elements Connect

Bug fixes

• CO-3675 - Live User Fields are preselected in Bulk Edit
• CO-3705 - Can't configure a connection to GitHub with OAuth2
• CO-3696 - Missing parent configuration errors on dependent fields after Connect configuration update

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from Elements Connect v5, read this release note carefully!

Admin tool

• CO-3684 - New tool to fix values corrupted by v. 6.1.2 / 6.1.3. Learn more in the documentation.
• We optimized the XML to JSON data migration tool released in v. 6.2.0. Reindexation to do manually after migration. Learn more in the documentation.

Improvements

• CO-3703 - New option to hide a read-only Connect field on create, edit and transition issue screens
• Increased security of the data sources passwords stored in Elements Connect

Bug fixes

• CO-3675 - Live User Fields are preselected in Bulk Edit
• CO-3705 - Can't configure a connection to GitHub with OAuth2
• CO-3696 - Missing parent configuration errors on dependent fields after Connect configuration update

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

This update improves the migration time from XML fields to JSON. Improvement is around 30% faster but can vary depending the environment where migration is executed.

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

This update improves the migration time from XML fields to JSON. Improvement is around 30% faster but can vary depending the environment where migration is executed.

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

Improvement

• CO-3101 - You can now use the Salesforce datasource when your Jira base URL is not reachable from outside your network
• CO-3692 - Copy "Live text" field display value in a "Snapshot text" field with Elements Connect post functions

Admin tool

• CO-3607 - If you have upgrade from Elements Connect v5, you might be bothered by the change in the storage format.This version brings a migration tool you can use to convert the Connect field values stored with the v5 format (XML) into the v6 format (JSON)Learn more about this tool.

Bug fix

• CO-3688 - getOptionName() is not retrieving name of the "child" of Jira Select List (Cascading)

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

Improvement

• CO-3101 - You can now use the Salesforce datasource when your Jira base URL is not reachable from outside your network
• CO-3692 - Copy "Live text" field display value in a "Snapshot text" field with Elements Connect post functions

Admin tool

• CO-3607 - If you have upgrade from Elements Connect v5, you might be bothered by the change in the storage format.This version brings a migration tool you can use to convert the Connect field values stored with the v5 format (XML) into the v6 format (JSON)Learn more about this tool.

Bug fix

• CO-3688 - getOptionName() is not retrieving name of the "child" of Jira Select List (Cascading)

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

This version fixes 5 bugs:

• CO-3614 - Connect fields updated thought an Automation rule are not properly indexed
• CO-3585 - Configuration tester problem when testing Json datasource with wrong Key index
• CO-3486 - Elements Connect does not use Jira formatting to display numbers
• CO-3518 - Enter key clears SQL datasource configuration form inputs
• CO-3560 - Autocomplete shall suggest "$userInput" only if the editor is "Autocomplete"

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

This version fixes 5 bugs:

• CO-3614 - Connect fields updated thought an Automation rule are not properly indexed
• CO-3585 - Configuration tester problem when testing Json datasource with wrong Key index
• CO-3486 - Elements Connect does not use Jira formatting to display numbers
• CO-3518 - Enter key clears SQL datasource configuration form inputs
• CO-3560 - Autocomplete shall suggest "$userInput" only if the editor is "Autocomplete"

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

This version fixes 3 bugs:

• CO-1369 - Searching with currentUser() on Live User field does not work
• CO-3699 - Attributes with a "null" value are not displayed in the JSON payload
• CO-3673 - "No duplicates" option is not available in Search View when Read-Only - Single Value is selected in Edit View

Elements Connect is on its way to Jira Cloud! ☁️

Join us for an exclusive webinar on Feb. 18th and get a preview of this new app. Register now!

If you're upgrading from v5, read this release note carefully!!

This version fixes 3 bugs:

• CO-1369 - Searching with currentUser() on Live User field does not work
• CO-3699 - Attributes with a "null" value are not displayed in the JSON payload
• CO-3673 - "No duplicates" option is not available in Search View when Read-Only - Single Value is selected in Edit View

Elements Connect is on its way to Jira Cloud! ☁️

Join us for an exclusive webinar on Feb. 18th and get a preview of this new app. Register now!

If you're upgrading from v5, read this release note carefully!!

This version fixes 3 bugs:

• CO-3680 - Translated fields can be searched by ID only, not by name
• CO-3641 - The Search view doesn't work when $userInput is used in the query
• CO-3646 - Fordbidden error with contextless scoped Connect fields

Elements Connect is on its way to Jira Cloud! ☁️

Join us for an exclusive webinar on Feb. 18th and get a preview of this new app. Register now!

If you're upgrading from v5, read this release note carefully!!

This version fixes 3 bugs:

• CO-3680 - Translated fields can be searched by ID only, not by name
• CO-3641 - The Search view doesn't work when $userInput is used in the query
• CO-3646 - Fordbidden error with contextless scoped Connect fields

Elements Connect is on its way to Jira Cloud! ☁️

Join us for an exclusive webinar on Feb. 18th and get a preview of this new app. Register now!

If you're upgrading from v5, read this release note carefully!!

This version fixes 2 bugs and add one compatibility:

• CO-3662 - Dropdown Fields are displayed sometimes as free Text fields
• CO-3694 - Typing a special character in an autocomplete Connect field causes field to disappear
• Compatibilty with Jira 8.7.0 - User anonymisation feature

Elements Connect is on its way to Jira Cloud! ☁️

Join us for an exclusive webinar on Feb. 18th and get a preview of this new app. Register now!

If you're upgrading from v5, read this release note carefully!!

This version fixes 2 bugs and add one compatibility:

• CO-3662 - Dropdown Fields are displayed sometimes as free Text fields
• CO-3694 - Typing a special character in an autocomplete Connect field causes field to disappear
• Compatibilty with Jira 8.7.0 - User anonymisation feature

Elements Connect is on its way to Jira Cloud! ☁️

Join us for an exclusive webinar on Feb. 18th and get a preview of this new app. Register now!

If you're upgrading from v5, read this release note carefully!!

This version fixes 2 bugs:

• CO-3647 - Setting Accept header in OAuth datasource fails when fetching fields options
• CO-3678 - Inline editing broken with IE 11 when Elements Connect is enabled

Elements Connect is on its way to Jira Cloud! ☁️

Join us for an exclusive webinar on Feb. 18th and get a preview of this new app. Register now!

If you're upgrading from v5, read this release note carefully!!

This version fixes 2 bugs:

• CO-3647 - Setting Accept header in OAuth datasource fails when fetching fields options
• CO-3678 - Inline editing broken with IE 11 when Elements Connect is enabled

Elements Connect is on its way to Jira Cloud! ☁️

Join us for an exclusive webinar on Feb. 18th and get a preview of this new app. Register now!

If you're upgrading from v5, read this release note carefully!!

This version fixes four bugs:

• CO-3582 - Can't create / edit Issues when a Snapshot Date / Datetime field value is set, but empty
• CO-3668 - Dependencies to Insight fields do not work on edit / create issue screen
• CO-3682 - Impossible to select fields in the "Set Elements Connect field value" action in Automation (Global settings configuration)
• CO-3674 - Impossible to select fields in the "Set Elements Connect field value" action in Automation (Project level configuration)

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

This version fixes four bugs:

• CO-3582 - Can't create / edit Issues when a Snapshot Date / Datetime field value is set, but empty
• CO-3668 - Dependencies to Insight fields do not work on edit / create issue screen
• CO-3682 - Impossible to select fields in the "Set Elements Connect field value" action in Automation (Global settings configuration)
• CO-3674 - Impossible to select fields in the "Set Elements Connect field value" action in Automation (Project level configuration)

We are working on our next project: Elements Connect for Jira Cloud! ☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

This version fixes four bugs:

• CO-3654 - JQL search fails when a condition is set on any field AND a connect field AND $userInput is used in the Connect query
• CO-3657 - Move operation needs a selection on an Elements Connect field even if the source value is still valid in the target when the field has a dependency to the project

If you're upgrading from v5, read this release note carefully!!

This version fixes four bugs:

• CO-3654 - JQL search fails when a condition is set on any field AND a connect field AND $userInput is used in the Connect query
• CO-3657 - Move operation needs a selection on an Elements Connect field even if the source value is still valid in the target when the field has a dependency to the project

If you're upgrading from v5, read this release note carefully!!

This version fixes four bugs:

• CO-3677 - InputValue appears in Field Stored Key when using the Select editor
• CO-3655 - Error 500 when configuring a OAuth datasource to Microsoft Sharepoint (Azure)
• CO-3660 - Elements Connect field names are case sensitive in JQL when "~" is used
• CO-3578 - HTML returned by the datasource shall be escaped only when the editor can evaluate HTML and on display

If you're upgrading from v5, read this release note carefully!!

This version fixes four bugs:

• CO-3677 - InputValue appears in Field Stored Key when using the Select editor
• CO-3655 - Error 500 when configuring a OAuth datasource to Microsoft Sharepoint (Azure)
• CO-3660 - Elements Connect field names are case sensitive in JQL when "~" is used
• CO-3578 - HTML returned by the datasource shall be escaped only when the editor can evaluate HTML and on display

⚠️ If you're upgrading from v5, read this release note carefully!!

This version fixes two bugs :

• CO-3642 - It shall be possible to clear the "Value not found template" in the field configuration
• CO-3658 - Can't copy Live User into JIRA User using postfunction with JIRA 8.4

⚠️ If you're upgrading from v5, read this release note carefully!!

This version fixes two bugs :

• CO-3642 - It shall be possible to clear the "Value not found template" in the field configuration
• CO-3658 - Can't copy Live User into JIRA User using postfunction with JIRA 8.4

⚠️ If you're upgrading from v5, read this page carefully.

This version brings 4 new features:

• You can copy the value of a "Live user" field into any Jira field with the "Copy key to issue field" post function - CO-3521
• On Data Center, the "Specific load balancing cookie" load balancer strategy is now supported - CO-3568
• HTML returned by data sources can be evaluated (again!) - CO-3581
• Connect query engine now supports the JSD "Organizations" field, you can build queries based on the Organizations who have access to a request -CO-2357

We have also fixed 4 bugs, including the case where Connect lost dependencies after an app upgrade.

Learn more about the features unlocked by this new version on our blog and read the full release note.

We are working on our next project: Elements Connect for Jira Cloud! ☁️If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

⚠️ If you're upgrading from v5, read this page carefully.

This version brings 4 new features:

• You can copy the value of a "Live user" field into any Jira field with the "Copy key to issue field" post function - CO-3521
• On Data Center, the "Specific load balancing cookie" load balancer strategy is now supported - CO-3568
• HTML returned by data sources can be evaluated (again!) - CO-3581
• Connect query engine now supports the JSD "Organizations" field, you can build queries based on the Organizations who have access to a request -CO-2357

We have also fixed 4 bugs, including the case where Connect lost dependencies after an app upgrade.

Learn more about the features unlocked by this new version on our blog and read the full release note.

We are working on our next project: Elements Connect for Jira Cloud!☁️

If you are a Jira Cloud user or plan to migrate your Jira Server instance to Cloud: register here to be updated of our progress!

If you're upgrading from v5, read this release note carefully!!

This version brings the compatibility with Jira 8.4

If you're upgrading from v5, read this release note carefully!!

This version brings the compatibility with Jira 8.4

If you're upgrading from v5, read this release note carefully!!

• CO-3549 - Connect field disappears from the basic search options when refreshing the page
• CO-3549 - Description of Elements Connect fields doesn't support HTML and JS
• CO-3549 - Connect fields do not work on JSD if a global default value is set (IE11)
• CO-3549 - User field selected value do not appear in basic search

If you're upgrading from v5, read this release note carefully!!

• CO-3549 - Connect field disappears from the basic search options when refreshing the page
• CO-3549 - Description of Elements Connect fields doesn't support HTML and JS
• CO-3549 - Connect fields do not work on JSD if a global default value is set (IE11)
• CO-3549 - User field selected value do not appear in basic search

If you're upgrading from v5, read this release note carefully!!

Bug fixes:

• CO-3615 - Field broken after upgrade V5 to V6 if cache is active + empty query
• CO-3624 - NullPointerException error logged when a Live text legacy field query does not return any result
• CO-3613 - Error when executing a request on an AppLink datasource if the query contains velocity on multiple lines
• CO-3627 - Hitting the Enter key to submit the "user input" input reloads the configuration page

If you're upgrading from v5, read this release note carefully!!

Bug fixes:

• CO-3615 - Field broken after upgrade V5 to V6 if cache is active + empty query
• CO-3624 - NullPointerException error logged when a Live text legacy field query does not return any result
• CO-3613 - Error when executing a request on an AppLink datasource if the query contains velocity on multiple lines
• CO-3627 - Hitting the Enter key to submit the "user input" input reloads the configuration page

If you upgrade from v5, please read this release note carefully!!

This version fixes bugs:

• CO-3609 - Edit issue: Connect fields depending on user field not refreshed when their parent field is edited
• CO-3612 - Error when editing a field which has a dependency to a "Multi value select" Jira field
• CO-3605 - "Set a field value" post function selects all values available for a single value field instead of the first one
• CO-3606 - Popup doesn't display properly when in-line editing dependent Element Connect fields

If you upgrade from v5, please read this release note carefully!!

This version fixes bugs:

• CO-3609 - Edit issue: Connect fields depending on user field not refreshed when their parent field is edited
• CO-3612 - Error when editing a field which has a dependency to a "Multi value select" Jira field
• CO-3605 - "Set a field value" post function selects all values available for a single value field instead of the first one
• CO-3606 - Popup doesn't display properly when in-line editing dependent Element Connect fields

If you upgrade from v5, please read this release note carefully!!

This version fixes bugs:

• CO-3609 - Edit issue: Connect fields depending on user field not refreshed when their parent field is edited
• CO-3612 - Error when editing a field which has a dependency to a "Multi value select" Jira field
• CO-3605 - "Set a field value" post function selects all values available for a single value field instead of the first one
• CO-3606 - Popup doesn't display properly when in-line editing dependent Element Connect fields

If you upgrade from v5, please read this release note carefully!!

This version fixes this bugs:

• CO-3604 - Legacy fields don't behave like Deprecated fields with schemes
• CO-3584 - Cannot copy Connect Live Text key value into another Live Text Connect field on Post Functio

If you upgrade from v5, please read this release note carefully!!

This version fixes this bugs:

• CO-3604 - Legacy fields don't behave like Deprecated fields with schemes
• CO-3584 - Cannot copy Connect Live Text key value into another Live Text Connect field on Post Function

If you upgrade from v5, please read this release note carefully!!

This version fixes some bugs which are listed here :

• CO-3510 - Can't edit Elements Connect field contextualized on an issue type from the "Convert subtask to issue" when target task has a different workflow: Forbidden 403
• CO-3594 - Impossible to use default value for an Elements Connect field with multi selection in JSD
• CO-3596 - Elements Connect fields ignore the "Required" or "Mandatory" option
• CO-3600 - Make it clear that an issue shall be selected in the configuration tester when there is a dependency to $issue

If you upgrade from v5, please read this release note carefully!!

This version fixes some bugs which are listed here :

• CO-3510 - Can't edit Elements Connect field contextualized on an issue type from the "Convert subtask to issue" when target task has a different workflow: Forbidden 403
• CO-3594 - Impossible to use default value for an Elements Connect field with multi selection in JSD
• CO-3596 - Elements Connect fields ignore the "Required" or "Mandatory" option
• CO-3600 - Make it clear that an issue shall be selected in the configuration tester when there is a dependency to $issue

If you upgrade from v5, please read this release note carefully!!

This version fixes some bugs which are listed here :

• CO-3593 - Impossible to use default value for an Elements Connect field in JSD
• CO-3208 - Autocomplete multi value Elements Connect field cannot be used on Safari iOS and Android
• CO-3524 - Problem with ScriptRunner and CPU Usage
• CO-3590 - Parent fields not appearing when (bulk) moving issues between projects
• CO-3595 - Cannot edit Elements Connect fields value after upgrade to 6.0.4
• CO-3496 - Selection in the first column of a cascading select list deselects option in the second column

If you upgrade from v5, please read this release note carefully!!

This version fixes some bugs which are listed here :

• CO-3593 - Impossible to use default value for an Elements Connect field in JSD
• CO-3208 - Autocomplete multi value Elements Connect field cannot be used on Safari iOS and Android
• CO-3524 - Problem with ScriptRunner and CPU Usage
• CO-3590 - Parent fields not appearing when (bulk) moving issues between projects
• CO-3595 - Cannot edit Elements Connect fields value after upgrade to 6.0.4
• CO-3496 - Selection in the first column of a cascading select list deselects option in the second column

If you upgrade from v5, please read this release note carefully!!

This version brings back the compatibility with Jira Misc Workflow Extensions app (JMWE) post functions, see CO-3583 - Can't copy Elements Connect fields with JMWE.

It also fixes some bugs which are listed here :

• CO-3265 - Dependencies are not resolved when bulk-moving issues between projects
• CO-3580 - JSON Path in Columns with velocity or empty lines not evaluated
• CO-3587 - Unknown error when trying to save field configuration when license is not valid

If you upgrade from v5, please read this release note carefully!!

This version brings back the compatibility with Jira Misc Workflow Extensions app (JMWE) post functions, see CO-3583 - Can't copy Elements Connect fields with JMWE.

It also fixes some bugs which are listed here :

• CO-3265 - Dependencies are not resolved when bulk-moving issues between projects
• CO-3580 - JSON Path in Columns with velocity or empty lines not evaluated
• CO-3587 - Unknown error when trying to save field configuration when license is not valid

If you upgrade from v5, please read this release note carefully!!

In Elements Connect 6.0 we introduced some changes in the fields value storage format which had an impact on the compatibility of Elements Connect with third-party apps. We did our best to make sure Elements Connect remained compatible with the most popular third-party apps, however, we didn't take into account some commonly used apps.

In this version, we're fixing some compatibility issues that weren't addressed by the 6.0 version.

Rest assured that we know how integration with other apps is important for customers and that fixing compatibility bugs is our #1 priority.

Bug fixes:

• CO-3572 - Broken compatibility with JEMH
• CO-3579 - Can't set Connect field values when importing issues from CSV
• CO-3577 - Elements Connect does not display correctly special characters (like Cyrillic alphabet or chars with accents)
• CO-3576 - Dependencies between fields appear broken whilst they should not

If you upgrade from v5, please read this release note carefully!!

In Elements Connect 6.0 we introduced some changes in the fields value storage format which had an impact on the compatibility of Elements Connect with third-party apps. We did our best to make sure Elements Connect remained compatible with the most popular third-party apps, however, we didn't take into account some commonly used apps.

In this version, we're fixing some compatibility issues that weren't addressed by the 6.0 version.

Rest assured that we know how integration with other apps is important for customers and that fixing compatibility bugs is our #1 priority.

Bug fixes:

• CO-3572 - Broken compatibility with JEMH
• CO-3579 - Can't set Connect field values when importing issues from CSV
• CO-3577 - Elements Connect does not display correctly special characters (like Cyrillic alphabet or chars with accents)
• CO-3576 - Dependencies between fields appear broken whilst they should not

If you are upgrade from v5, please read this release note carefully!!

This version brings the support of the gzip encoding for URL datasources. If you're requesting large files with Elements Connect, you should activate this option in your datasource configuration to speed up your fields.

Fixed bugs related to the 6.0 version:

• CO-3492 - Connect should handle the gzip encoding
• CO-3547 - Order of JSON columns not saved in the correct order
• CO-3563 - "Cannot read property 'maxSuggestions' of undefined" error
• CO-3564 - NullPointerException when generating configuration backup
• CO-3565 - HTML returned by the data source shall never be evaluated
• CO-3567 - Connect Legacy Text fields not compatible with Jira Misc Workflow and other apps
• CO-3569 - Export a field configuration even if the CF is deleted
• CO-3570 - It shall be possible to open and delete a field configuration when field is missing
• CO-3571 - Add debug information in logs when searching on connect fields generates an error

If you are upgrade from v5, please read this release note carefully!!

This version brings the support of the gzip encoding for URL datasources. If you're requesting large files with Elements Connect, you should activate this option in your datasource configuration to speed up your fields.

Fixed bugs related to the 6.0 version:

• CO-3492 - Connect should handle the gzip encoding
• CO-3547 - Order of JSON columns not saved in the correct order
• CO-3563 - "Cannot read property 'maxSuggestions' of undefined" error
• CO-3564 - NullPointerException when generating configuration backup
• CO-3565 - HTML returned by the data source shall never be evaluated
• CO-3567 - Connect Legacy Text fields not compatible with Jira Misc Workflow and other apps
• CO-3569 - Export a field configuration even if the CF is deleted
• CO-3570 - It shall be possible to open and delete a field configuration when field is missing
• CO-3571 - Add debug information in logs when searching on connect fields generates an error

We've put UX and ease of configuration the heart of this release. This version comes with a completely redesigned admin interface featuring a field configuration tester, a new snapshot field category, and more.

UPGRADING FROM V5

This version brings some breaking changes.

As we have improved the core engine of Connect, we recommend to read the full release note and to test this new version on a staging instance.

Downgrade from v6 to v5 is not possible due to a change in the storage format.

CONFIGURATION TESTER

We've built a brand new field configuration tester which provides insights on your field configuration. It shows query results, a preview of how your data will be displayed in issues and metrics about query execution time.

SNAPSHOT FIELD

We've added a new category of custom fields: snapshot fields. Instead of fetching data every time a screen is refreshed, snapshot fields get the record value from the data source only once.

For more details, read the full release notes.

We've put UX and ease of configuration the heart of this release. This version comes with a completely redesigned admin interface featuring a field configuration tester, a new snapshot field category, and more.

UPGRADING FROM V5

This version brings some breaking changes.

As we have improved the core engine of Connect, we recommend to read the full release note and to test this new version on a staging instance.

Downgrade from v6 to v5 is not possible due to a change in the storage format.

CONFIGURATION TESTER

We've built a brand new field configuration tester which provides insights on your field configuration. It shows query results, a preview of how your data will be displayed in issues and metrics about query execution time.

SNAPSHOT FIELD

We've added a new category of custom fields: snapshot fields. Instead of fetching data every time a screen is refreshed, snapshot fields get the record value from the data source only once.

For more details, read the full release notes.

In this version, we added the compatibility with Elements Copy & Sync 2.18.0.

If you are using Elements Connect fields in an Elements Copy & Sync field mapping, you will need to install this update (or any 6.x version) before you upgrade to Elements Copy & Sync 2.18.0.

Elements Connect 5.14.0 implements version 0.2.0 of Elements Connect Java API used by Elements Copy & Sync 2.18.0 (see Javadoc here).

Please, see the compatibility matrix between the two apps to know which versions you should use in order for the two products to work well together.

In this version, we added the compatibility with Elements Copy & Sync 2.18.0.

If you are using Elements Connect fields in an Elements Copy & Sync field mapping, you will need to install this update (or any 6.x version) before you upgrade to Elements Copy & Sync 2.18.0.

Elements Connect 5.14.0 implements version 0.2.0 of Elements Connect Java API used by Elements Copy & Sync 2.18.0 (see Javadoc here).

Please, see the compatibility matrix between the two apps to know which versions you should use in order for the two products to work well together.

• CO-3536 - "Forbidden (403)" when editing a hidden field in a Request Type in JSD
• CO-3538 - "Forbidden (403)" when using the "Create epic" feature in a Software board

• CO-3536 - "Forbidden (403)" when editing a hidden field in a Request Type in JSD
• CO-3538 - "Forbidden (403)" when using the "Create epic" feature in a Software board

• CO-3535 crowd support for local Jira datasources

• CO-3535 crowd support for local Jira datasources

• CO-3533 fixed 403 issues with issues moves
• CO-3534 fixed issues with dependant fields evaluation during issues moves

• CO-3533 fixed 403 issues with issues moves
• CO-3534 fixed issues with dependant fields evaluation during issues moves

• CO-3531 fixed access restriction issues

• CO-3531 fixed access restriction issues

• CO-3527 - NullPointerException with the Query Tester and an LDAP datasource
• CO-3528 - Memory leak in Connect

• CO-3527 - NullPointerException with the Query Tester and an LDAP datasource
• CO-3528 - Memory leak in Connect

• CO-3520 : Integration issue between Connect, Automation and ScriptRunner

CO-3520 Integration issue between Connect, Automation and ScriptRunner

• CO-3438 : LDAP data source configuration does not allow to set an login and password on Jira 8
• CO-3512 : Searching on Connect field not working on Jira 8 if the key is not an integer
• CO-3438 : Connect fields not loaded correctly at first connection on JSD

• CO-3438 : LDAP data source configuration does not allow to set an login and password on Jira 8
• CO-3512 : Searching on Connect field not working on Jira 8 if the key is not an integer
• CO-3438 : Connect fields not loaded correctly at first connection on JSD

Valiantys Software has a new name: Elements, a Valiantys company!

We've also renamed our products to provide consistency and clarity across our apps portfolio.

nFeed will now be called Elements Connect.

Valiantys Software has a new name: Elements, a Valiantys company!

We've also renamed our products to provide consistency and clarity across our apps portfolio.

nFeed will now be called Elements Connect.

• NFEED-3499 - nFeed does not always retrieve options when connected to Jira REST API (Data Center)

• NFEED-3501 - Error 403 on JSD 3.2.4 portal with nFeed fields
• NFEED-3498 - Indexing fails on issues where a multiple value nFeed field is set
• NFEED-3483 - Can't edit nFeed field contextualized on an issue type from the "Convert subtask to issue": Forbidden 403

• NFEED-3501 - Error 403 on JSD 3.2.4 portal with nFeed fields
• NFEED-3498 - Indexing fails on issues where a multiple value nFeed field is set
• NFEED-3483 - Can't edit nFeed field contextualized on an issue type from the "Convert subtask to issue": Forbidden 403

• NFEED-3490 - Hidden fields on JSD cannot be referred with $issue.customfield_xxxxx
• NFEED-3488 - Dependent Fields not working in Customer Portal

• NFEED-3490 - Hidden fields on JSD cannot be referred with $issue.customfield_xxxxx
• NFEED-3488 - Dependent Fields not working in Customer Portal

nFeed is now compatible with Jira 8

nFeed is now compatible with Jira 8

This version fixes bugs related to the permissions.

• NFEED-3481 - Can't edit a contextualized nFeed field when an issue is "quickly" created from a scrum backlog and a field is mandatory
• NFEED-3476 - Can't edit nFeed field contextualized on an issue type from the "Create link issue dialog": Forbidden 403

This version fixes bugs related to the permissions.

• NFEED-3481 - Can't edit a contextualized nFeed field when an issue is "quickly" created from a scrum backlog and a field is mandatory
• NFEED-3476 - Can't edit nFeed field contextualized on an issue type from the "Create link issue dialog": Forbidden 403

nFeed is now Data Center approved.

It means that as of today we are offering a Data Center version of nFeed that has been tested and approved by Atlassian to live up to a Data Center-specific standard.

Having nFeed Data Center approved demonstrates our commitment to Enterprise customers and aligns with our investments in providing excellent performance and customer service. It's the culmination of months worth of effort to make sure nFeed meets the standard of large instances.

This version fixes bugs related to the permissions.

NFEED-3474 - 403 error for nFeed mandatory fields on Bulk workflow transition validation screen

NFEED-3473 - Cannot edit nFeed mandatory fields on Bulk Edit validation screen

NFEED-3468 - Can't change sub-tasks issue type (403 error)

NFEED-3470 - 403 error for nFeed mandatory fields on Bulk Edit validation screen

• NFEED-3467 - Can't set default value of nFeed field
• NFEED-3466 - Can't edit a nFeed field when it's contextualised on a sub-task issue type
• NFEED-3465 - Edit nFeed fields on Bulk transition screen does not work
• NFEED-3464 - Edit nFeed fields on Issue transition screen does not work

This version fixes a critical security vulnerability found in nFeed.

Updates are available for all nFeed versions that are compatible with a supported version of Jira (7.3 to 7.13). We strongly recommend customers update nFeed at the earliest opportunity to patch this vulnerability.

Feel free to reach out to our support team if you have any questions or need help upgrading.

This version contains the same security fix as 7.13.12. It also fixes a bug introduced by 7.13.12 where permission was denied when nFeed custom field was contextualized on an issue type.

This version fixes bugs related to the permissions.

• NFEED-3474 - 403 error for nFeed mandatory fields on Bulk workflow transition validation screen
• NFEED-3473 - Cannot edit nFeed mandatory fields on Bulk Edit validation screen
• NFEED-3470 - 403 error for nFeed mandatory fields on Bulk Edit validation screen
• NFEED-3468 - Can't change sub-tasks issue type (403 error)
• NFEED-3467 - Can't set default value of nFeed field
• NFEED-3466 - Can't edit a nFeed field when it's contextualised on a sub-task issue type
• NFEED-3465 - Edit nFeed fields on Bulk transition screen does not work
• NFEED-3464 - Edit nFeed fields on Issue transition screen does not work

This version fixes a critical security vulnerability found in nFeed.

Updates are available for all nFeed versions that are compatible with a supported version of Jira (7.3 to 7.13). We strongly recommend customers update nFeed at the earliest opportunity to patch this vulnerability.

Feel free to reach out to our support team if you have any questions or need help upgrading.