Known issues

An error is displayed when the IBM Engineering Workflow Management Client Extension is installed with products based on Eclipse 4.6 (Neon).

First occurrence: 6.0.3

Problem: When the IBM Engineering Workflow Management, formerly known as Rational Team Concert Client Extension is installed with products that are based on Eclipse 4.6 (Neon), such as Rational Software Architect, an error might be displayed once each session with text such as An SWT error has occurred or No more handles.

Workaround: On Linux systems that use the apt-get tool to install software, run the following command to install the libwebkitgtk library:sudo apt-get install libwebkitgtk-1.0-0On Linux systems that use RPM to install software, such as Red Hat, download webkitgtk-2.4.9-1.el7.x86_64.rpm and run sudo rpm -ihv webkitgtk-2.4.9-1.el7.x86_64.rpm to install it

Conditions might be removed if queries created in the web client are edited in earlier versions of the client for Eclipse IDE.

First occurrence: 6.0.6

Problem: If you use version 6.0.6 or later of IBM Engineering Workflow Management) web client to create a work item query that contains a Tags equals Unassigned condition, and then edit the query in version 6.0.5 or earlier of the client for Eclipse IDE, the Tags equals Unassigned condition might be removed.

Workaround: Do not use a version 6.0.5 or earlier client for Eclipse IDE to edit a work item query that was created or edited in the 6.0.6 or later web client.

Context aware search facility does not work in release 7.0.2.

First occurrence: 7.0.2

Problem: You cannot use the context aware search ability from the work item context menu when a 7.0.2 search engine is deployed. The search results are empty.

Workaround: Use context aware search engine from 7.0.1. This issue was resolved in 7.0.2 iFix001 and the context aware search ability from the work item context menu works as before.

IBM Engineering Workflow Management client is not installed on all instances of Microsoft Visual Studio 2017

First occurrence: 6.0.4

Problem: When you install the IBM Engineering Workflow Management client for Microsoft Visual Studio IDE from IBM Installation Manager and select Visual Studio 2017, the integration is installed on all instances of Microsoft Visual Studio 2017. However, if you install additional instances of Microsoft Visual Studio 2017 after you install the IBM Engineering Workflow Management client, the integration is not available on the newly installed instances of Microsoft Visual Studio 2017.

In IBM Installation Manager, this process installs the IBM Engineering Workflow Management client on all installed instances of Microsoft Visual Studio 2017.

IBM Engineering Workflow Management client is not installed on all instances of Microsoft Visual Studio 2019.

First occurrence: 6.0.6.1

Problem: When you install the IBM Engineering Workflow Management client for Microsoft Visual Studio IDE from IBM Installation Manager and select Visual Studio 2019, the integration is installed on all instances of Microsoft Visual Studio 2019. However, if you install additional instances of Microsoft Visual Studio 2019 after you install the IBM Engineering Workflow Management client, the integration is not available on the newly installed instances of Microsoft Visual Studio 2019.

IBM Engineering Workflow Management Tracking and Planning artifacts from existing archived project areas are not automatically deleted from the LQE store on upgrade to 7.0.2

First occurrence: 7.0.1

Problem: IBM Engineering Workflow Management Tracking and Planning artifacts from existing archived project areas are not automatically deleted from the LQE store after upgrade to 7.0.2. In 7.0.2, when you archive a project area, delete events are published to the IBM Engineering Workflow Management Tracking and Planning TRS feed for all Tracking and Planning artifacts that belong to the project area, so that LQE or any other consumer can consume the events. When you restore a previously archived project area, creation events are published to the TRS Feed.

IBM Engineering Workflow Management work item editors might not display the same tabs in the the web client on upgrade to 7.0.

First occurrence: 7.0

Problem: In versions earlier than IBM Engineering Workflow Management 7.0, work item editors with multiple tabs using the Overview layout with the same label only display the last tab with the shared label. In IBM Engineering Workflow Management 7.0, work Item editors display all tabs with unique IDs. This might result in more tabs to be visible than in previous versions.In versions earlier than IBM Engineering Workflow Management 7.0, work Item editors display all uniquely labeled Overview layout tabs, including those with duplicate tab IDs. Duplicate tabs can be added to the same editor via "Reuse Existing Tab".In 7.0, IBM Engineering Workflow Management, Work Item editors display all tabs with unique IDs. This might result in fewer tabs to be visible than in previous versions.

