| Description | |
|---|---|
| Client for Microsoft Visual Studio |
Integrated web-based work item editor By default, work items now open in an integrated web-based editor in the Rational Team Concert Client for Microsoft Visual Studio. Unlike a browser, this web-based editor better integrates and interacts with the other views in the client. With this editor, you can run client-side validations for work item attributes within the Visual Studio client. The editor also honors script-based dependencies between work item attributes. The Visual Studio client can also access any new features that are added to the web client. Also, any transformations that the web client undergoes in future releases will be automatically available in Visual Studio. Image of the new work item editor:  The web-based editor integrates well with the rest of the rich client. For example, the editor can signal when a work item is modified, save all modified work items, set a work item as current, and work with change sets linked to the work item. You can multiple-select change sets and accept, explore, or locate them just like you can from the native editor. Image of how to open all related changes in the Change Summary view:  The default editor for work items in the Visual Studio client is now the integrated web-based editor. To use the native editor instead, you must clear the Open work items in the web editor by default check box. Image of the Open work items in the web editor by default check box: 
|
| Client for Microsoft Visual Studio |
Link SCM-controlled files to other CLM artifacts for traceability You can now create links between SCM-controlled files in Rational Team Concert and other Collaborative Lifecycle Management (CLM) artifacts, such as requirements in Rational DOORS Next Generation, test scripts in Rational Quality Manager, or other SCM-controlled files to provide full traceability from user requirements to implementation to test results. For more information, see Linking Rational Team Concert source control files to CLM artifacts. To follow links from an SCM-controlled file to another artifact, you must select a global configuration as the context for the operation. The global configuration helps specify the version and configuration for the CLM artifacts, which might have multiple versions and be used in different configurations. For example, a user requirement might be changed for different releases or variants of a product. To find the corresponding requirement from a source file, you must specify the configuration in which the source file and the requirement are used. For more information, see the OSLC Linked Data Platform design document. For details, also see Work Item 398844. |
| Client for Microsoft Visual Studio |
More rich-text features are available in the native work item editor The native work item editor in the Client for Microsoft Visual Studio now includes an extended set of rich-text capabilities. By default, the Description field includes these capabilities, and you can add other, customized rich-text fields by using the HTML presentation type. The rich-text support in the native editor in the Visual Studio client is the same as for the Eclipse and web clients. For details about these features see Work Item 399495. Image of the native rich-text editor in Visual Studio:  The default editor for work items in the Visual Studio client is now the integrated web-based editor. To use the native editor instead, you must clear the Open work items in the web editor by default check box. Image of the Open work items in the web editor by default check box: 
|
| Enterprise extensions |
Build HFS files on z/OS The dependency build for z/OS supports building HFS files in USS. To build HFS files, you must provide an Ant build script that performs the build. The Ant script is associated with a top-level folder in one of your projects, and the dependency build runs the script any time that the folder or files within the folder are modified. In the build definition editor, you must enable the option that turns on HFS in the preprocessor. Specify the base directory where your script creates the output. This directory should be located outside the load directory. Image of the build definition "z/OS Dependency Build" page:  When you associate a language definition with an HFS folder, the language definition must contain a translator whose call method is "Ant build file". Image of the translator editor call method:  This type of translator allows you to specify the output that your build produces. If an output is only produced during certain conditions, you can specify the name of the property that controls when it is relevant. Image of the translator editor output section:  HFS output is included in promotions and deployments. No extra configuration is required for promotion, but packaging and deployment require that you specify the base directory for the HFS output. Image of the package definition output text field:  When you create a ship list package, you can manually specify HFS-type output that you want included. Image of the package definition ship list filters:  Image of the package definition ship list add dialog box:  For more information, see Building USS files. |
| Git integration |
Improved Git repository registration page The Git repository registration page was improved and you can now perform all registration-related activities on a single page. Image of the new Git repository registration page: 250877 |
| Jazz build |
Import and export build engine definitions and build definitions In Rational Team Concert and the Rational Team Concert Enterprise Extension editions, you can now import, export, update, and delete build engine definitions and build definitions. For more information, see Build Definition Ant Tasks. |
| Jazz source control |
Link SCM-controlled files to other CLM artifacts for traceability You can now create links between SCM-controlled files in Rational Team Concert and other Collaborative Lifecycle Management (CLM) artifacts, such as requirements in Rational DOORS Next Generation, test scripts in Rational Quality Manager, or other SCM-controlled files to provide full traceability from user requirements to implementation to test results. For more details, see Linking Rational Team Concert source control files to CLM artifacts. To follow links from an SCM-controlled file to another artifact, you must select a global configuration as the context for the operation. The global configuration helps specify the version and configuration for the CLM artifacts, which might have multiple versions and be used in different configurations. For example, a user requirement might be changed for different releases or variants of a product. To find the corresponding requirement from a source file, you must specify the configuration in which the source file and the requirement are used. For more details, see the OSLC Linked Data Platform design document. You can add a link to a file, remove links, and display links. Image of the Add Related Artifacts menu item:  Note: Different types of artifacts might show different views and each application might have different ways to find the related links. Select the correct global configuration to perform link operations For the links to work properly, the global configuration must contain configurations with both source and target artifacts. Image of an example global configuration:  In the example, in the “My GC” configuration, there are four configuration members: a “JKE Banking (Quality Management) Stream” (contains JKE banking project test cases), a “JKE Banking (Requirement Management) Stream” (contains JKE banking project requirements), a “JKE Banking Integration Stream” (contains JKE banking project source files), and “My Test Stream” (for experimental code). In this global configuration, you can follow links between artifacts that are included in any of those four configuration streams. |
| Jazz source control |
Search for baselines In Rational Team Concert, you can now search for baselines in the Eclipse client, web client, Visual Studio client, and the Jazz SCM command line interface. You can use this feature to search for baselines by component, baseline name, creator, and creation date. Eclipse client Image of the Search > Jazz Source Control > Baselines menu item:  Image of the Search for Baselines dialog box:  Image of search results:  Visual Studio client Image of the Team Concert > Search > Baselines menu item:  Image of the Search for Baselines dialog box:  Image of search results:  SCM web UI Image of the Source Control > Advanced Search page:  Image of search results:  SCM CLI Images of the help for List Baseline:   Image of List baseline results: 
|
| Tracking and planning |
Configure planning attributes in the web client The Rational Team Concert web client now supports configuring planning attributes on the Process Administration page. Previously, configuring plan attributes and customizing plan views and types was possible only in the Eclipse client. In this release, you can also configure planning attributes from the web client. The web client currently supports the following configurations: • Estimate Attributes: Choose how to track progress on work items. • Currency: Set financial data. • Time Tracking: Modify the time-tracking configuration. • Work Environment: Specify project-wide settings of the work environment, including work hours. • Work Item Type Categorization: Configure plan items from work item types. • Attribute Mapping: Configure a work item attribute as a plan attribute. • Complexity: Select an attribute to express the complexity of a top-level work item. • Activate blocked cards on Kanban and Taskboard views: Mark cards as blocked. • Backlog Iteration: Set a backlog iteration for a timeline. In addition, you can also remove a plan view, customize a plan type definition, and refine and create group modes, filters, and sort modes. Note: The configuration to promote plan views is available only in the Eclipse client. You can configure all other planning attributes in the web client. Image of the Planning - General page:  Image of the Planning - Plan Types and Views page: 
|
| Tracking and planning |
More rich-text features are available in HTML fields Work items in both the web client and rich clients now include an extended set of rich-text capabilities for HTML fields. By default, the Description field includes these capabilities, and you can add other, customized rich-text fields by using the HTML presentation type. The following extended rich-text features are now available: • Ordered lists • Unordered lists • Underline • Strikethrough • Font family • Font Size • Text color • Highlighting • Horizontal Rule • Remove styling • Indent/Outdent Image of the extended rich-text features for HTML fields: 
|
| Tracking and planning |
New SAFe 4.0 process templates are available New predefined process templates are available that support Scaled Agile Framework (SAFe) 4.0 Portfolio and Program. These process templates provide SAFe Portfolio/Value Stream and Program/Team Rational Team Concert project areas with default support for the typical artifacts and activities, including Kanban planning and economic prioritization by using Weighted Shortest Job First (WSJF). For more information, see Enterprise Scaled Agile Framework on Jazz.net. |