Fixes in this release

Release 2.4.5

Date Source failure in LQE and LDX when discovering updated Jira issues

Jira data sources in IBM Link Index Provider (LDX) and IBM Lifecycle Query Engine (LQE) failed to update when new TRS Change Log pages were generated for recent modifications in Jira.

Release 2.4.4

Empty reports in Report Builder when limiting the scope.

In ELM Report Builder, limiting the scope of a report to a subset of Jira projects was producing empty results since version 2.4.3. Jira projects were no longer correctly identified as Change Management projects.

Duplicate DOORS Next 7.0.1 requirement selection dialog.

In Jira, when creating a link to DOORS Next requirements (version 7.0.1 or higher), the Jira link creation dialog displayed duplicate labels for DOORS selection dialogs, which could cause confusion though harmless.

Release 2.4.3

Cannot use drag and drop to create links with IBM Engineering Requirements Management DOORS 9.7.

DOORS 9.7 was not recognized as a supported application for drag and drop of artifacts to create links. As a consequence, the only option for the user was to use the OSLC Selection Dialog to create links to DOORS.

Wrong position for the online-help button on Jira versions.

On Jira versions prior to 7.10.0, the online-help button (displayed in all connector dialogs) were incorrectly positioned.

Missing delete icon for Friends and Consumers.

On Jira versions prior to 7.10.0, the delete icon in Friends and Consumers pages was missing.

Release 2.4.2

No known bugs were fixed on this release.

Release 2.4.1

Cannot associate a global configuration to a Jira Version

On previous versions, the user could not display the global configuration dialog in Jira with Oracle database.

Release 2.4.0

Cannot associate a functional user to consumers when users are anonymized

When users are anonymized in Jira (for compliance with General Data Protection Regulation), such users were not correctly rendered in the Issue selection dialog and it was not possible to associate them as functional users to consumers.

Cannot show the preview of a DOORS Next migrated requirement

When requirements were migrated from DOORS Next 6.0.x to 7.0.x, it was not possible to show the preview of those artifacts from Jira.

Release 2.3.2

Cannot create a Jira issue from remote application if Issue Type field is not visible.

If the Jira Issue Creation Screen did not display the Issue Type field, no Jira Issue could be created from an OSLC Remote Application. Such field is now always displayed in OSLC creation dialog; the Jira Creation Screen itself doesn't need to be modified.

Cannot link to Jira issue with non-printable characters in text fields.

If a Jira issue had a text field with non printable characters (all characters before index 32 in ASCII table), no OSLC link could be created from an OSLC Remote Application to this issue.

TRS store corruption on Jira Data Center with Linux NFS.

If Linux NFS was used for the Home directory of Jira Data Center, the Tracked Resource Set (TRS) information stored in this directory could become corrupted, leading IBM Lifecycle Query Engine (LQE) administrator to re-index frequently the Jira Data Sources.

Release 2.3.1

Epic Link field rendering error on creation dialog.

If no default issue type was set for a working project Issue Type Scheme, there was an exception in the Jira Issue creation dialog when rendering the Epic Link field.

Consumer becomes untrusted when removing the functional user.

Removing a functional user from a trusted consumer was causing the consumer to become untrusted.

Release 2.3.0

No known bugs were fixed on this release.

Release 2.2.0

Missing TRS event entries

On previous version, some TRS event entries were missing causing wrong synchronization with IBM Link Index Provider (LDX) / IBM Lifecycle Query Engine (LQE) datasources.

Double waiting spinner on Internet Explorer

On previous versions, a double waiting spinner could be seen when creation Collaboration Links or adding project associations on Internet Explorer.

Cannot visualize small previews of remote artifacts if remote HTTP session got expired

On previous versions when the OSLC Remote Application HTTP session got expired, there was no way to start it again (without refreshing the page) in order to see small previews.

Possible wrong linking to versioned artifacts if Link/Version-Field Mapping was not set

If the Link/Version-Field Mapping was not set on previous versions, selection/creation dialogs was not preventing from creating Collaboration Links while they should in order to prevent a possible wrong linking.

Release 2.1.0

Jira base URL change support without server restart

On previous versions, a change on the Jira base URL would require a server restart for OSLC Connect to use the new value. This restart is not longer needed.