New & Noteworthy

	Description
Global Configuration Management	Components and configurations now support team areas for managing group permissions Components and configurations now support team areas, which provide more detailed control for write access to artifacts in a project area. Team areas govern which options and privileges are available to users. For example, certain menus, buttons, or actions for modifying artifacts might not be available to users based on the team area of the artifact. By default, components are not assigned a team area, and the initial stream and baseline inherit the team area from the component. To change the team area, go to the Attributes tab for a component or configuration and select an option from the Team Area list: Unassigned: This option is the default setting for components. You also use this setting to remove the team area. Inherit From Component: This option is available only for configurations. Changes to the Team Area attribute of the component are automatically reflected in the configuration. More Team Areas: This option opens the Select Team Area dialog box, which you use to select a team area. A recently used team area: The list shows the five most recently selected team areas, including the current team area. When you create a configuration, it's assigned the same team area as the configuration it's created from. Image of setting a team area on a configuration:
	Permission changes This release includes several changes to permissions. Permissions for personal streams The permissions to modify a personal stream were removed because personal stream owners can now modify personal streams by default, such as archive, restore, or scrub them. New permissions are available to manage personal streams that other team members own. For example, you can archive, modify, scrub, or view the personal streams of other team members. By default, these permissions are only assigned to the Administrator role. You can now use team areas to assign permissions for personal streams. A personal stream is created with the same team area as its shared stream, but you can change the team area. The team area controls access for other team members, not the owner of the personal stream. These permissions are assigned to roles at the project or team level. Personal streams are not strictly private. Team members with a direct URI to another team member's personal stream can view it. Other permissions The permissions assigned to the default process roles for Dashboards, Process, and Reports were made consistent. During an upgrade, if a role ID matches a built-in role, the designated permission changes are applied regardless of role customization, but other permissions are left as is. To prevent this behavior, change the role ID. The "modify contributions" permissions were removed. Now, a single "modify" privilege allows modifications to both properties and contributions. Note: The contributions of baselines cannot be changed, regardless of privileges.
	Faster configuration tree updates In addition to the performance enhancements in 6.0.6 iFix003, further optimizations make adding, moving, and replacing configurations in global configuration trees even faster. This includes creating configurations, such as baseline hierarchies and creating multiple streams at once.
	TRS improvements for reporting reliability Several improvements were made to the following TRS feeds for the Global Configuration Management (GCM) application: GCM Resources (TRS 2.0) and GCM Process Resources (TRS 2.0). These improvements make Jazz Reporting Service reports based on the LQE data source more reliable and eliminate common causes for skipped resources. The improvements include these features: New TRS Feed Validation page: On this page, you can run a validation that compares the TRS feeds against data in the repository. Run the validation if Jazz Reporting Service reports have inconsistencies such as missing or duplicated resources. This feature is similar to the TRS validation feature for Rational Team Concert and Jazz Team Server, which is available starting in version 6.0.6 iFix003. TRS events are created for artifacts when project areas are archived or restored: When you archive a project area, TRS deletion events are created for the artifacts in that project area. Similarly, when you restore a project area, TRS creation events are created for the artifacts in that project area. Archived resources aren't listed as skipped resources: Resources that are missing because they are archived aren't listed as skipped resources. Self-repair: A self-repair feature creates a TRS deletion event when a requested resource is missing because it is archived. Repair for project areas: You can repair an entire project area by temporarily archiving and then restoring it. You should validate the TRS feeds for the GCM application if Jazz Reporting Service reports have inconsistencies such as missing or duplicated artifacts. You can also ask a Lifecycle Query Engine (LQE) administrator to validate a TRS feed against the LQE index. If both validations finish with no errors, the LQE index matches the data in the application repository. To validate the TRS feeds for the GCM application: 1. Open the application administration page: https://host:port/gc/admin 2. On the toolbar, click TRS Feed Validation. 3. In the TRS Feeds section, click a feed and click Validate. Image of the TRS Feed Validation page:
	Extension API for UI customization The Global Configuration Management (GCM) Extension API provides support for simple UI customization and automation. This API is modeled after the Rational DOORS Next Generation client extension capability and is packaged as an OpenSocial Feature so that OpenSocial gadgets such as custom dashboard widgets can consume it. For details, see Global Configuration Management (GCM) Extension API. Image of an example OpenSocial gadget on the Mini Dashboard with buttons for calling the API:
	Create baselines of local streams by using the Create Baseline action Previously, you could only use the Create Baseline action on global streams. Now, you can use the Create Baseline action on local streams, which are streams contributed from applications such as Rational Quality Manager or Rational DOORS Next Generation. To create a baseline of a local stream, select one or more local streams from a global configuration hierarchy, and click Create Baseline. In the Create Baseline dialog box that opens, you can select whether to replace the streams with the new baselines. Image of creating baselines of three local streams:
	Create streams from external contributions In the configuration tree, you can create a global stream from a global stream that is an external contribution, which is a global configuration from another Global Configuration Management server. This functionality is available when both servers are at version 6.0.6.1 or later.
	Move multiple configurations by using the Move and Place actions Previously, you could only move multiple configurations at once by dragging and dropping them. Now, you can use the Move and Place actions to select and move multiple configurations. You can move several configurations from different parts of one tree to the same or a different tree. Image of the Move and Place actions:
	Copy the URL of a configuration or component You can now copy the URL of a configuration or component to the clipboard. On either the toolbar or the context menu for a configuration or component, click Copy Link. Then, you can press Ctrl+V to paste the link in a new location, such as in an email, SPARQL query, or REST API. Image of the Copy Link icon on the toolbar:
	SCM icons are now the same in Rational Team Concert and Global Configuration Management Previously, the icons for source-control management (SCM) snapshots and components were different in Rational Team Concert and Global Configuration Management (GCM). Now, the SCM icons are consistent in both applications. Image of SCM icons in a global configuration tree:
Jazz Foundation	New repository tools command for database partitioning If your database supports partitioning, you can optionally partition the primary internal database table that stores configuration data by the underlying database. Partitioning can provide better performance and scalability if there is a large amount of configuration data in a configuration-enabled system. To enable partitioning, use the new -partitioning repository tools command. You should enable partitioning only if you have a large amount of configuration data and your underlying database supports partitioning. For details, see Repository tools command to partition the database tables.
	Update historical states for users When you make changes to a user in the user editor, you can now save some of these changes to the historical states by selecting the Save to All Historical States check box near the Save button. Only the user name, email address, and picture are updated in the All Historical States record. Any other changes are saved only for the current user state. Image of the Save to All Historical States check box:
	Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

New & Noteworthy for Jazz Foundation 6.0.6.1