General

1. New Features

1. Support to copy a Test plan and its associated test suites from Test Hub.

Users can now copy and reuse test plans and associated test suites in Test Hub, with options to customize titles, choose paths, and selectively copy test suites while flexibly managing test case IDs and details through reference or duplication

2. Azure DevOps ‘MultiValue’ custom control support in Modern Requirements4DevOps

Modern Requirements now supports Azure DevOps custom control ‘Multivalue control’. Displayed as a field in Modern Requirements, allowing users to edit, configure, and generate reports with multiple values shown as semi-colon separated when selecting them with the help of checkboxes.

2. Tool Enhancements

1. Performance optimization on loading files on the browse page

Users shall now experience significant performance improvements when files are loaded on the browse page once a module is accessed. This will save time and give a better user experience without any hassle.

2. Message update in Diagram/Simulation/Use Case/Smart Note/FAQ when file is not checked in.

When file is not checked in, on renaming/deleting/moving/copying the file now shows the proper message Cannot [action], because file is not checked in. or in the case of copy, it shows like “Unable to copy, because file is not checked in.

3. Work item ‘Revision ID’ is replaced with ‘Update ID’ in ModernRequirement4DevOps.

Instead of ‘Revision ID’ of a work item an ‘Update ID’ will now be shown in the MR application. Also, the column labels ‘Revision’ or ‘Rev. ID’ have been replaced with ‘Version’ or ‘Ver. ID’ respectively.

4. Performance Optimization in Project Connection time.

The project connection time is reduced, and projects files are loaded faster on accessing ModerRequirements4DevOps module for the first time.

5. Updating static files without explicitly clearing browser cache.

Users no longer need to clear browser cache to update static files like CSS and JavaScript, as they will now update automatically, eliminating hurdles like in file creation and report generation.

3. Change Request

1. Linked work item details in “Linked Work item Type” virtual field of Smart Report now corresponds to the work item version/revision.

Smart Report displays details of linked work items based on configured ‘Linked Work item Type’ virtual field, with respect to revision(s), specifically for work items in Smart Docs, Version Package, Review, Baseline, and Trace Analysis modules, aiding users in viewing version-specific linked work item details.

Smart View

1. Change Request

1. Variant functionality in Smart View.

In the latest MR version, users can now view all variants belonging to the same variant family, known as a Variant Group (VG). A VG is identified by a ‘VG’ tag, allowing users to see all group variants.

2. Tool Enhancement

1. Add Multiple work items at once as variant from ‘Link to existing work item’ window.

In Smart View’s ‘Variants’ Tab, users can now easily add multiple work items as variants by clicking ‘Link existing work item’.

Admin Panel

1. New Features

1. Configure a comment as ‘Required’ for ‘Review Response Action’ value.

Administrators can configure a mandatory comment requirement for a designated ‘Review response action’ value, ensuring stakeholders provide justifications when selecting this value during a review.

2. Tool Enhancement

1. Configure versions for Copilot4DevOps.

In the admin panel’s “General Tab,” users can configure Copilot4DevOps settings, selecting the API model and specifying model versions to be displayed under the “Additional Instruction” right panel, allowing users to choose their preferred model version for data generation.

2. Copilot4DevOps Token Status

The admin panel now includes a “COPILOT4DEVOPS TOKEN STATUS” section within the “Licensing” tab, providing users the visibility into their token usage. Information includes monthly consumption, quota allocation, and start date, with token quotas tailored to the user’s
Modern Requirements license type, such as Floating or User-based.

Version Package Management

1. Change Request

1. View all Variants of the work item at ‘Switch Variant’ window.

In the latest MR version, users can now view all variants belonging to the same Variant Group (VG), in the ‘Switch Variant’ window.

2. New Features

1. Update Version Package template of existing version package(s).

Users can now update the associated Package template for an existing version package using the ‘Update Template’ option, with changes in work item type compatibility and field properties reflected in the version package, while modifications in variant packages are not impacted by meta template updates.

2. Create Package Variant along with the associated Sub Packages.

When creating a package variant, users can now include ‘sub-package(s)’ of a version package by choosing from options like ‘Link sub package(s),’ ‘Create variant of sub package(s)’ with customizable prefixes/postfixes, or ‘Don’t link sub package(s),’ providing flexibility and control over the association between source and variant packages.

3. Create a Version Package from the Queries and Backlog.

Users can create a Version Package directly from the Queries and Backlog tab, selecting work items and applying a Package template, with the created Version Package opening in a new browser tab.

4. View the changed type of work item(s) on the Version Package grid if changed from ADO.

Users can now easily identify and interact with work items that have changed types in the Version package grid. The changed work items are highlighted with pink if allowed or red if not allowed validating from Package template. Locked work items are validated and highlighted accordingly, allowing users to remove work items that are not allowed.

5. The last selected package template is remembered on reopening the new package.

The user selection for the package template is retained in the new package window. The last selected template is auto-selected in creating New Package, New Package Variant, Sub Package, and Linked Package.

6. Column Option on the Version Package grid.

Users can now customize column options for work items on the Version Package grid.

7. Context Menu meatball icon beside the work item title.

Users can now open the work item context menu from the meatball icons appearing beside the work item title.

8. Work item title shows as hyperlink on the Version Package grid.

Users are now able to click the work item title on the Version Package grid. On clicking, Smart View will invoke if the work item is Locked, and the ADO editor will open for Live work items.

9. Exclude ‘Live’ work item from a version package without breaking it links with other work item(s) in ADO.

Users are now able to exclude any ‘Live’ work item from the Version Package using the ‘Remove from Package’ option. The linking of respective work item with other work item(s) will remain intact in ADO and work item will get removed only from the Version Package.

10. Permissions for Version Package module.

Admins can now give permissions to the group of users on Project level from the ModernRequirements4DevOps admin panel settings.

3. Tool Enhancement

1. Add Multiple work items at once from ‘Link to existing work item’ window.

Users can now easily add multiple work items to the Version Package using the ‘Existing work item’ option.

Copilot4DevOps

1. New Features

1. Dynamic Prompt

A new “Dynamic Prompt” feature in Copilot4DevOps allows users to enter custom prompts in various modules, generating results based on selected queries and fields. Users can perform actions such as creating work items and publishing within ADO projects/teams and VPM/Smart Docs grids through the generated results.

2. Pseudocode

Copilot4DevOps enables the generation of pseudocode for input work item data, allowing users to select HTML fields, view original data, generate pseudocode, and perform actions like copying, adding to work items, or creating new work items with the generated pseudocode, offering flexibility and ease of integration into ADO projects, Version Packages, and Smart Docs grids.

3. Test Script

Copilot4DevOps facilitates the generation of Test Scripts for input work item data based on user-defined HTML fields and chosen frameworks, offering features like copying, adding to work items, or creating new work items with the generated Test Script, providing flexibility for integration into ADO projects, Version Packages, and Smart Docs grids.

2. Tool Enhancements

1. Additional Instructions

Copilot4DevOps now includes an option for additional instructions, allowing users to append custom instructions for desired results. The user can specify AI model, conversation style, output length, response language, and add custom instructions, enhancing flexibility in existing functions like elicit, which features two custom instruction input areas for titles and detailed instructions.

2. Copilot4DevOps Token Status

A new “Token Status” feature has been added to Copilot4DevOps’ Home page, allowing users to track their token usage. It includes details like monthly consumption, quota, start date, and a progress bar, tailored to different license types like Floating or User-based.

3. Improved Extension Point startup performance for Copilot4DevOps module.

The startup performance from the extension point of the Copilot4DevOps module has been significantly enhanced. Users will notice considerable improvements in extension point loading times, resulting in a smoother and faster user experience

Smart Docs

1. New Features

1. Export Smart Docs file/folder(s) to Microsoft Excel.

Users can now export Smart Docs files and folders to Microsoft Excel using the ‘Export to Excel’ option, available in the context menu at both file and folder levels. The generated Excel file includes Project Team Details and a Smart Docs List with comprehensive information such as titles, creation dates, modified dates, and URLs for navigation.

2. Tool Enhancements

1. System will maintain the last selection of Smart Docs templateat ‘Newfile’ window.

Upon creating a new Smart Docs, a user will be able to see his last selected template which he used in the past for file creation.

2. Support of Document Properties in Smart Docs Versions.

Users can now configure and export document properties directly to Microsoft Word/PDF from Smart Docs versions, accessible through a toolbar when viewing both manually created Smart Docs versions and Review versions.

3. Configure “Linked Work item type” virtual field from Column Options.

Like Smart Report, users will now be able to configure a “Linked Work item Type” virtual field from Column Options right panel. A user can configure the fields of linked work item which need to be shown in a grid column using the ‘Config’ option.

4. Froala version integration

Users can now experience a better UI with Froala’s latest version integration in Smart Docs with some bug fixes.

Review Management

1. Change Request

1. ‘Submit Comment’ option is moved from ‘Responses’ tab to a new tab ‘All Comments’.

A ‘Submit Comment’ option has been moved from ‘Responses’ tab to the new tab ‘All Comments’ keeping the same functionality as before.
Note: The details of a new tab ‘All Comments’ is explained below under section 1