Workaround: If you see unexpected tabs, modify the process configuration to remove tabs that should not be present. If you do not see expected tabs, modify the process configuration to ensure that all expected tabs have unique tab IDs.

Excluded expressions are always listed as All except business safe work types in the SAFe Program process template.

First occurrence: 6.0.3

Problem: In a project area that uses the SAFe Program process template, when you edit a plan view and select Exclude and Expression, the editor sets the expression to All except business safe work types regardless of the expression that you select.

Workaround

1. Open the project area in the IBM Engineering Workflow Management (formerly known as Rational Team Concert) client for Eclipse IDE.
2. Click the Process Configuration Source tab.
3. Change the definition of the filter, and then save the project area:

First occurrence: 6.0.6.1

Problem: This upgrade requires all existing full-text search indexes that were created in 6.0.6.1 or earlier to be rebuilt. Full-text search indexes must be rebuilt for both the CLM servers and the Rational Team Concert (now known as IBM Engineering Workflow Management) Client for Eclipse IDE.

Workaround: Typically, when you upgrade an installation by using the upgrade scripts, the full-text search indexes from the earlier installation are copied to the new installation. However, the upgrade scripts do not copy previous indexes from version 6.0.6.1 or earlier (including interim fixes). Instead, the new server automatically rebuilds the indexes in the background after you start it. Results of full-text searches might be incomplete until the reindexing operation is finished; the progress of the reindex is periodically written to the server log file. Alternatively, instead of allowing the server to rebuild full-text search indexes online, you can rebuild them manually by running the repotools-<app> -rebuildTextIndices command after the upgrade is complete, but before you start the server, where <app> is one of am, ccm, or qm. Note that reindexing might be a lengthy process and can take many hours for a large database. In the web client, a system alert in the banner states that reindexing is in progress. If you follow a manual upgrade procedure instead of running the upgrade scripts, you must ensure that the full-text indexes are not copied from the old installation to the new installation. If the new installation is configured to use the same full-text index location as the old installation (the value of the com.ibm.team.fulltext.indexLocation property in the old and new teamserver.properties file is the same absolute path name), you must either run the repotools-<app> -rebuildTextIndices command before you start the server, or delete the contents of the folder at that location before you start the server. You might want to preserve the old contents if you decide to abandon the upgrade and roll back to the previous release.If an application is clustered, the offline reindexing procedure (using repotools) or the online procedure (ensuring that the full-text index folder is empty before starting the server) must be performed on each node in the cluster.The IBM Engineering Workflow Management client for Eclipse maintains a local full-text search index for the team artifact history view. When you upgrade the IBM Engineering Workflow Management Client for Eclipse to version 6.0.6.1 or later, the full-text search index is automatically deleted, which means the artifact history is cleared and will accumulate artifacts again after the upgrade. For CLM servers, complete one of these steps:

• For online background indexing, no action is required except to ensure that the full-text index folder is empty before you start the server
• For offline indexing before you start the server, run the appropriate repotools -<app> -rebuildTextIndices command.

IBM Installation Manager does not detect Microsoft Visual Studio 2017 when it is installed

First occurrence: 6.0.4

Problem: When you install the IBM Engineering Workflow Management client for Microsoft Visual Studio IDE, an additional option for Visual Studio 2017 is available. The option is disabled if Visual Studio 2017 is not detected on the computer, or if the Visual Studio 2017 installation is corrupt. Microsoft provides a Setup API to query installed editions of Visual Studio 2017 with sample code and utilities at Microsoft/vs-setup-samples. Run the sample to determine whether your Visual Studio 2017 installation is corrupt.

IBM Installation Manager does not detect Microsoft Visual Studio 2019 when it is installed.

First occurrence: 6.0.6.1

Problem:When you install the IBM Engineering Workflow Management client for Microsoft Visual Studio IDE, an additional option for Visual Studio 2019 is available. The option is disabled if Visual Studio 2019 is not detected on the computer, or if the Visual Studio 2019 installation is corrupt. Microsoft provides a Setup API to query installed editions of Visual Studio 2019 with sample code and utilities at Microsoft/vs-setup-samples. Run the sample to determine whether your Visual Studio 2019 installation is corrupt.

Workaround: If the installation is corrupt, repair Visual Studio 2019 and ensure that it installs successfully.

1. Close IBM Installation Manager and all instances of Microsoft Visual Studio.
2. Repair Visual Studio 2019 by using the Visual Studio Installer as described in Repair Visual Studio .
3. Re-run IBM Installation Manager and confirm that the Visual Studio 2019 option is enabled.

