Revisionhistory is not retained in Testsuite&plan migration

[Lokeshmaxi]

1. ReflectedWorkItemID Field Configuration:

I was using Azure DevOps Migration Tools (version 16.2.0)

1. When using a custom field (Custom.ReflectedWorkItemId) for the ReflectedWorkItemIdFieldName parameter, the processor failed with the error:

"ReflectedWorkItemId not found for work item ID (*****)"*

Upon investigation, it appears the corresponding work item was deleted in the source system.

However, when switching to the built-in field Microsoft.VSTS.Build.IntegrationBuild as the value for ReflectedWorkItemIdFieldName, the migration completed successfully.

👉 Request: Please confirm which field is officially recommended for the ReflectedWorkItemIdFieldName when using the TestPlansAndSuitesMigrationProcessor.

2. Missing Test Suite Revision History:

During the migration, we observed that revision history for Test Plans and Test Suites was not retained.

Only the current state was recreated in the target system.

👉 Request: Please confirm if this is the expected behavior and whether revision history support is on the roadmap for this processor.

3. Static Test Suite Title Mismatch:

Some static test suites were migrated with modified titles in the target project.

The new titles are slightly different from the source, though they appear structurally correct.

👉 Request: What logic governs renaming or altering suite titles during migration? Is there a mapping or sanitization that we need to be aware of?

4. Requirement-based Test Suites Not Migrating:

We observed that requirement-based test suites are not being migrated at all.

This was consistent across multiple projects.

All associated work items have already been migrated beforehand.

👉 Request: Please confirm if requirement-based test suites are supported in v16.2.0, and if so, what additional configuration is needed to ensure successful migration.

We appreciate your guidance on the above issues to ensure accurate and complete migration of our test assets.

[MrHinsh]

Request: Please confirm which field is officially recommended for the ReflectedWorkItemIdFieldName when using the TestPlansAndSuitesMigrationProcessor.

Follow the provided how-to in the documentation for migrating plans and suits

Request: Please confirm if this is the expected behavior and whether revision history support is on the roadmap for this processor.

Confirmed. It is not posible to migrate revission history for Suits and Plans as they are not really work items.

Request: What logic governs renaming or altering suite titles during migration? Is there a mapping or sanitization that we need to be aware of?

No idea, depends on your title. Perhaps an example?

Request: Please confirm if requirement-based test suites are supported in v16.2.0, and if so, what additional configuration is needed to ensure successful migration.

Supported. No additional configuration needed

[Lokeshmaxi]

Request: What logic governs renaming or altering suite titles during migration? Is there a mapping or sanitization that we need to be aware of?

For example: I have testplan with title "Migration test", where respective test suite have title "Migration of Test suites", now when I've ran testplan&suite migration processor ,The test plan is properly migrated with title "Migration test", but respective test suite is migrated as "Migration test" in the Target project? what could be reason for this behaviour? i have analyzed generated logs which ran with "Verbose" & haven't find anything useful or error in logs.

[MrHinsh]

No idea... not aware of any renaming. Test suits are expected to be names the same as they are

[Lokeshmaxi]

ok Martin, Thanks for response