2. New Features

1. ‘All Comments’ tab is added into the right panel.

A new ‘All Comments’ tab is introduced in the right panel of Smart Docs, consolidating both ‘Submit Comment’ and the newly introduced ‘Text-based Comment’ options, with the ‘Submit Comment’ option previously in the ‘Responses’ tab now relocated to this new tab.

2. Add text-based comment on a selected part of text in a work item field.

Users can now add text-based comments to selected text in a work item field using the ‘Add Comment’ icon on the review grid toolbar, facilitating a seamless commenting experience with highlighted text and clear identification of comment types in the Summary tab.

3. A ‘Comment’ is configured as ‘Required’ for ‘Review Response Action’ value.

If a comment is configured as ‘Required’ in the MR Admin panel for the ‘Review response action’ value then upon selecting a particular action value, the review stakeholders shall be prompted to enter a comment to rationalize your action, otherwise you cannot proceed with it.

3. Tool Enhancement

1. The count of ‘Submit Review’ shall be shown with respect to the count of Submit Review submitted in the ‘Responses’ tab.

The count of ‘Submit Review’ is shown with respect to the count of Submit Review submitted in the ‘Responses’. Previously only a single count for ‘Submit Review’ was shown for a Review stakeholder.

Smart Report

2. New Features

1. Generate Smart Report on Test Plan or Test Suite including sub-test Suites from Azure Test hub.

Users can now generate Smart Reports in ADO Test Hub, including sub-test suites of a chosen Test Plan or Test Suite, with a new option “Generate Report including Suites hierarchy.” The feature allows selection of multiple test suites in a hierarchy, with a limit of 25 test suites, displaying a notification if limit is exceeded.

2. Save Smart Report directly into Document Management System.

Users can now directly save generated Smart Reports to the Document Management using the “Save to Library” option, available in Smart Report, Smart Docs toolbar, and Advanced Reporting modules. The feature allows customization of titles, selection of folders, uploading of custom Word templates and handling existing file scenarios.

2. Tool Enhancement

1. Support to generate report in Test Hub-exclusive to Enterprise Plus License holder.

Users with an “Enterprise Plus” license will be able to utilize the “Generate Report” option in Test Hub exclusively. For others, this feature is disabled, accompanied by a tooltip on the “General Report” option indicating its exclusive support for Enterprise Plus licenses.

2. Support to display the date-time pattern in the “Details” field of Test Results in Smart Part with the configuration defined in the admin panel.

Users will be able to customize the date-time pattern displayed in the “Details” field of Test Results within Smart Part, in alignment with the settings defined in the admin panel.

Trace Analysis

1. Tool Enhancement

1. Generate horizontal matrix on version Package including sub-package(s).

Users can now include sub-packages when generating a trace matrix on a version package by checking the “Include sub-package(s)” checkbox. This feature ensures a clear hierarchy, considers associated sub-packages up to a specified level, and maintains functionality for top- level work items, linked items, and field configurations.

2. Sorting becomes easy on linked work items in the exported Excel spreadsheet.

In the exported Excel spreadsheet, top-level work item rows will now be merged by default if there are multiple linked work items associated with them. This enables users to easily view the respective predecessor work items in a path when sorting the work items in 2nd or subsequent columns, improving usability for filtering, sorting, and other functions.

3. UI and icons updates in Editor tab for both Horizontal and Intersection Matrix options.

Users can now experience a better understanding when creating a traceability matrix, with added label text in the Horizontal Matrix tabs and updated icons and checkboxes text for Work item type, Query, and Multi-Query in both Intersection and Horizontal matrices.

4. Support to access test reporting in trace analysis exclusive to Enterprise Plus License holders.

Users with an “Enterprise Plus” license will be able to utilize the “Test Reporting” option in Trace Analysis exclusively. For others, this feature is disabled, accompanied by a tooltip on the “Test Reporting” option indicating its exclusive support for Enterprise Plus licenses.

5. Support to display the date-time pattern in the “Details” field of Test Results in Trace Analysis with the configuration defined in the admin panel.

Users will be able to customize the date-time pattern displayed in the “Details” field of Test Results within Trace Analysis, in alignment with the settings defined in the admin panel.

Baseline

1. New Features

1. Details added in Baseline Difference Report as per the applied filter on grid.

During baseline comparison, applying filters on work item fields allows users to generate Difference Reports containing only the filtered data, applicable to all types of comparisons (current version, baseline, or ADO Query) and report types (Summary and Detailed Reports).

Bug Fixes