Jazz repository login errors occur if the IBM Engineering Workflow Management Client Extension is installed after Rational Software Architect

First occurrence: 6.0.3

Problem: This issue occurs if you use IBM Installation Manager to install Rational Software Architect 9.5 or 9.6 (and possibly other versions) and then install version 6.0.3 interim fix 005 or later of the IBM Engineering Workflow Management client extension for Eclipse 4.x. After you install the client extension, you cannot log in to IBM Engineering Workflow Management server and receive a Repository Connection Failed error or errors in the Eclipse error log that begin like this:java.lang.NoClassDefFoundError: org.apache.http.impl.client.WinHttpClientsat com.ibm.team.repository.transport.client.RemoteTeamServer.isWindowsAuthAvailable(RemoteTeamServer.java:2590)at com.ibm.team.repository.client.login.AbstractLoginInfo.isWindowsAuthPossible(AbstractLoginInfo.java:31)

Workaround: This issue does not occur if you install Rational Software Architect and the IBM Engineering Workflow Management Client Extension at the same time. For new installations, use IBM Installation Manager to install both items at the same time.If you already have Rational Software Architect installed, and then install the client extension and experience this issue, start the Eclipse IDE by using the -clean option. If you use a Windows shortcut to start the IDE, add -clean to the end of the Target field in the shortcut properties. If you start the IDE by running the Eclipse executable file from a command prompt, add -clean to the command argument list. To correct the issue, start Eclipse by using the -clean option once.

Licensing errors might occur if you upgrade the Java environment or upgrade applications to version 6.0.5 or later.

First occurrence: 6.0.5

Problem: If you upgrade your version of Java to a fix pack that was built after April 2017, or you upgrade an application to version 6.0.5 or later and are using WebSphere Liberty, licensing errors might occur. The errors occur because earlier licenses were signed with the MD5 algorithm, which is now blocked by newer versions of Java.For example, the License Key Management page for Jazz Team Server might display the following error in the Description field: CRJAZ1236I A development time license is being used. Similarly, the jts.log file might display the following error: CRJAZ0965I The file was not a valid server or client access license activation key.The latest license files no longer contain the MD5 algorithm because IBM and Oracle Java introduced restrictions on JAR files that are signed with weak algorithms and keys.

Workaround: The licenses in the IBM License Key Center were updated to use a different signature algorithm.After you upgrade your server to version 6.0.5 or later, obtain the updated licenses from the IBM License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses.

1. Log in to Jazz Team Server, go to jts/admin > > Server > License Key Management and note all the licenses on the server.
2. In IBM License Key Center, under License Management, click Return Keys.
3. Click the product link that you want to return the license keys for, and then click Return.
4. After the license is returned, click Get Keys.
5. Click the product link to generate licenses for.
6. When prompted, provide the required information and click Generate.
7. Download the file that contains the new licenses.
8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.

1. Log in to Jazz Team Server, go to jts/admin > > Server > License Key Management and note all the licenses on the server.
2. In IBM License Key Center, go to View keys by host or View keys by user.
3. Enter the information about the host or the user.
4. Select the product to generate the license for.
5. Click View Licenses for Selected Product Lines.
6. Select the license and click View Details.
7. Click Download Keys.
8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.

MacOS download quarantine prevents applications from starting.

First occurrence: 6.0.x

Problem: In recent versions of MacOS, downloaded compressed files might be marked with a quarantine attribute that prevents applications in the download from running. Downloads affected by this include the ELM Web Installer for macOS; IBM Engineering Workflow Management Eclipse IDE Client, IBM Engineering Workflow Management Build system, and IBM Engineering Workflow Management SCM tools compressed downloads for macOS.The problem manifests as a failure to launch the application in the download. For example, if the ELM Web Installer is downloaded and decompressed, running the launchpad.sh script fails to start the launchpad. Similarly, for the IBM Engineering Workflow Management Eclipse IDE Client download, running open Eclipse.app fails if the quarantine attribute is present. The SCM tools applications might also exhibit failures with quarantine attributes applied. In addition to the application launch failures previously described, users might see warning dialogs indicating the application was downloaded from the Internet. With MacOS Catalina and newer versions, you might also see a dialog asking for permission for the application to access the filesystem

