IBM Rational Team Concert
Task tracking · Source control · Agile planning
Rational Team Concert 4.0.3
Rational Team Concert 4.0.3 New & Noteworthy
Rational Team Concert is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM). For new and noteworthy information about other parts of the Rational solution for CLM, see these pages:
New in Rational Team Concert 4.0.3
- Eclipse client
- Tracking and planning
- Jazz source control
- Client for Microsoft Visual Studio IDE
- My Dashboard view
- My Current Work section
- My Future Work section
- Pending approvals
- Pending requests
- Configuring the predefined sections
- Event log
- Filtering sections
- Filtering support in the Change Explorer view
- Searching with the work item picker query
- Enhanced search and filtering in the Pending Changes view
- Rational Team Concert Shell
- ISPF client
- Dependency build and promotion
- ClearCase Connector
- Jazz build
- User assistance
Starting with Rational Team Concert 4.0.3, an IBM Installation Manager package is available that installs the Rational Team Concert Client for Eclipse IDE with Eclipse 4.2.2. This installation package is in addition to the original Rational Team Concert Client for Eclipse IDE installation based on Eclipse 3.6.2. You can install either Eclipse-based IDE from the web installer launchpad. In addition, the new package is available in the .zip file of the IBM Installation Manager repository. You can download the file from the IBM Installation Manager Repositories section of the All Downloads page. If you use MacOS, where no IBM Installation Manager package is provided, you can still set up a client with Eclipse 4.2.2 by downloading an Eclipse 4.2.2 classic download from eclipse.org, downloading the p2 update site .zip file from the All Downloads page, and using the Eclipse installer to install Rational Team Concert into Eclipse.
Tracking and planning
New ranking model
Initially, you could only rank items in a plan by dragging them. The new implementation model provides three additional ways to rank items:
- Apply rank action
When you perform this action, the entire plan is ranked. You must save the changes for the new ranking to persist.
- Integer-based ranking
This feature enables you to change the rank value of a plan item. After you click the rank, you can enter the new rank in the field.
The items are reordered based on the number that you enter.
Note: If you enter a number that is already associated with an item, the item replaces it with that rank, and it is positioned above that item. All ranks below the item are increased by 1.
- Context menu options
- Remove > New Rank: Removes the rank associated with the item
- Remove > New Rank Below: Removes the rank of all items below the selected item
- Apply New Rank Above: Applies ranks to all non-ranked items above the selected item
You can drag items to rank them above, between, and below other items. The item is ranked based on the destination location and predecessor item.
If the predecessor is ranked, the dragged item gets the next rank, and all subsequent item ranks are increased by 1. If the predecessor if not ranked, the dragged item loses its rank, and its secondary sort attribute is changed to that of the predecessor to maintain the ordering sequence.
Note: An exception occurs if you use a user-defined secondary sorter. In that case, the item loses its rank, but its secondary sort attribute is unchanged.
Increased hierarchy levels for cross-project plans
Initially, cross-project plans displayed a single hierarchy level. Now, they support multiple hierarchy levels for items that are tracked in the plan.
New plan checks for cross-project plans
Cross-project plans now support three new plan checks for items that are tracked in a plan.
Warnings are displayed when the following situations occur:
- The rolled-up schedule for an item in the plan exceeds the end date of the iteration that the plan is associated with.
- The "planned for" date of a plan item exceeds the plan's iteration end date.
- The rolled-up schedule for an item in the plan exceeds the due date that is specified for the item.
Date expressions for colorizers and filters
All plans now support date expressions in colorizers and filters that you can use to highlight or hide items in the plan view.
Plan performance improvements
Plan loading performance is improved by 40 to 50 percent. For example, the Rational Team Concert product backlog now loads in 10 seconds, compared to 20 seconds prior to the changes, over a network latency shown in the image below using browser Mozilla Firefox 17.0.5. In addition, plan loading performance has improved in a clustered environment. For example, the Rational Team Concert product backlog now loads in 12.2 seconds, compared to 26.6 seconds prior to the changes, over a network latency shown in the image below using browser Mozilla Firefox 17.0.5 in a clustered environment.
Create work item templates in the web client
You can now create work item templates in the web client:
- Run a query that contains all the work items to create templates of.
- In the work item query result view, on the toolbar, click Create Work Item Templates.
- Select the work items to be part of the template.
- Start the work item template wizard by clicking the Create Work Item Template button.
You can also create work items from a template from the Work Items drop-down menu, as well as in plans.
Process guidance in the work item editor
The work item editor layout can now contain in-place process guidance. This feature is enabled with a new Static Rich Text editor presentation that supports hyperlinks and renders rich hovers for any URL that honors the OSLC Preview specification. By linking to the URL of any content from your project area's process description, this content is easily available to users.
Jazz source control
Jazz properties can be edited in the Windows Explorer properties view
You can view and edit Jazz properties for files and folders that are under Jazz source control from within the Windows Explorer properties view. Jazz properties are displayed on the Jazz tab. You can use the embedded Jazz properties view to edit properties such as MIME type, delimiter, and user properties.
When you right-click a shared file or a folder and click Properties, the properties menu that is displayed has a Jazz section.
You can add custom properties to shared files and folders. These custom properties are version controlled.
List and set preferences
Preferences for the source control command line client can be retrieved or set through a commmand.
scm list preferences
scm preference get
scm preference set
> lscm list preference commit.atomic.maximum - -1 (files) content.threads - 10 dump.exception - true json.output - false log.level - SEVERE password.mask - true refresh.local.changes - true repository.timeout - 480 (seconds) trace.dir - /home/shashi/.jazz-scm trace.dir.max_size - 2000000 (bytes) trace.disable - trace.file.compress - true trace.file.max_size - 1000000 (bytes)The --verbose option shows more information when listing the perferences.
> lscm list preference -v Name : commit.atomic.maximum Description : Sets the maximum number of changes that will be committed as an atomic group. If any single file upload fails in a commit
Client for Microsoft Visual Studio IDE
My Dashboard view
The My Dashboard view in the Rational Team Concert Client for Visual Studio is redesigned in 4.0.3. The new view now has several predefined sections for your work: current work, future work, and outstanding approval requests between you and your team members. The view also has an Event Log section where you can configure your team feeds. You can configure each section to show data from one or more project areas that you are connected to.
In addition to the predefined sections, you can create query sections. Each query section can show the results of one or more queries. You can group your query results by using different group-by clauses.
My Current Work section
This section displays your current work across the current iterations for all development lines in each of the configured project areas. Work items are grouped by project areas and, optionally, by iterations within a project area.
My Future Work section
This section displays your future work across all future iterations or the backlog for all development lines in each of the configured project areas. Work items are grouped by project areas and, optionally, by iterations within a project area.
This section displays work items with that have pending approvals for you. Opening a work item displays it on the Approval tab of the work item editor.
This section displays work items that you own that have pending approvals for your team members. This section is useful if you deliver to a stream that is contingent on peer reviews and approvals.
Configuring the predefined sections
For each predefined section, you can configure one or more project areas by using the Configure option from the drop-down list. You can also decide if you want your current work items grouped by iterations.
Selecting the Configure option opens the Configure Query Section window. You can select one or more connected project areas from the dialog box. The corresponding predefined section then displays work that relates to the section across multiple project areas. When you select project areas, you can decide if you want your configuration to apply to all unconfigured predefined sections.
This section displays the event log for your teams. The event log shows the team's status in terms of work item modifications, source artifact creation or updates, build requests, and reports.
You can customize the event log to configure the projects and teams to receive notifications about, as well as the type of event.
You can also specify a rich set of filters for your event log.
User-defined query sections
You can create new sections and associate one or more queries with each of those sections.
You can select queries from multiple project areas and display them in the same section.
You can group your query results by different fields.
You can display the results as a bar chart or as a grouped list.
You can display only the sections that you are interested in at any given point in time, and filter out the rest.
Filtering support in the Change Explorer view
The Change Explorer view was enhanced to support filtering, which makes comparing two SCM items, such as streams or workspaces, easier.
Now, you can filter the view to display only the change sets that match the filter criteria. The filter text is used as an expression and can match any of the following fields:
- Change set owner name
- Change set comment
- Work items (label and summary) that are attached to the change set
- Last modified date of the change set
- File and folder names that are contained as part of the change set
Searching with the work item picker query
In previous releases of Rational Team Concert Client for Visual Studio, you could only search for a work item by using a keyword. In this release, the picker is enhanced to show the results of a query from which you can choose a work item. If you choose a query as input in the work item picker, the first 50 items that match the query are displayed in the picker.
Enhanced search and filtering in the Pending Changes view
The search and filtering options in the Pending Changes view were modified. A new filter hides the Suspended nodes in the Pending Changes view, and the search now matches the file name and the following fields:
- Change set owner name
- Change set comment
- Work items (label and summary) that are attached to the change set
- Last modified date of the change set
- File and folder names that are contained as part of the change set
Rational Team Concert Shell
Rational Team Concert Shell now has different modes of operation and is geared toward both the developer and the non-developer communities. While advanced users can still take advantage of the full capabilities of Rational Team Concert Shell, simpler usage patterns are available for users who want simple document management and version control. You can get started easily, have more guidance, and hide advanced SCM concepts that you do not need.
To customize the experience for these two user groups, Rational Team Concert Shell now provides two modes of operation: Basic mode and Advanced mode.
Basic mode is a new mode, for which you do not need to know Rational Team Concert SCM concepts, such as repository workspaces, components, or change sets. You do need to know about project areas and streams at a high level, as you work with files and folders.
In addition to providing simpler usage patterns for Basic mode, context-sensitive help is now part of the Rational Team Concert Shell user interface. The context-sensitive help guides Basic mode users during operations that require user input. In addition, messages prompt the user to take different actions based on the state of the managed files and folders. For example, messages are displayed on the taskbar to signal incoming changes, conflicts, or other situations that require the user's attention. When you click the message, the tool guides you through the next steps.
The Advanced mode is similar to the previous version of Rational Team Concert Shell and also includes enhancements to the user experience. Conflict resolution, for example, is now easier, and you can resolve conflicts by using the Resolve context menus for conflicting files or folders. You no longer need to use the Pending Changes view to resolve conflicts. Richer menu options in the Artifacts view are available for adding components to a repository workspace and for reloading workspaces that are not synchronized.
Choosing a mode of operation
When you install Rational Team Concert Shell for the first time, the default mode of operation is Basic mode. You can choose to switch to the Advanced mode at startup or at a later time. On request, the startup dialog box helps you choose a mode of operation.
If you are an existing user and you install a new version of the Rational Team Concert Shell client or upgrade to a new version, Advanced mode is the default mode of operation during installation.
Getting started with Basic mode
To get started in Basic mode, you must create a new work area. A work area is the folder in the file system within the folder hierarchy that you want to manage with Rational Team Concert. This location is where Rational Team Concert loads files and folders from your team's stream. In Advanced mode, as well as in other Rational Team Concert clients, this location is called the sandbox.
To create a new work area, you select a folder from the file system as your work area. The next step is to get files and folders from your team's stream into the work area for Rational Team Concert to manage. To connect to Rational Team Concert source control, you need a team invitation. Additionally, you need a source control configuration file or the URI for your team's stream, which can be obtained from your team lead. The source control configuration file has information about the team's stream and its components. Rational Team Concert Shell uses either the URI or the source control configuration file, and creates a repository workspace from the stream. The repository workspace is then loaded into the work area, and files and folders in the work area are now managed by Rational Team Concert.
After a work area is created, changes that you make to files and folders in the work area are tracked by Rational Team Concert. In subsequent sessions, you can open the work area by using a taskbar menu item. Rational Team Concert supports one current work area at a time. If you need to work with multiple work areas, you must switch between them by using the Open Work Area menu from the taskbar. On the Open Work Area menu, work areas are displayed in a recently used list. The current work area is at the top of the list.
Getting the source control configuration fileThe team lead, who works in the Rational Team Concert Shell client in Advanced mode, generates the source control configuration file and shares it with users. Alternatively, the team lead can share the URI of the stream.
Getting the team stream's URI
The rich client has a Copy URI menu option on most artifacts in the Team Artifacts view.
The team lead can copy the stream URI by using this menu option and share it with the team members.
Working in Basic mode
In Basic mode, a richer set of menu items is available on the taskbar, where you can manage the Rational Team Concert Shell by using the control panel, connect to existing repository connections, create or open work areas, and connect to online help. You can also deliver all changes that you make locally, in one delivery, to the team's stream, or you can accept all the team's changes at once with the Deliver All Changes and Accept All Changes menu options.
The menu options change based on whether you are connected to a work area or whether you are logged in.
The control panel
The control panel for Basic mode enables you to create a work area and manage preferences.
Most preferences have predefined values in Basic mode that cannot be changed. You can decide at startup whether Rational Team Concert should automatically begin to manage the last work area that you were connected to. You can also decide whether to be prompted to associate a work item with each deliver operation.
Working with files and folders
After you set up a work area, you can start working on the files and folders in the work area. In Basic mode, by default, when you change an existing file, the file is automatically checked in. This feature makes source control simpler so that you do not need to use the two-step process of checking in and delivering. Each file is checked in to a new change set. You must explicitly add new files to source control. You are prompted to enter a check-in comment when you deliver a change. You can also associate a work item with the delivery.
You can choose a work item based on number, or you can run a query to select a work item to associate with the delivery.
Resolving a conflict
When a conflict occurs, you are prompted to resolve the conflict by a message on the taskbar.
You can resolve the conflict by using the context menu options.
Downloading the server version
You can now download the latest version of the file on the server to a temporary location. This feature is useful when you want to compare the current file with what exists in the team's stream, for example, in conflict scenarios.
Dissociating work items
Before this release, you could use the ISPF client to associate a work item with a change set. In this release, you can now dissociate a work item from a change set. This SCM operation is available from an outgoing change set view and from the history view of a file.
View or compare file content
Before this release, you could use the ISPF client to see the content of a change set from the history view of a file or member. In this release, you can see the content of each version of a file from the list of change sets displayed in the history panel. You can also compare a version with a previous or current version (the version that is loaded in the sandbox).
Dependency build and promotion
IBM i search path improvements
Search path system definitions now include dedicated fields to specify source and object libraries, which improves usability.
Build definitions are enhanced, so that you can associate a search path, which enables you to specify a search path that is unique to each build definition.
A new property type was added: search path. Properties of this type can be defined in build definitions and build engines.
The search path resolution order is now available. For each item being built, the search path used is the first one found in this order:
- Translator (most specific)
- Build definition
- Source and object libraries of the IBM i project, containing the member being built (least specific)
The Select Search Path window now includes a preview section.
Build subset enhancements
When you create a build subset, you can select from a list of files built in a dependency build. Build subsets are useful for organizing streams that contain large numbers of files and for limiting the scope of personal builds.
- Process control
From the process configuration tab for a project area, administrators can now control the ability of users to create, modify, and delete build subsets based on user roles. Additionally, administrators can limit the visibility of build subsets.
- Personal and team build subsets
You can create build subsets that are either private (not visible to anyone but that user) or scoped (shared with other team members who have access to the associated build definition). You can also create build subsets for other members of your team or project area. Personal build subsets that you own are now visible in a folder called My Subsets, which is available in the Team Artifacts view in the Enterprise Extensions folder. Team build subsets are visible in a Shared Subsets folder.
- New build subset editor
The build subset window is now replaced by a new build subset editor. You can use the new editor to set the build subset owner and visibility.
The editor also includes file-selection enhancements to make it more obvious that you can add files to a build subset by using any or all of the following methods:
- Browsing and selecting individual files (manual selection)
- Using rules
- Using work items
- Additional build request options
You can now request a build directly from a context menu on the build subset itself or from the build subset editor, in addition to the previously available method of requesting that a build subset be built from the associated build definition.
z/OS link edit enhancements
The Rational Team Concert z/OS dependency build automatically attempts to rebuild main programs when one or more statically linked subprograms are updated.
New default scanner for System z
The default z/OS scanner for System z uses the same scanner that is included with the latest version of Rational Asset Analyzer, which is available when Rational Team Concert 4.0.3 becomes available.
Ignore changes to system definitions during dependency builds
With this flag, you can control how the Rational Team Concert dependency build analyzes the changes to the definitions since the previous build result.
Improved performance for dependency build preprocessing
This release include significant improvements in Enterprise Extensions dependency build preprocessing speeds. In performance testing, the preprocessing speeds in 4.0.3 test environments were up to 75 percent faster than the preprocessing speeds in the 4.0.2 test environments.
History importer enhancement improves connectivity of Jazz SCM version trees of imported files
When you import related multiple streams, the history importer now reflects the version tree of files in Rational ClearCase and Rational Team Concert when you import streams in the dependency order.
For example, if the chaparral_main UCM stream is imported by creating baselines R6.0_db and R7.0_db for the component db , when the chaparral_r6_main UCM stream is imported with the initial baseline for db as R6.0_db, the history importer adds the Jazz SCM component db 's baseline named R6.0_db when a file or folder in the db component is added to the synchronization stream.
The following image shows the Rational ClearCase version tree for a file that is modified on multiple streams:
The history view for the corresponding file in Rational Team Concert is shown in the following image. The view is set to show all the versions in the repository.
You can achieve the same version tree reflection with base Rational ClearCase when you set the parent branch's label-type as a backstop label-type when you import a child branch.
In addition, the history importer now creates baselines in the Rational Team Concert stream instead of in an internal workspace.
Create a synchronized stream by using the command line
This release includes support for the new create ccss subcommand. The command enables scripting to create many synchronized streams. The usage syntax for the command is as follows:
Help for: ccc create synchronizedStream
Purpose: Create a ClearCase Synchronized stream.
Usage: ccc create synchronizedStream [options]
--certificate arg - The file that contains the user's login
--smartCard - Uses the connected smart card for
-A [--attype] arg - Attribute type selector used by the
history import to select which labeltypes
or baselines to import and in what order
-B [--brtype] arg - Branch type selector to synchronize
-C [--sync-user] arg - Synchronization process Jazz Team Server
-e [--engine-sleep-time] arg - Sleep time of the import build engine in
seconds. The default value is 120 seconds.
-G [--gpath] arg - ClearCase view storage global path
-H [--hpath] arg - ClearCase view storage local path
-I [--importOnly] - Creates a history importer stream.
-L [--lbtype] arg - Back stop label type selector
-M [--merge-ws-name] arg - Optional merge workspace name
-P [--password] arg - The password for the repository.
-p [--project-area] arg - Project area (name or UUID).
-r [--repository-uri] arg - The URI that specifies the location of the
-t [--team-area] arg - Team area (name or UUID) in the given
-T [--view-host] arg - ClearCase view storage host
-u [--username] arg - The user name for the repository.
-U [--ucm] arg - Stream selector
-v [--verbose] - Shows more information.
-V [--view-stg] arg - ClearCase view storage path
-Y [--sync-user-password] arg - Password of the synchronization process Jazz
Team Server account.
Reports for timesheet entry data
New reports that use live timesheet entry data are now available. The added reports are the Personal Timesheet, the Personal Timesheet by Project Area, the Personal Timesheet by Work Item, the Team Timesheet, and the Work Item Timesheet Summary.
ETL for "modified by" data
The "modified by" data is now loaded into the data warehouse and stored in the following data warehouse table:
- RICALM.REQUEST_HISTORY (Field: MODIFIER_ID)
ETL for approvals and approval descriptors
The approvals and approval descriptors data is now loaded into the data warehouse and is stored in the following data warehouse tables:
ETL for complex custom attributes
The complex custom attributes data is now loaded into the data warehouse. The data includes complex custom attributes of these types: Category, Contributor, Deliverable, Item, Iteration, Process Area, Project Area, Team Area, Timeline, Work Item, and SCM Component.
The complex custom attributes data is stored in the following data warehouse tables:
Rational Team Concert plug-in for Jenkins
A Rational Team Concert plug-in is now available for Jenkins. This plug-in enables you to configure a Jenkins job to run the SCM phase using Rational Team Concert source control. The plug-in adds an option for Rational Team Concert in the Source Code Management section of the job configuration, with options to point directly to a build workspace, or to take the SCM configuration from a referenced build definition in Rational Team Concert. The build definition approach supports advanced SCM options, such as load rules. In addition, a Rational Team Concert build result is created, which provides traceability to changes in the build, their associated work items, and links to the Jenkins build. The Rational Team Concert plug-in also works well with the Hudson/Jenkins integration that was added in Rational Team Concert 4.0, which enables you to request Jenkins builds from within the Rational Team Concert clients. This plug-in is available from the Jenkins plug-in repository (not part of Rational Team Concert proper) and works with different versions of Rational Team Concert (tested with version 220.127.116.11 and later).
ClearCase Synchronizer tutorial
This release contains a new tutorial that walks you through the process of configuring the ClearCase Synchronizer to synchronize items that are stored in Rational Team Concert source control with items that are stored in Rational ClearCase. By following the steps in the Get started with the ClearCase Synchronizer tutorial, you create a ClearCase synchronized stream and a merge workspace, synchronize files between Rational Team Concert and ClearCase, and create a schedule for future synchronization operations.
Work item customization tutorial
This release contains a new tutorial that shows you how to customize work items. By watching the Customize work items tutorial, you learn how to create a work item type, create a work item attribute, create an enumeration attribute type, define a workflow, and customize the work item editor.
Jazz.net now includes a deployment wiki and community. The Deployment wiki and community provides deployment-specific information and guidance for Rational products that extends beyond the basic product and support documentation. The wiki assembles deployment information from many locations into a single community-developed and community-managed knowledge base.
Help for integrating Rational Team Concert and Rational Developer for i
This release includes a new set of help topics that describe how to integrate Rational Team Concert and Rational Developer for i. Using Rational Team Concert and Rational Developer for i together, software development teams can develop using the tools provided by Rational Developer for i and the planning, team collaboration, build, source control management, defect tracking, and deployment tools provided by Rational Team Concert. See Integrating Rational Team Concert and Rational Developer for i for details.
Refactored information center
The information center has been refactored to emphasize the specific Rational solution for Collaborative Lifecycle Management products. This new organization makes it easier to find help for a specific product or for Rational Reporting. The Rational solution for Collaborative Lifecycle Management section of the table of contents contains content that is common to all the CLM products, such as installing, upgrading, and administering.