**As** an extensions maintainer
**I want to** be able to adapt early
**so that** I can support old and new versions on OpenProject

**Acceptance criteria**

* Setting a version for a work package works as usual

* Roadmap works as usual

* Bulk edit correctly does bulk operations on versions

* Copy of projects correctly copies work package versions

* Version boards properly load and update versions

* New installations come with versions prefilled as expected

* Queries that reference versions stlill work properly

* Filters for versions and target versions have the same behaviour


**Technical notes**

This is a large change under the hood, but the behaviour of the application should not change.

The goal is to replace version usage everywhere so that we can rely on target\_versions as being the single source of truth. This should not cause any product behaviour changes, only transform how we use data.

* make sure write operations properly persist the data in target\_versions

* make sure all subsystems read from target\_versions, and ignore work\_package.version


**Out of scope**

* User facing changes (other than some filter keys/ids)


<br> Begin of the insertion

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/922272/content">

<br>End of the insertion