Workaround: Use the xattr command to workaround this issue. Run xattr -h to see usage information for this command. There are options for listing what attributes are present on a file or directory and also options to add or remove attributes.Use xattr with the -p option to print the value of a specified attribute. The following example command shows whether the quarantine attribute is applied to a compressed download. As shown in the command, the full name of the quarantine attribute is com.apple.quarantine. If the xattr -p com.apple.quarantine ELM-Web-Installer-Mac-7.0.zip attribute is applied, the example command shows a one-line encoded value. If the quarantine attribute is not applied, the command returns an error message such as: No such xattr: com.apple.quarantine. Be aware that if a compressed download has the quarantine attribute applied, and the compressed file is decompressed, macOS applies the quarantine attribute to every decompressed file. Even if you remove the quarantine attribute from the compressed file before unzipping, and the compressed file is decompressed with the quarantine attribute applied, you must remove the attribute from the whole decompressed directory structure.To remove the quarantine attribute from a downloaded compressed file before decompressed it, run the xattr command with the -d option as follows: xattr -d com.apple.quarantine ELM-Web-Installer-Mac-7.0.zip. If a quarantined compressed file has been decompressed, running xattr with the -r (for recursive) option processes a specified directory structure. For example, if the quarantined ELM Web Installer is decompressed into a directory named elm-web-installer, then the following command recursively removes the quarantine attribute from all the decompressed files: xattr -dr com.apple.quarantine elm-web-installer

Outdent cannot be used on lines that contain nested content.

First occurrence: 6.0.3

Problem: Content that is copied from external sources into the Work Item editor might contain HTML data structures that prevent the outdent functionality from being used. For example, the following data prevents outdent from being used (on "Line 1"):Line 0<br /><div style="margin-left:20px"> <div> Line 1<br /> Line 2<br /> Line 3<br /> </div></div>. You cannot remove the indention from content that is not indented relative to its parent. In the example, if you place the cursor on "Line 1", you are not allowed to use outdent because "Line 1" is not indented relative to its parent.

Workaround: There are several mechanisms that can be used to work around this issue. All of them center around modifying the content to remove the elements between the indented element and the content. Complete the following steps:

1. Place the cursor at the beginning of the line you wish to outdent.
2. Delete the indention (exact keys vary by OS).
3. Continue to format the data as needed.

The Story Points (numeric) value is always 0.

First occurrence: 6.0.4

Problem: Enumeration literal values for the Complexity attribute were modified in the SAFe 4.0 Process (Program) template; however, the calculated script that uses this attribute was not updated. As a result, the calculated value for "Story Points (numeric)" is always 0.

1. In the Eclipse client for IBM Engineering Workflow Management, open the project area.
2. Go to the Process Configuration tab.
3. Expand Project Configuration > Configuration Data > Work Items and select Attribute Customization.
4. Expand Calculated Values and select Calculated Story Points (Numeric).
5. Update the switch condition in the script to use the new values: switch (a_label) { case '1 pt': result= 1; break; case '2 pts': result= 2; break; case '3 pts': result= 3; break; case '5 pts': result= 5; break; case '8 pts': result= 8; break; case '13 pts': result= 13; break; case '20 pts': result= 20; break; case '40 pts': result= 40; break; case '100 pts': result= 100; break; }
6. Go to Project Configuration > Configuration Data > Work Items > Types and Attributes and select the Story work item type.
7. Edit the Story Points (numeric) attribute.
8. Change Calculated Value Script to None, and then change it back to Calculated Story Points (Numeric).
9. Save the project.
10. Create a new Boolean attribute or use an existing attribute for the story work item. Make the calculated value dependent on this attribute.
11. Run a query that includes all the story work items that require the "Story Points (numeric)" attribute to be updated, and include the attribute in the query results.
12. Update the attribute to true, which triggers the new script and updates the values of existing work items.

The clmhelp.war file and the updateSite.zip for release 7.0.1 are unavailable for download.

First occurrence: 7.0.1

Problem: The clmhelp.war file and the updateSite.zip file for release 7.0.2 are unavailable for download due to technical issues.

Workaround: You can install the KCCI.zip file on your intranet server to view the help locally. Click here to download the ELM702_KCCI_contents.zip file.For information about installing the KCCI.zip file, see the Installing help on an intranet server topic.

URL for work item OSLC pickers has changed.

First occurrence: 6.0.4

