- EA Connector for codebeamer version 2.0.0 was released on February 7th, 2020.
- EA Connector for codebeamer version 2.0.1 was released on February 19th, 2020.
- EA Connector for codebeamer version 2.0.2 was released on April 1st, 2020.
- EA Connector for codebeamer version 2.0.3 was released on April 16th, 2020.
- EA Connector for codebeamer version 2.0.4 was released on April 28th, 2020.
- EA Connector for codebeamer version 2.0.5 was released on August 21st, 2020.
codeBeamer Version Restriction
The versions 2.0.x of the EA Connector for codebeamer only support codebeamer version 9.5.
The minimum supported version of codebeamer is version 9.5.
If you want to use codebeamer version 10, please use the current version 2.1.3 of the EA Connector for codebeamer: Release 2.1
|Floating license as default license type||If the license management dialog is started, the license type "floating" is selected as default.||2.0.5|
|Menu location of "Configure codebeamer Server Settings"||The menu for configuring the server codebeamer server settings (URL, user and password) is now accessible from everywhere in EA (main menu, project browser and diagram conetext menu).||2.0.5|
|Impact of Import/Export is shown (as count)||If you import / export data, the connector now displays how many elements will be added / modified if you continue with the operation.||2.0.2|
|Export Diagrams of imported requirements||It is now possible to export diagrams to codebeamer, from packages that were initially imported from codebeamer.
This feature enables you f.e. to import requirements from codebeamer and enhance the description with a diagram, that can be export back to codebeamer.
|Licensing: Floating||Floating Licenses were introduced.||2.0.2|
|Licensing: Demo Mode||If there is no valid license, it is now possible to start a demo mode once, which enables a trial period of 30 days.||2.0.2|
|Progress bar for Mapping UI||A progressbar was added, which is displayed during the initialization of the mapping UI.||2.0.1|
|Initial Version of the EA Connector for codebeamer||The predecessor of the connector (version 1.x) was implemented by Intland. This is the first version published by LieberLieber.||2.0.0|
|TSL error when connecting to the codebeamer server||There were connection problems with TSL v1.3 when connecting to codebeamer for configuring the mapping.||2.0.5|
|Create Custom Mapping: newly added tagged value attribute is not considered in cB data synchronization||If a custom mapping with an attribute mapping including a tagged value was created, the tagged value attribute was not considered during cB import / export.||2.0.5|
|Wrong text in license dialog||If a floating license was applied in the license dialog (instead of applying it on the RLM server) the EA plugin indicated that the provided licenses was not a LemonTree license.||2.0.5|
|Tracker package name wasn't updated properly||The name of the package, which represents the tracker after an import was not updated accordingly in the EA database. After a reload of the EA project, you could still see the previous package name. Once the package was selected, the name was refreshed and the name of the tracker was displayed.||2.0.5|
|Import to SQL-based EA Repositories failed||If an EA Repository, hosted on an SQL Server was used for importing data from codebeamer, the operation failed.||2.0.5|
|Mapping UI shows wrong direction of sync||If you started an export to codebeamer for the first time, the Mapping UI opened and the radio button "Import" was pre-selected.||2.0.5|
|Trace Links were not consistently created||The trace links to other tracker items were not created consistently for each export of new data to codebeamer.||2.0.4|
|Changed diagram was not exported||Changes in diagrams were not recognized as changes, therefore the diagrams were not exported.||2.0.4|
|Diagram duplication in codebeamer||The image of an exported diagram was added every time an export was executing, hence duplicating the attachment of the tracker item.||2.0.3|
|Import/Export-Workflow||Packages that were initially imported can only be synchronized with an Import and packages that were initially exported can only be synchronized with an Export.||2.0.2|
|Performance of Mapping UI||The start-up performance of the mapping UI was improved significantly.||2.0.2|
|Credentials in logfile||The backend logfile contained credentials info as plain text.||2.0.2|
|Removing of trace links||Traceability links that were deleted in EA were not updated in codebeamer accordingly.||2.0.1|
|Progress bar for Mapping UI||A progressbar was added during the initialization of the mapping UI.||2.0.1|
|Import to SQL EA Repositories||Up to version 2.0.4 the import into EA projects, which are stored on SQL databases was not supported.
→ This issue was resolved in the release 2.0.5
|2.0.2 - 2.0.4|