December 5, 2014
Rational Team Concert
Task tracking · Source control · Agile planning
Rational Team Concert 4.0 M7 Milestone
Rational Team Concert 4.0 M7 New and Noteworthy
Rational Team Concert, Rational Quality Manager, and Rational Requirements Composer share a common set of server applications with each product offering role-based licenses that permit access to different capabilities provided by the applications. Therefore you should also read the New & Noteworthy page for Jazz Foundation 4.0 M7 and unless you elect to not install the Quality Management and the Requirements Management applications, you should also read the pages for Rational Quality Manager 4.0 M7 and Rational Requirements Composer 4.0 M7.
Table of contents
- Jazz source control
- Work items
- Rational Team Concert ClearQuest Synchronizer
- Rational Team Concert Shell
- Client for Microsoft Visual Studio IDE
- ISPF client
- Dependency build and promotion
- User assistance
Jazz source control
File and folder read permission (Eclipse Client)
Read permissions on files and folders are inherited from their components. You can further scope read permissions of a file or folder by opening the Repository File View, right-clicking the file or folder, and clicking Change Access Control.
In the V4.0 release, you can use the Access Control window to control the read access of files and folders in three ways:
- To allow anyone who has access to the parent component to retrieve the selected file or folder, select Public.
- To limit the access to yourself, select Private.
- To specify which project area or team area to use to control access to files and folders, select Scoped.
These permissions apply to the selected items in the component throughout the entire repository. The permissions also apply to any workspace, stream, snapshot, or baseline that include the component. The permissions apply to every state of the selected files or folders. Previous versions of any workspace, stream, or snapshot are protected by the same permissions.
Check-in history (web client)
In the web client, you can access the check-in history of any change in a change set. The check-in history is useful if you checked in an invalid change and want to reload the content that was checked-in in that same change set. In the following example, four versions of the mathResearch.txt file were checked in into this change set before it was delivered.
Auto-detection of changes made outside of Eclipse (Windows operating system only, Eclipse Client)If you enable this new option, the Eclipse client automatically detects changes that external tools made. The changes are shown in the Pending Changes view. You can also use this option for external sandboxes, even when the files are not shown in the Eclipse workspace.
Validating delivery by using work item queries
You can use the new Require Work Items to Match Query advisor to use a work item query to validate work items during delivery. You can prevent change sets that are associated with work items and that fail to meet a query from being delivered to a stream.
Improved Auto-Resolve for add/add conflicts
You can auto-resolve conflicts that arise when you and another user add a folder with the same name. The auto-resolve merges as much of the file hierarchy as possible.
Testing of HTTP value set providers
Configuring HTTP value set providers is a complicated task. A complex XPath expression, the wrong login credentials, or invalid URLs can make it difficult to fetch and extract the correct data from a server. If an error occurs, it can be difficult to find the problematic configuration.
In a new test window, you can validate your HTTP value set provider while you configure it. You can retrieve values from the server, filter the values, and validate the results. Moreover, the entire communication to the server is recorded. You can inspect detailed information about all HTTP requests and responses.
A new attribute-type enumeration list represents collections of enumeration values. You can use the list to select any combination of different enumerations. You can configure a new editor to display the attributes of that new type. Support for queries and printing has also been added.
The new attribute-type enumeration list replaces the multi-list presentation.
You can use the Report viewlet to select, configure, and view results for any report resource on the server.
You can also change the report type of any pre-configured Trend Report viewlet on demand.
Rational Team Concert ClearQuest Synchronizer
Sychronizer to Bridge Transition Tool
In V4.0, the RTC-ClearQuest synchronizer component includes new standalone Java application: the syncToBridge tool. With this tool, RTC-ClearQuest customers can automate the transition transition from the synchronizer to the OSLC-based ClearQuest-RTC bridge integration.
For more details about the syncToBridge tool, see this help topic:
For more details about the ClearQuest-RTC Bridge, see these help topics:
- Configuring and using integrations for Collaborative Lifecycle Management
- Configuring and using the Rational® ClearQuest Bridge
Rational Team Concert Shell
With Rational Team Concert Shell, you can perform source control on files and folders from Microsoft Windows Explorer.
Rational Team Concert Shell includes a control panel, a set of context menus for files and folders that is specific to Rational Team Concert, and a Pending Changes view. You can use the Control Panel to manage Jazz artifacts and preferences. From the context menus, you can perform source control operations on files and folders. The Pending Changes view provides more sophisticated source control, where you can work with change sets and perform advanced operations on work items.
Rational Team Concert Shell control panel
You can use the Rational Team Concert Shell control panel to get started. You can accept a team invitation, share sources, or load a repository workspace, and tailor your environment by specifying preferences. The control panel includes help for ease of use. You can start the control panel from the Start menu, the Rational Team Concert icon on the task tray, or the desktop.
Source control for files and folders
The Rational Team Concert Shell includes a context menu named Rational Team Concert. From this context menu, you can do various source control operations on files and folders, such as share and disconnect, check in and deliver, associate a work item, lock and unlock, and ignore and remove from the ignore list.
Files and folders that are under source control have visual cues. For example, shared files and folders are marked with orange cylinders. Local unresolved files and folders are marked with yellow squares. Arrows indicate incoming and outgoing changes.
Pending Changes view
If you want more control over source control operations, you can use the Pending Changes view, which is integrated into Windows Explorer. In the Pending Changes view, you can do advanced source control operations, such as discarding and suspending change sets, and submitting change sets for review.
Client for Microsoft Visual Studio IDE
Symbolic link support
You can now load and share symbolic links by using Rational Team Concert Client for Visual Studio IDE. Many SCM operations are supported, such as check-in, deliver, undo, compare, move, and rename. You can choose to receive a prompt if a broken link is checked-in.
If you have JazzAdmin permissions, you can delete a file state from the repository. However, you cannot recover a deleted state.
In the History view, you can browse through the intermediate states of a change set. You can select any intermediate state and delete it from the repository.
The load wizard provides the option to load by using a load rule file, which makes the process more flexible. Load rules are a collection of rules that are used to decide what repository items are loaded into a sandbox.
You can generate load rule files for a loaded workspace. You can easily share rules or communicate load rules to other users and processes, such as build scripts. When you generate load rules, you can rename each load rule file that you create and select where to save the file.
Filter Pending Changes view
You can now apply filters in the Pending Changes view to filter components from the view. You might want to filter components from the view when many components are in the view and you want to see only certain components.
Locating change sets
In Rational Team Concert for Visual Studio Client, you can determine which workspaces or streams contain a change set or set of change sets.
In the context menus of change sets and work items, you can select Locate change set. The editor shows the work item and its associated change sets in the source area. You can select the stream, workspace, or baseline in the target area.
You can also drag work items onto the source area, and drop a repository, a project area, streams, workspaces, and baselines onto the target area. However, if you drop a project area or repository, all of the associated streams and workspaces are added to the target area. Adding a project area or repository can be time-consuming if the project or repository contains a large number of streams or workspaces.
To show the search results for a target item in a separate result view, click Show Result Details.
Variables in work item queries
The Rational Team Concert for Visual Studio Client now supports creating and running queries with variables. When creating or editing a query, the user can specify that values are to be provided when the query is executed by selecting the "provide condition values by parameter" icon in the top right corner of the condition area in the query editor. When executing the parameterized query, for example, by selecting "Show Work Items" from the query menu for the parameterized query, an input wizard will be displayed, allowing you to provide values for the query parameters.
Overriding the Include and Exclude ship lists and container mapping
In the Create Package wizard, you can override the Include and Exclude ship lists that are defined in the package definition. You can also override the container mapping. Any changes will affect only the package that is being created.
Deployed and packaged objects are listed in deployment and packaging summary work items
The summary work item that is created during a deployment or packaging contains a list of all of the outputs that were deployed or packaged. The list also contains the name of the host and the package directory.
Show all packages
You can view a list of all of the packages by right- clicking a package definition and selecting Show All Packages. You can then double-click any column to open the artifact for that column. To open an HTML report about the package, double-click the Package Label column.
Querying deployed packages
You query for deployed packages by right-clicking a deployment definition and selecting Query Deployed Packages. You can then specify a deployment definition, package definition, build agent, a specific package, or several of those items. If you specify the deployment definition, package definition, and build agent, you can see all of the packages that are deployed to the machine that is running that build agent. To see which machines a package is deployed to, leave all of the fields blank except for the Packages field, and in that field, enter the specific package that you are interested in.
Deploying packages from the Builds view
When you view the results of a package definition in the Builds view, you can right-click a result and select Load and Deploy. A window opens allowing you to specify the deployment definition to use. Then, the Request Deployment window opens and indicates the package to deploy.
When you request a deployment, you can specify that it is a personal deployment. You can also change the container mappings to deploy to your personal locations.
View and compare change set details in the ISPF client
Before this milestone release, in the ISPF client, you could view only a list of resources that were included in a specific incoming or outgoing change set. In this milestone, you can view the contents of the corresponding local file or remote file. You can also compare the two files by using the standard ISPF compare tool.
View compare and merge during conflict resolution
Before this milestone release, in the ISPF client, to resolve conflicts, you had the options to "Resolve with mine" or "Resolve with proposed." As of this milestone, you can view, compare, and merge the contents of local and remote files.
You can also save a backup version of your local file before you complete a "resolve with proposed" action.
Dependency build and promotion
Dependency build support is enhanced with the new Buildable Subset wizard. Previously, to select a subset of files to build, you had to browse through files in a repository workspace and select individual files to include in a subset. With the new wizard, you can create build subsets by using work items or rules.
IBM i LinkEdit Support
Support for SCM link files has been added. The link files are scanned and information is stored in source code data. These link files are processed at build time to resolve command arguments.
Support for IBM i commands in pre- and post-commands
In the dependency build editor, you can specify IBM i commands to run automatically before and after IBM i dependency builds.
Additional IBM i scanners
New source code data scanners were added for IBM i DDS, CL, and PF files.
Load rules for z/OS dependency builds
You have more options to load source files during a z/OS dependency build.
Cross-repository delivery with system definition ID mapping
You can use a new editor to associate remote system definition IDs with local system definitions. This association automatically resolves any system definitions during cross-repository delivery.
Source code data improvements
Source code data collection and storage are redesigned to lower the memory footprint that is required to store the source code data. The source code data can be shared between streams. Additionally, the handling of the index history of source code data is redesigned. Only the amount of history that is needed for dependency build, impact analysis, and promotion is kept.
Tooling to migrate deprecated z/OS dependency build definitions
In the Eclipse client, you can migrate dependency build defintions created with version 3 of the product to the new build template, allowing you to more easily employ the new features.syncToBridge command-line utility, see Transitioning from the ClearQuest Synchronizer to the ClearQuest Bridge.
Help for deploying a clustered environment
The following new topics describe how to configure and deploy a cluster of servers to achieve load-balancing and high availability by using WebSphere Application Server Network Deployment:
- Deploying a clustered environment by using WebSphere Application Server Network Deployment
The interactive installation guide has also been updated to include a choice for clustering:
Interactive upgrade guide updated for 4.0
The interactive upgrade guide has been updated to describe how to upgrade to the 4.0 release:
Help for setting up the server and applications via the command-line interfaceAs an alternative to using the Setup Wizard, you can now set up the Jazz Team Server and associated applications by using the command-line interface. The Running the setup with command-line commands topic describes how to do it.
Help for using Jython scripts to set up WebSphere Application Server and deploy CLM applications
See the Setup WebSphere Application Server and deploy CLM applications using Jython scripts topic for details about how to use Jython scripts to automate common administration tasks and configure security in WebSphere Application Server.
Updates to planning help
The Kanban is a plan view that gives you a quick overview of work item status, divided into columns of open, in progress, and resolved. You can set limits for each column and also drag work items to appropriate columns. See Creating plan views for details.
You can use a cross-project plan to view relationships between work items across project areas. For detaills about creating cross-project plans, see Tracking work item relationships across projects.
Updates to SCM help
The Locate change sets feature lets you determine which repository workspace or stream contains a particular change set. For details about using the Locate Change Sets editor, see the context-sensitive help and Locating change sets.
You can now permanently delete file versions from source control. See Deleting file versions from the repository for details.
You can now view the history of check-ins of a file in source control. See Viewing the change history of files for details.
Help for transitioning from the ClearQuest Synchronizer to the ClearQuest Bridge
If you use the ClearQuest Synchronizer to synchronize Rational Team Concert work items with Rational ClearQuest change requests, you can migrate the synchronized work items and change requests so that they use the ClearQuest Bridge. For details about using the new syncToBridge command-line utility, see Transitioning from the ClearQuest Synchronizer to the ClearQuest Bridge.
Help for creating and using access groups to restrict read access to work items
To restrict access to work items, you can define access groups that can consist of members of project areas, members of team areas, and specific users. You can then limit read access to specific work items to members of an access group. For details about creating and using access groups, see Using access groups to control access to work items.
Content filtering in the information center
Help content filtering is now available in the Rational solution for Collaborative Lifecycle Management 4.0 information center. By setting a filter, you customize the online help to suit your information needs. At any time, you can modify the filter to see fewer or more topics. Alternatively, you can remove the filter to see all the help topics. The filter affects the topics that are listed in both the navigation tree and the search results.
To access the filter options, click the Filter icon in the information center banner:
The filter dialog opens and you can choose to filter content by role and capability: