**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**

* Begin of the insertionSetting a version for a work package works as usual

End of the insertion Begin of the deletion ...


**Technical notes**

End of the deletion * Begin of the insertionRoadmap works as usual

* Bulk edit correctly does bulk operations on versions

* Copy of projects correctly copies work package versions

* Version boards properly loadEnd of the insertion Begin of the deletion ...


**PermissionsEnd of the deletion and Begin of the insertionupdate versions

End of the insertion Begin of the deletion visibility considerations**

End of the deletion * Begin of the insertionNew installations come with versions prefilled as expectedEnd of the insertion Begin of the deletion _To whom is this feature visible?_End of the deletion

* Begin of the insertionQueries that reference versions stlill work properly

End of the insertion Begin of the deletion _When is it not visible?_


**Translation considerations**

End of the deletion * Begin of the insertionFilters for versionsEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the insertiontarget versions haveEnd of the insertion Begin of the deletion phrases inEnd of the deletion the Begin of the insertionsame behaviourEnd of the insertion Begin of the deletion key languages_ End of the deletion


Begin of the insertion**Technical notes**End of the insertion Begin of the deletion **Out of scope**End of the deletion

Begin of the insertionThis is a large change under the hood, but the behaviourEnd of the insertion Begin of the deletion * <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informedEnd of the deletion of the Begin of the insertionapplication should not change.End of the insertion Begin of the deletion changes._End of the deletion

Begin of the deletion <br>

End of the deletion 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 Begin of the insertionwork\_package.version


**Out of scope**

* User facing changes (other than some filter keys/ids)End of the insertion Begin of the deletion versionEnd of the deletion


<br>