Instability during TRS operations could lead to duplicate key errors.
A duplicate key error on TRS tables could appear due to system instability like disabling/enabling cluster nodes.
Calm Filter endpoint replies 403 error
The endpoint required more changes to work after migration to Jira 10.
No known bugs were fixed on this release.
Double PUT request for Windchill Simplified Change Object Creation.
The Linking Wizard could sometimes send twice the request to add a link to Windchill when using the Simplified Creation Dialog.
Exclusive Issue Type creation dialog submit issue.
When the exclusive Issue Type was checked in the Issue Types Mapping admin page, the Issue Type combo is correctly disabled but would not send the Issue Type for creation leading to an error.
Instability during TRS operations could lead to duplicate key errors.
A duplicate key error on TRS tables could appear due to system instability like disabling/enabling cluster nodes.
Scroll bar missing in the Linking Wizard for remote Projects.
The Linking Wizard had no bar for scrolling down and selecting a remote project from the bottom when multiple projects were associated.
Tracks Change Set Links cannot be deleted from Jira.
Tracks Change Set Links can be created only from DOOR Next Change Sets. However, it was not possible to remove them from Jira once created when they should be.
Deleted Version Associations cleanup
Under some special conditions, removing a Jira version associated to a Global Configuration could cause errors in the JQL of the selection dialog when linking from remote applications.
Truncated TRS feeds on out-of-sync Data Center environments.
Some unusual TRS events could cause the truncation of TRS feeds on regular basis, requiring a re-index of consuming data sources, typically IBM LDX or LQE. This fix prevents the TRS truncation in such environments.
No known bugs were fixed on this release.
No known bugs were fixed on this release.
Fixed compatibility with MySQL 8.0.
OSLC Connect for Jira was not compatible with MySQL 8.0, due to a change in recommended character set in MySQL.
Links not visually removed in Jira Board.
When collaboration links were deleted from a Jira Board, the links were correctly deleted in the storage but not visually removed from the page. The page is now automatically refreshed on link deletion.
Special characters prevent remote OSLC access to Jira.
Special characters used in project names were preventing OSLC access. This fix sanitizes project names to address this issue.
Cannot select a Release using filters from IBM Global Configuration Management.
From an IBM Global Configuration, when adding a link to a Release, it was not possible to select a Jira Version if a search or filter was applied first.
Inconsistent Collaboration Links when Version is not associated to a Global Configuration.
There was an inconsistent behavior when an Issue was using multiple Jira Versions, in Affects Version or Fix Version fields, and only some of them were associated to a Global Configuration. That made ELM applications to display inappropriate links to such Issue for some Global Configurations.
Fixed compatibility issues with Jira Plugin Agile Hive.
A conflict with Agile Hive caused some buttons to be inactive. This is now fixed.
No known bugs were fixed on this release.
No known bugs were fixed on this release.
Appfire Configuration Manager for Jira (CMJ) integration restored.
The integration for Appfire Configuration Manager for Jira (CMJ) stopped working in OSLC Connect for Jira 3.3.0, where support for Java 8 was removed.
Cannot create issues with a required Issue Security Level.
The Issue Security Level selected in the creation dialog was not saved while creating the issue.
LQE fails with "Locks acquirement timeout expired" on Jira TRS data source.
On high load, IBM Lifecycle Query Engine (LQE) sometimes reported that a lock could not be acquired for accessing a Jira TRS data source (HTTP 503).
Preview missing for some linked Polarion documents.
There was no OSLC rich preview for some linked Polarion documents containing spaces in their title.
Jira links to some remote artifacts displayed as "Not connected resource".
When the title of a remote artifact (e.g. a DOORS Next requirement) contains new line characters, the link from a Jira issue was displayed as "Not connected resource", though the link was valid.
Cannot search for issues not having a Reporter.
From a remote application, when searching for a Jira issue to link to the remote artifact, the search results were not showing issues not having a value for the Reporter field. The Reporter field may not have a value in some cases when the issue was cloned. The selection dialog now shows the Creator field in such case.
Upgrade to the 3.2.0 version was not possible if Link Decorators were disabled.
Upgrade was not possible if both the Priority and Status Link Decorators were disabled.
Unrecognized link between a Jira issue and a DOORS Next change set.
The "Tracks Change Set" link between a Jira issue and a DOORS Next change set was no longer correctly processed, preventing the correct display of the linked requirement and the discovery of the link from DOORS Next.
Rejection of a dropped Windchill web URL for creating a link.
When a Windchill web URL was dropped in Jira's OSLC linking wizard, a loop made an authentication popup to constantly open and close. The user is now informed such Windchill web URL cannot be used to initiate link creation.
No known bugs were fixed on this release.
Cursor misplaced in the Request participants field.
On service projects, the cursor was behind the user names in the Request participants field.
No known bugs were fixed on this release.
Linking from IBM DOORS Next to Jira was not possible on some projects.
Some Issue Type mapping configurations were wrongfully preventing to link to Jira issues. The message "Linking is not possible because Jira does not support Change Management Development Plans" was displayed instead.
Random errors occurred when dropping RMM designs for linking.
"An error prevented this action to complete. Please contact a support representative." error was displayed from time to time when dropping RMM designs for linking.
Bulk operations failed for transitions when The OSLC Property Match Validator is configured.
Transitions couldn't be performed, in bulk operations, when The OSLC Property Match Validator was configured.
Unavailable Issues Previews with custom screens.
The issue preview was not available in the remote application if the associated screen to the preview was deleted.
TRS data sources rebuild needed sporadically.
Remote TRS clients (LQE) needed to rebuild Jira's TRS data sources from time to time.
UI rendering error with ALM Works Structure.
A styling conflict with ALM Works Structure plug-in prevented the right display of issues in its view.
No known bugs were fixed on this release.