Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to last technical version, not only based on version tag #34

Open
tobiasschaefer opened this issue Feb 8, 2022 · 0 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@tobiasschaefer
Copy link

Process instances that are not on the current version of the process model are always migrated to the current version. The version tag is used for this purpose.

Under certain circumstances there may be several deployments of the last version (tag) and then it can happen that the instances of all are on the last version, but not necessarily on the last deployment/process definition.

This is irritating when you look in the cockpit for the instances of the last version tag. Could the migrator be adapted so that it also takes this into account?

@BenFuernrohr BenFuernrohr self-assigned this Mar 22, 2022
@BenFuernrohr BenFuernrohr added the enhancement New feature or request label Mar 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants