More than 150 improvements and new features have been integrated into ReqSuite® RM 3.4. The most important new features are listed below.
The most obvious new feature is the redesign of the start page as well as the workspace within projects. In the latter, for example, it is now possible to collapse the category bar on the left side to have more space for the element tables. In addition, the Process Guide has been completely redesigned and now integrates better with the various editing windows.
Better Editing Options
In ReqSuite® RM 3.4 you can now edit requirements / elements directly within the element tables without having to open the edit window every time (inline editing). This makes it easier to make small changes to requirements. In addition, it is now possible to view the attachments to a requirement / element directly in the table.
Furthermore, the possibility for block selection (using Ctrl + click, etc.) has been created in the element tables and it has been ensured that table settings made by the user (column width, sorting, etc.) are automatically saved.
From now on it is also possible to switch between different requirements / elements in the editing window without having to close and reopen this window every time.
Finally, ReqSuite® 3.4 allows to document reasons when deleting requirements / elements, if desired.
Improved Change Support
In the configuration, it is now possible to set which change effects can potentially exist between different elements. Consequently, if a change is made to a corresponding element in a project, the potentially affected elements are automatically marked and the persons responsible for them are informed.
New Bulk Editing Functions
In addition to bulk editing of attribute fields and relationships, which ReqSuite® RM has already supported for many versions, it is now also possible to copy multiple requirements / elements at the same time or export them to other projects.
To facilitate the mission-critical configuration of ReqSuite®, various support measures have been integrated. This includes, for example, a check for circular relationships or warnings for critical deletions. In addition, the layout set by the user is now automatically saved in the model preview and is made available as an image to the end users within an associated project.
Colors and Symbols
In order to find relevant information faster, new visualization options have been created in ReqSuite® RM 3.4. On the one hand, colors can be defined for categories as well as for enumeration values within the configuration, which are then applied in related projects. In addition, users are alerted by means of symbols to requirements / elements for which there are open comments, exceeded deadlines or change impacts.
Selection for Reuse
When reusing requirements / elements from other projects, the “all or nothing” principle has been softened in ReqSuite® RM 3.4. Users can now select which elements attached to an element to be reused should also be reused (and which not).
As of now, ReqSuite® offers an interface to other ReqSuite instances in addition to interfaces to JIRA, TFS/Azure DevOps and GitLab. This allows different organizations that have ReqSuite® RM in use to exchange requirements / elements with each other. Internally, we will use this feature to allow our customers to directly document change requests to ReqSuite® in their ReqSuite® instance and automatically exchange them with our development backlog.
Automatic State Transitions
In ReqSuite® RM 3.4, automatic state transitions can now be defined. Specifically, it can be set that a requirement / element is automatically set to a certain state if all requirements / elements derived from it have already been set to this state.
Enhancements in Word and Excel export
As of ReqSuite® RM 3.4, the simple Excel export now also includes all comments and attachments associated with a requirement / an element by default. In addition, the folder path of an element is also output alongside its name.
New markers have also been defined for tables in the Word export (<CATEGORY>:TABLE WITH…):
- VERSION: Outputs the current version number of a requirement / element.
- RELATED_COMMENTS: Returns the comments for a requirement / an element
- RELATED_ATTACHMENTS: Outputs the attachments to a requirement / element
- INSTANCEMODELS: Outputs the image for a requirement / element
- LAST_CHANGE: Returns the date of the last change to a requirement / element
- DEADLINE: Returns the target date of a requirement / element
- CREATION_DATE: Outputs the creation date of a requirement / element
Furthermore, when outputting relationships in tables, it is now possible to specify whether all (ALL) transitively attached elements of another category or only the directly related elements (DIRECT) of this category are to be output.
Furthermore, the possibility has been created to extend the forms of elements during Word export with additional lines for status and version. Instead of <CATEGORY>:INSTANCE one selects <CATEGORY>:INSTANCE+ for this.
Finally, it is now possible in Word to apply filters to the output of attachments and comments using ATTACHMENTS and ALL COMMENTS, respectively, where the filter refers in each case to the request or element to which the attachment or comment belongs.
Extension of the JIRA / TFS / GitLab Interfaces
The interfaces to JIRA, TFS and GitLab now also supported an exchange of Deadline / DueDate and Labels.
In large projects, baselining can take a lot of time. For this reason, baselining has now been implemented as an asynchronous function for large projects. This means that users do not have to wait, but are notified as soon as the baseline is created.