ReqView 2.22 – Integration With Azure DevOps, Search in Documents

 Apr 13, 2026 Libor Buš releases share

Integrate Requirements Management in ReqView with Project Management in Azure DevOps (ADO). Use advanced search in documents, new grid component, and enhanced PDF export.

Integration With Azure DevOps (ADO)

You can benefit from an integrated Application Lifecycle Management (ALM) solution by connecting ReqView with Azure DevOps (ADO):

• ReqView allows you to manage stakeholder requirements, system requirements, low-level HW/SW requirements, risks, and validation & verification (V&V) information. Data is organized into structured documents and linked, enabling seamless review and traceability across related requirements.

• Azure DevOps (ADO) enables you to manage HW/SW development using various work item tracking processes. You can also manage tests and their execution, Git repositories, build pipelines, and artifacts.

Workflow for Using ReqView and ADO:

1. Capture Requirements: Define and manage requirements, risks, and tests across the V-model within ReqView.
2. Export Requirements: Export a baseline of your requirements document from ReqView as ADO work items to share them with the development team.
3. Trace Requirements: Navigate between requirements in ReqView and work items in ADO in both directions.
4. Manage Development: Track HW/SW development progress in ADO using either agile or traditional development processes.
5. Import Development Status: Synchronize development status from ADO work items back into ReqView. Display this status directly within a Requirements Traceability Matrix (RTM) in ReqView.

For more information, see Integrate With Azure DevOps (ADO).

Search Text in Documents

You can now search across ReqView documents using the new Search pane located on the left. The pane displays results grouped by documents, objects, and attributes. Text matches are highlighted within table views, the Attributes pane, and the Discussion pane:

Click on any search result to focus on it in the current table view, the Attributes pane, or the Discussion pane. To navigate through search results, press F3 for the next result or ShiftF3 for the previous one.

You can also customize your search with the following modes: Match Case, Match Whole Word, Use regular expressions, and Limit Search to Current Table View.

For more information, see Filter, Sort and Search Requirements > Search Text in Documents.

New Grid Component

This release enables a new grid component as the default for document table views. The new grid introduces several usability enhancements:

• Show or hide table columns: Right-click on the table header and choose Columns from the context menu.

  

• Freeze Columns: Keep key columns visible while scrolling horizontally by right-clicking the table header and selecting Freeze Column from the context menu.

• Context Menu: Edit document objects using the context menu instead of context toolbar. For instance, you can edit an attribute or a single object or multiple objects by right-clicking the edited column and selecting Edit from the context menu.

If needed, you can switch back to the previous grid component by enabling the Use legacy grid component option in the Preferences dialog.

Improved Export of PDF Files

We have completely redesigned the PDF export process to address several known issues. The new export engine automatically detects content overflows and styling issues, displaying them in the PDF Export Warnings dialog. Additionally, you can now use export sections with unique page sizes, margins, and layouts.

Note: You may need to update your HTML templates. For example, download and customize PDFBookTemplate.html to generate PDF files with a professional book layout.

For more information, see Export Documents to PDF.

Disable Section Numbering

You can set the Disable automatic section numbering option in the Document Properties dialog to display and export document sections without any number. This is particularly useful for showing the original section numbers in read-only documents imported from PDF, MS Word (such as industry standards), or from Enterprise Architect design models.

Default Enumeration Values

We have updated the handling of default enumeration values to align with industry-standard requirements management tools. The default value for an enumeration attribute is now set at the moment a document object is created. Consequently, changing a default value later will not affect existing objects.

Note: When opening a project saved in an older version of ReqView, enumeration attributes with undefined values will be automatically updated to the current default value for all document objects.