Description
The process migration wizard currently supports only two scopes: migrate a single process instance (from the instance detail view) or migrate all running instances of the source process version (from the Processes view). There is no way to migrate an arbitrary subset of instances in one action.
Use case
A user needs to migrate only some of the running instances of a process version to a newer version — for example, instances matching a specific business key, a specific active activity, or a manually picked list — while leaving the rest on the current version until they complete naturally or are migrated later.
Today the only way to achieve this is to migrate instances one by one through the instance detail view, which is impractical when more than a few instances need to move together.
Expected behavior
The migration wizard should allow selecting which of the source version's running instances participate in the migration, instead of only "one" or "all". This could take the form of a filterable/selectable list of matching instances (similar to how the batch operations wizard already lets a user narrow down target instances before applying an action), or another mechanism that lets a subset be chosen before the migration is confirmed.
Impact
Without this, teams either accept the risk of migrating every running instance of a version at once, or spend time migrating instances individually. A selectable-subset option would make version migrations safer to roll out incrementally and more practical for larger numbers of instances.
Description
The process migration wizard currently supports only two scopes: migrate a single process instance (from the instance detail view) or migrate all running instances of the source process version (from the Processes view). There is no way to migrate an arbitrary subset of instances in one action.
Use case
A user needs to migrate only some of the running instances of a process version to a newer version — for example, instances matching a specific business key, a specific active activity, or a manually picked list — while leaving the rest on the current version until they complete naturally or are migrated later.
Today the only way to achieve this is to migrate instances one by one through the instance detail view, which is impractical when more than a few instances need to move together.
Expected behavior
The migration wizard should allow selecting which of the source version's running instances participate in the migration, instead of only "one" or "all". This could take the form of a filterable/selectable list of matching instances (similar to how the batch operations wizard already lets a user narrow down target instances before applying an action), or another mechanism that lets a subset be chosen before the migration is confirmed.
Impact
Without this, teams either accept the risk of migrating every running instance of a version at once, or spend time migrating instances individually. A selectable-subset option would make version migrations safer to roll out incrementally and more practical for larger numbers of instances.