Workarounds and Limitations: Known issues in IBM Engineering Workflow Management 7.0

Engineering Workflow Management (EWM) 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 EWM 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 EWM 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 EWM 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, EWM, Work Item editors display all tabs with unique IDs. This might result in fewer tabs to be visible than in previous versions.

Workaround
Users seeing unexpected tabs need to modify the process configuration to remove tabs that should not be present.
Users not seeing expected tabs need to modify the process configuration to ensure that all expected tabs have unique tab IDs.

Related information
Work Item 491010
Customizing the work item editor in the web client
Work item editor presentations

Full-text search indexes must be rebuilt when you upgrade to 7.0 or later

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 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 Rational Team Concert (now known as Engineering Workflow Management) Client for Eclipse maintains a local full-text search index for the Team Artifact History view. When you upgrade the Rational Team Concert (now known as 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.

Related information
Work Item 467854

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 (formerly known as Rational Team Concert) 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 Engineering Workflow Management (formerly known as Rational Team Concert) client, the integration is not available on the newly installed instances of Microsoft Visual Studio 2019.

Workaround
Re-install the Engineering Workflow Management (formerly known as Rational Team Concert) client for Microsoft Visual Studio IDE by completing the following steps:

1. In IBM Installation Manager, select the Modify option, deselect Visual Studio 2019, and then finish the installation.
2. In IBM Installation Manager, select the Modify option, select Visual Studio 2019, and then finish the installation.

This process installs the Engineering Workflow Management (formerly known as Rational Team Concert) client on all installed instances of Microsoft Visual Studio 2019.

Related Information
Work Item 416095

Code review page fails to render in the embedded browser in the RTC client for Microsoft Visual Studio

First occurrence
6.0.6.1

Problem
Rational Team Concert (now known as Engineering Workflow Management) client for Microsoft Visual Studio IDE, uses Internet Explorer (IE) 11 running in IE 9 compatibility mode as the embedded browser instance. The Open Code Review button in the work item editor opens a web page that uses the Orion JavaScript library to render the code review compare page. The Orion library needs IE 11 mode, and it does not support IE 9 compatibility mode. Hence, the code review page opens in the embedded browser but does not render the UI and the page is blank.

Workaround
To use the external browser, complete the following steps:

1. Go to the Debug > Options menu.
2. In the Options preference dialog, search for Team Concert.
3. From the Team Concert child preferences list, select Web browser.
4. Select Use External Web Browser and click OK.

Related information
Work item 533102
 

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 Rational Team Concert (now known as 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.

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 the Rational Team Concert (now known as 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.

Related information
Work Item 450401

Colors and gradients are missing or incorrect in versions of Eclipse 4.7

First occurrence
6.0.5

Problem
If you use Rational Team Concert (now known as Engineering Workflow Management) P2 and any version of Eclipse 4.7, some colors and gradients might be missing or incorrect. For example, if you hover over the work item ID, the ID might be grayed out and unreadable. In other instances, an additional or unexpected color might be displayed.

These issues are caused by a problem with theme settings in Eclipse. In versions of Eclipse 4.5, the default theme is Windows. In versions of Eclipse 4.7, the default theme is Light. These issues do not occur in versions later than Eclipse 4.7, which have the default theme Windows Classic.

Workaround
In any version of Eclipse 4.7, change the theme from Light to Windows Classic:

1. In Eclipse, select Windows > Preferences > Search for Theme > Select Appearance.
2. On the Appearance tab, set the theme to Windows Classic.

Related information
Work Item 443424

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.

Important: If you are not upgrading all applications at the same time, you must apply an interim fix to the applications at earlier versions before you upgrade Jazz Team Server. The following interim fixes contain the compatible version of Java:

• 6.0.4 interim fix 007 and later
• 6.0.3 interim fix 010 and later
• 6.0.2 interim fix 015 and later
• No version of 5.0.2 contains a compatible Java version. For 5.0.2, complete the steps in the IBM Support flash article.

If you cannot apply the interim fix before the upgrade, upgrade Jazz Team Server and then complete the steps in the IBM Support flash article. If you do not apply the interim fix or complete the steps in the article, the internal licenses do not load on Jazz Team Server and the applications might experience issues.

To update your current license files, follow the instructions in the Interactive Upgrade Guide or complete the following steps based on the type of license:

For term (floating or authorized user) or token licenses:

Note: For token licenses, you are only required to download the jazztokens.zip file. You do not have to download the license.dat file because it does not contain changes.

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.

For non-term floating and authorized user 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, 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.

Note: If you imported trial licenses before the newer versions of Java were adopted, you might still receive errors in the jts.log file even after you import the updated licenses. For example, you might receive this error: CRJAZ0965I The file was not a valid server or client access license activation key. You can ignore these errors.

Related information
IBM License Key Center
Interactive Upgrade Guide
Oracle release note: Restrict JARs signed with weak algorithms and keys

On case-insensitive macOS systems, existing SCM sandboxes must be repaired before use in 6.0.5 and later

First occurrence
6.0.5

Problem
Rational Team Concert (now known as Engineering Workflow Management) 6.0.5 fixed several defects that affected source control management (SCM) operations on macOS systems. In previous releases, Rational Team Concert (now known as Engineering Workflow Management) SCM operations treated all macOS file systems as case-sensitive, which caused problems because macOS systems can be case-insensitive. For details, see Work Item 416705, Work Item 417531, and Work Item 417542.

If you have sandboxes that were created before 6.0.5 on a case-insensitive macOS system, you must repair the metadata for those sandboxes. Otherwise, a warning is displayed when you start the client that prompts you to repair the metadata. If you use the client without repairing the metadata, you might see unresolved changes when there are none for files and directories whose names contain uppercase letters. Additionally, you will not be able to unload a repository workspace whose name contains uppercase letters.

Sandboxes on case-sensitive macOS systems are not affected and do not require their metadata to be repaired.

Workaround
In Rational Team Concert 6.0.5 and later, repair the metadata for existing sandboxes by using any of the following methods:

• In the warning that opens when you start the client, click the Repair Now button.
• Enter this command: scm repair -d sandbox-path
• In the client for Eclipse IDE, click Window > Preferences > Team > Jazz Source Control > Repair Metadata.

The metadata repair operation might take a long time to complete. An alternative to repairing the metadata is to create a new sandbox.

Related Information
Work Item 447226

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 (formerly known as Rational Team Concert) 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 Engineering Workflow Management (formerly known as Rational Team Concert)  client, the integration is not available on the newly installed instances of Microsoft Visual Studio 2017.

Workaround
Re-install the Engineering Workflow Management (formerly known as Rational Team Concert) client for Microsoft Visual Studio IDE by completing the following steps:

1. In IBM Installation Manager, select the Modify option, deselect Visual Studio 2017, and then finish the installation.
2. In IBM Installation Manager, select the Modify option, select Visual Studio 2017, and then finish the installation.

This process installs the Engineering Workflow Management (formerly known as Rational Team Concert) client on all installed instances of Microsoft Visual Studio 2017.

Related Information
Work Item 416095

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.

Related information
Work Item 419973

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 Rational Team Concert (now known as 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.

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

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

Related information
Work Item 416092

The “Story Points (numeric)” value is always 0

First occurrence
6.0.4

Problem
As part of the fix for Work Item 405355, 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.

Workaround
Complete these steps:

1. In the Eclipse client for Engineering Workflow Management (formerly known as Rational Team Concert), 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.

Note: The script-based calculated values are not designed to detect updates to the script itself. If a dependent attribute is changed, in this case Story Points, it triggers the script execution.

Related information
Work Item 433587

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

First occurrence
6.0.3

Problem
When the 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-0

On Linux systems that use RPM to install software, such as Red Hat, download webkitgtk-2.4.9-1.el7.x86_64.rpm and run the following command to install it:

sudo rpm -ihv webkitgtk-2.4.9-1.el7.x86_64.rpm

Related information
Work Item 425554
Stack overflow: swt browser No more handles Error

Jazz repository login errors occur if the 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 Rational Team Concert (now known as Engineering Workflow Management) Client Extension for Eclipse 4.x. After you install the client extension, you cannot log in to the Rational Team Concert (now known as 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.WinHttpClients
at 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 Rational Team Concert (now known as 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, you should only have to start Eclipse by using the -clean option once.

Related information
Work Item 416596

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 it’s 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 it’s 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.

Related information
CKEditor Issue 3899

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 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:

Related information
Work Item 441262

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; EWM Eclipse IDE Client, EWM Build system, and EWM 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. Image: 304336.Similarly, for the EWM Eclipse IDE Client download, running open Eclipse.app fails if the quarantine attribute is present.
[Image: 304200]

The SCM tools applications might also exhibit failures with quarantine attributes applied.
[Image: 304334]

In addition to the application launch failures previously described, users might see warning dialogs indicating the application was downloaded from the Internet [Images: 304198 and 304199]. With macOS Catalina and newer versions, users might also see a dialog asking for permission for the application to access the filesystem.
[Image: 304195]

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.  Note: As shown in the command, the full name of the quarantine attribute is “com.apple.quarantine”.

xattr -p com.apple.quarantine ELM-Web-Installer-Mac-7.0.zip

If the quarantine 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”.
[Image: 304190]

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

[The use of xattr is shown in image 304193.]

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


Related information
Work Item 497806
https://jazz.net/library/article/1567

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, EWM 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.

Summarizing the steps here:

1. Open Start -> Settings > Update & Security > Windows Security > Virus & threat protection.
2. On the Virus & 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.

Related information
https://bugs.eclipse.org/bugs/show_bug.cgi?id=548443
https://www.eclipse.org/eclipse/news/4.14/
Technote for win-10 slow startup workaround (485785)

Known issues in translated versions of ELM 7.0 documentation

First occurrence
7.0

Problem

1. The table of contents for ELM 7.0 documentation on IBM Knowledge Center (KC) might display long navigation titles in place of short titles for content in languages other than English.
2. The pre-release header is visible on the translated pages of ELM documentation on IBM KC.

Related information

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

First occurrence
6.0.6.1

Problem
When you install IBM Engineering Workflow Management (formerly Rational Team Concert) into Microsoft Visual Studio 2019, the Engineering Workflow Management extensions are listed under Tools > Extensions and Updates. Do not disable or uninstall the Engineering Workflow Management extensions from within Visual Studio 2019. To install or uninstall the Engineering Workflow Management client for Microsoft Visual Studio IDE, use only IBM Installation Manager.

Related Information
Work Item 417681

Known issues for Engineering Workflow Management

on 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 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 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 Engineering Workflow Management to initialize. For details, see Work Item 456354.
• The product Welcome might include visual issues and inconsistencies. For example, icons might not be visible and icon tool tips might be incorrect. For details, see Work Item 402442 and Work Item 432353.
• The Eclipse error log might show errors after the Engineering Workflow Management for Eclipse IDE opens for the first time, but which do not affect performance. For details, see Work Item 414649.

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 and Work Item 456519.
• 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. For details, see Work Item 454223.
• 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:

Mac-specific issues

• Downloads of the 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 Engineering Workflow Management by running the eclipse.sh script from a terminal command line prompt:

• 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 as described in Work Item 454631.

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 Rational Team Concert (now known as Engineering Workflow Management) client for Eclipse IDE and the Rational Team Concert (now known as 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.

Related information
Work item 433977
Work item 433975

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 (formerly known as Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM)) 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.

Related information
Work Item 455371
Work Item 452307
APAR IJ04429

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

First occurrence
6.0.4

Problem
When you install IBM Engineering Workflow Management (formerly known as Rational Team Concert) into Microsoft Visual Studio 2017, the Engineering Workflow Management extensions are listed under Tools > Extensions and Updates. Do not disable or uninstall the Engineering Workflow Management extensions from within Visual Studio 2017. To install or uninstall the Engineering Workflow Management client for Microsoft Visual Studio IDE, use only IBM Installation Manager.

Related Information
Work Item 417681

Engineering Workflow Management

Shell does not show the status of ignored files and folders
First occurrence
5.0

Problem
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, 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 IBM EWM > Status (for versions earlier than EWM 7.0, right-click and then, click Rational Team Concert > Pending Changes Status). 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 Engineering Workflow Management) Shell.

Related information
Work Item 371097
Workaround: Overlay icons do not appear on files and folders in a sandbox in Rational Team Concert Shell

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.

For example, consider work items with the following summary:
– test example partial: Defect 1.png (293400)
– test example: Defect 2.png (293399)
– test example: Defect 3.png (293398)

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.
Image of query: Summary query condition.png (293396)

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: Full text query condition.png (293397)

Related information
Work item 296090