What's new in IBM® Engineering Requirements Management DOORS Next 7.1
Learn more about what’s new and changed in DOORS® Next 7.1.
Milestone 10
This milestone contains only quality improvements.
Milestone 9
This milestone contains only quality improvements.
Milestone 8
- SAFe® 6.0 Full and Essential templates
-
The Scaled Agile Framework® (SAFe®) methodology is an industry-standard framework for helping organizations scale agile and lean practices to an enterprise level. Now, SAFe® 6.0 Full and Essential templates are available to establish a quality management environment that contains artifacts to validate cross-solution train portfolio epics, cross-ART capabilities, and ART features and stories in the scope of a portfolio of solution trains of one or more ARTs and its teams.
The following changes are done:- Removed value stream, strategic theme, and program artifact type for moving support for strategic alignment, lean budgeting, and objective-key results (OKRs) to Engineering Workflow Management. Unique attributes and artifact templates associated with these artifact types are also removed.
- Updated terminology to align with SAFe® 6.0 recommendations. The following artifacts are updated
to reflect the following terminology changes recommended by SAFe® 6.0:
- Values of scope attribute data type
- Updated roles and permissions to empower teams and clarify responsibilities
Note: In SAFe® 6.0, the following terminology changes are introduced:- Program increment with planning interval
- Solution with solution train
- Program with ART
- Solution epic with solution train epic
- Program epic with ART epic
Note: In this milestone, the predefined lifecycle project templates are not updated to use SAFe® 6.0 templates. You must manually create an application project area by using the individual application SAFe® 6.0 project template and establish the required associations.For more information, see Scaled Agile Framework® (SAFe®) 6.0 Requirement Management process templates.
- New options added for filters to match the artifacts
-
Most filters can be combined with new group operators, including matching all, some, or none of the conditions in a group of filters. Filters for the basic attribute data types are supported. Filters for enumerations, tags, links, or full-text are not supported. The user interface for editing the expanded filters is enhanced, and it aligns with the Carbon Design System. Filters are easier to read, the targets are larger, and the keyboard accessibility is improved. Filters can be edited in a separate window.
Milestone 7
- Create a historical baseline
-
The Create Baseline operation now provides the option to create a historical baseline of a stream. This option allows you to select a date and time in the past to capture the state of the artifacts at that point in time. The baseline that is created is referred as historical baseline and is similar to any other baselines.
- Ability to configure the artifact sidebar width in the Artifact editor
- Now, the new com.ibm.rdm.fronting.web.artifactSidebarDefaultWidth advanced property for RM servers can be used to set the width of the artifact sidebar in the Artifact editor. Users can set the percentage of the artifact sidebar width to the overall window width. The default value is 20 percent. Users can still manually adjust the width.
- Enhancements to the REST APIs
-
Introduced the following enhancements to the REST APIs:
- Create a historical baseline of the stream. A new option Create Baseline is provided that allows you to create a historical baseline of a stream for a specific historical timestamp. The baseline of a stream that is created earlier is referred as historical baseline. The resulting baseline is not different from another baseline.
- Allow HTTP clients to retrieve the content of the delivered and undelivered changesets. The changes retrieved are same as the changes displayed in the Changed Resources tab in the Changeset editor screen. The retrieved data includes resources that are added or deleted and provides concept and version URIs.
- Retrieve a list of baselines for a given stream by introducing a new public OSLC configuration
query capability. This capability allows HTTP clients to retrieve a list of baselines for a given
stream.Note: This API only retrieves baselines that are not archived from a stream.
- Provide information about an artifact such as when it was created, modified, or deleted by a specific user within a given period.
- Added a filter to an existing REST API that retrieves history of an artifact to allow the API to retrieve history of an artifact within a given period.
For more information, see the following topics:
Milestone 6
- Ability to export and download ReqIf definitions from a baseline context
- You can now export and download the ReqIF definitions available in a baseline.
- Ability to view ancestor and descendant artifacts in filtered module views
- Now, the ancestors and descendants of matched artifacts can be viewed when artifacts in a module are filtered. When a filter is active, options to show the ancestors, descendants, or both appear automatically. These options can be saved in a view. Depending on the selection of the option, you can also select the Highlight filter matches checkbox to differentiate the artifacts that match the filter from the ancestors and descendants of those artifacts. Highlighting is a user preference and is not saved with the view, but it can be enabled at any time.
Milestone 5
- Reopen Operation Has been added to the code review tool
- Users can now reopen a closed code review with Jazz Admin and Jazz Project admin roles.
Milestone 4
This milestone contains only quality improvements.
Milestone 3
This milestone contains only quality improvements.