Problem: In version 6.0.4 and later, the URL for the work item OSLC picker uses pickers instead of _ajax-modules.The following example shows the new URL format: https://jazz.net/jazz/pickers/com.ibm.team.workitem.WIPicker?projectAreaId=_1w8aQEmJEduIY7C8B09Hyw&showLoginLink=true&allowsMultiple=true. The following example shows the previous URL format:https://jazz.net/jazz/_ajax-modules/com.ibm.team.workitem.WIPicker?projectAreaId=_1w8aQEmJEduIY7C8B09Hyw&showLoginLink=true&allowsMultiple=true. The previous format for URLs does not work with the picker dialog boxes.

Workaround: If you use a whitelist, change the URLs by replacing _ajax-modules with pickers.

Windows 10 security feature causes slow startup and runtime for Eclipse applications.

First occurrence: 6.0.x

Problem: Eclipse based applications running on Windows 10 might start and run slowly, due to default security configuration. This applies to the ELM Web Installer launchpad, IBM Engineering Workflow Management client downloads and installs, the Jazz server, and any other Jazz applications that are based on Eclipse.

Workaround: This issue can be worked around by creating a security exclusion for the folder containing the Eclipse application. For information about creating the security exclusion, go to the Microsoft support website, complete the following steps.

1. Open Start > Settings > Update & Security > > Windows Security > Virus & threat protection.
2. On the Virus and Threat protection page, under Virus & threat protection settings, click Manage settings. Then, find exclusions and click Add or remove exclusions.
3. On the Exclusions page, click Add an exclusion and select Folder as the exclusion type. Then, navigate to the top-level folder of the Jazz download or install and select it.

Windows 10 updates break IBM Engineering Workflow Management Shell Control Panel functionality.

First occurrence: 6.0.4

Problem: When you start the IBM Engineering Workflow Management Shell Control Panel by clicking the Start menu or the taskbar icon, you see a duplicate taskbar icon. Also, operations that you perform in the Control Panel such as switching modes, connecting to a repository, setting up a sandbox, or changing preferences, are not applied to other File Explorer windows. Each taskbar icon can display a different set of menu items based on the operations that you perform in the Control Panel. The Windows 10 updates that were released in October 2020 cause the Control Panel to open in a different explorer.exe process. IBM Engineering Workflow Management Shell does not support a configuration where multiple Windows Explorer processes are running at the same time. In version 6.0.3 or earlier, IBM Engineering Workflow Management Shell resides on the desktop and not in the control panel, and hence, is not affected by Windows 10 updates.

Workaround: Complete the following steps:

1. Create a folder and change its attribute to read-only.
2. Rename the folder to IBM IBM Engineering Workflow Management Shell.{1632EAAE-5B6A-4861-AE2E-90BA389AF9BC}.
3. Open the folder to ensure that it displays the IBM Engineering Workflow Management Shell Control Panel.
   Note: Opening this folder does not start a new Explorer process.
4. Pin the folder to the Start menu or taskbar or create its shortcut on the desktop.
5. Click the folder icon that is pinned to the taskbar or double-click the shortcut icon on the desktop to start the IBM Engineering Workflow Management Shell Control Panel.
   Note: To open the IBM Engineering Workflow Management Shell Control Panel, use the new icon that you created instead of the default shortcut icon.

An error is shown when performing Git commit operation if you are using post receive hooks

First occurrence: 7.0.2

Problem: In GitLab 15.3.1, when post-receive hooks are configured for linking work items to Git commits and you perform the push operation through the Git CLI client, an error “128: Author identity unknown” is shown. However, the Git push is successful and the work item is updated with a link to the Git commit.

Connecting to IBM Bluemix DevOps Services projects is no longer supported

First occurrence: 6.0.5

Problem: In previous releases, you could connect from the IBM Engineering Workflow Management client for Eclipse IDE and the IBM Engineering Workflow Management client for Microsoft Visual Studio IDE to IBM Bluemix DevOps Services projects. You can no longer connect to IBM Bluemix DevOps Services projects from those clients. DevOps Services at hub.jazz.net is retired.

Context-sensitive help for VSTest does not load in the Eclipse client for IBM Engineering Workflow Management

First occurrence: 7.0.1

Problem: When you open Dynamic Help for the VSTest configuration in the Build Definition Editor, the correspondinghelp topic is not displayed. Instead, the Build Definition Editor help topic is displayed.

IBM Engineering Workflow Management Shell does not show the status of ignored files and folders

First occurrence: 5.0

Problem: IBM Engineering Workflow Management (formerly known as Rational Team Concert) Shell uses overlay icons to indicate the source control status of files and folders in a sandbox. However, in Windows 8.1 and 10, IBM Engineering Workflow Management does not use overlay icons to show the source control status of ignored files and folders. To view the source control status of a file or folder, right-click it; then, click Status under IBM EWM. For versions earlier than IBM Engineering Workflow Management 7.0, right-click and then, click Pending Changes Status under Rational Team Concert. If the file or folder is not ignored, and the overlay icon is not displayed, see Workaround: Overlay icons do not appear on files and folders in a sandbox in Rational Team Concert Shell to check for overlay icon issues in Rational Team Concert (now known as IBM Engineering Workflow Management) Shell. Workaround: Overlay icons do not appear on files and folders in a sandbox in Rational Team Concert Shell

Extensions should not be disabled or uninstalled from Microsoft Visual Studio 2017

First occurrence: 6.0.4

Extensions should not be disabled or uninstalled from Microsoft Visual Studio 2019.

First occurrence: 6.0.6.1

Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for IBM Engineering Lifecycle Management applications on a Windows platform

First occurrence: 6.0.5

Problem: IBM Engineering Lifecycle Management applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime.

Issues with IBM Engineering Workflow Managementon Eclipse 4.4 and 4.6

First occurrence: 6.0.6

Problem: Starting in version 6.0.6, the downloads for the Rational Team Concert (now known as IBM Engineering Workflow Management) Client for Eclipse IDE are based on Eclipse 4.4. and 4.6. The following known issues are related to these versions of Eclipse.

Common issues

• The first time that you open the IBM Engineering Workflow Management Client for Eclipse 4.4 IDE, the initialization process might take longer than with other Eclipse versions, and you might receive an Application is not responding message. In this case, wait for IBM Engineering Workflow Management to initialize.
• The product Welcome might include visual issues and inconsistencies. For example, icons might not be visible and icon tool tips might be incorrect.
• The Eclipse error log might show errors after the IBM Engineering Workflow Management for Eclipse IDE opens for the first time, but which do not affect performance.

Linux-specific issues

• Linux systems can be difficult to configure for Eclipse because specific versions of support libraries are required, and Linux systems might not include these libraries or might have unsupported versions installed by default. For helpful configuration information about the Eclipse Standard Widget Toolkit, see The SWT FAQ. Specifically, see the GTK, WebKit, and XULRunner sections. For tips on avoiding specific issues, see Workaround: Running the Rational Team Concert Eclipse client on 64-bit Linux.
• Eclipse performance on Linux platforms in GUI mode is more reliable with desktop environments such as GNOME and Unity instead of others such as KDE. See the related Installation Manager support article: IBM Installation Manager on Linux platforms in GUI mode requires the GNOME desktop environment. If you experience setup or configuration issues, switching the desktop environment might help.
• To avoid windowing system errors and crashes on Ubuntu 16.04 LTS systems, and other systems, start from the command line with the following sequence: export SWT_GTK3=0 ./eclipse

Mac-specific issues

• Downloads of the IBM Engineering Workflow Management client on macOS are initially in an untrusted (quarantined) state. To remove the quarantine flags, use the xattr command. For details, see Eclipse application might not start from the Finder on macOS when using the Rational Team Concert Eclipse 4.2 Client .zip download.
• To avoid the display issues described in Work Item 453595 and Work Item 454389, open IBM Engineering Workflow Management by running the eclipse.sh script from a terminal command line prompt: ./eclipse.sh. You can also customize this script to edit the configuration parameters for starting Eclipse.
• The Eclipse error log on macOS might include errors about a bundle or extension named com.ibm.cds which cannot be found. You can ignore this error, or prevent it by editing the config.ini file.

Queries return wrong results for medium HTML type attribute when bold or italics is applied

First occurrence: 4.0.4

Problem: A work item query with a condition set for any medium HTML type attribute does not return work items if the attribute value contains HTML tags (such as bold or italics) within the otherwise matching value. A work item query with a condition set for the HTML attribute, in this case, summary, returns only the work item with summary "test example". The query does not return the work items with summary "test example partial" or "test example" because in both the cases, the HTML tags are within the matching value. You can use the full-text condition to find such work items. However, full-text condition looks for occurrence in not only the specific attribute but all attributes that support full-text search. Hence, it can include more matching results than expected.Image of query with full text condition.