Description | |
---|---|
Browser Support |
Jazz Foundation officially supports the Chromium Edge browser
Jazz Foundation now officially supports the Chromium-based Edge browser. Also, the Internet Explorer browser is no longer supported. |
Global Configuration Management |
Query enhancements
1. GCM query across project areas You can now run a query across multiple project areas in the same repository. Use the Project Areas field at the top of the query editor to designate one or more project areas. The default area is the current project area. The query shows results from all selected project areas. The available attributes to use in the conditions and result columns are a union of attributes from the selected project areas. You can also see a new Project Area result column in the query results to identify the source of the matching configurations. The query editor collapses the equivalent attributes (having the same URI and data type) from different project areas. But it flags the following conflicts in the attribute names:
![]() 2. GCM query using subqueries You can now nest one query inside another query by using the Subquery condition. The value of this condition is another query in the same project area. Whenever the main query runs, the latest conditions of the subquery are placed inline with the conditions of the main query. The subquery respects the project areas and result columns of the calling query. Image of a Subquery condition: ![]() 3. GCM query on archived configurations A new Archived query condition is added that supplants the Show archived configurations toggle for query results. The advantage of adding this condition is that it can be saved with the query. It has three values: true (for archived configurations), false (for active configurations), and archived and active (for both). If your query doesn't include the archived condition, the results would show only active configurations, preserving the behavior of prior releases. Image of the archived query condition: ![]() 4. GCM query for non-existence New operators are added to enhance the query capabilities for checking non-existence:
![]() 5. GCM query on child configuration attributes
Configuration Type is any of [Stream] AND Child Configuration > Configuration Type is any of [Baseline] Here, the query matches all global streams that have global baselines as direct child contributions. The results are always parent global configurations; the matching children are just a part of the query qualifications. Also, these conditions query against child global configurations only, and not local configurations from other applications. Image of query conditions for child configurations: ![]() |
Distinct permissions to add or remove links
Previously, the permissions to add or remove links were governed by the attribute modification permissions. Now, the attribute modification permissions and the permissions to add or remove links are distinct. The attribute modification permissions govern the attributes only (not the links). A separate set of Add or remove links permissions are added for each system-defined link type and all user-defined link types. Image of add or remove permissions for link types: ![]() |
|
Customize suffix separator in configuration names
Now you can customize the separator value that is used between the base name and suffix in a configuration name by using a new Advanced Property, Suffix separator in configuration names. The default separator value of one single space remains unchanged. Enter any string of your choice as a value (for example, "_", "#", and so on) or leave it empty. To represent a space character, use <space> and for a percent character, use <percent>. Image of the suffix separator property set to "###": ![]() Image of the suffix separator being used in baseline creation: ![]() |
|
Two new attributes (Committed By and Committed On) added to the baseline details section
You can now see the Committed By (user) and Committed On (date) attributes under the details section of baselines. Earlier, this information was only available in the history view of the baselines. When a baseline is created directly from a stream, the value of Committed By is same as Created By, and the value of Committed On is same as Created On. These values are different if the baseline is staged first, and then committed later. Image of the Committed By and Committed On attributes: ![]() |
|
Web UI |
New style for UI components: Buttons, links, breadcrumbs, modal dialog boxes, and tabs
Select user interface components (buttons, links, breadcrumbs, modal dialog boxes, and tabs) are restyled in IBM Engineering Lifecycle Management (ELM) products as part of the ongoing task to align with IBM's open source Carbon Design System. Note: Custom themes applied to these components in prior releases might require additional work to have the intended effect when you move to 7.0.1 or later versions. Image of buttons (before and after): ![]() Image of links in Task Guide (before and after): ![]() Image of breadcrumbs in the work item editor (before and after): ![]() Image of Delete Tags dialog box (before and after): ![]() Image of Select User dialog box (before and after): ![]() Image of dashboard tabs (before and after): ![]() |
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. |
© Copyright IBM Corporation 2020 | Contact | Privacy Policy | Terms of Use