The two models of sharing (versions vs sprints) do not match. There will be cases, where we need to compromise and prioritize. What are the paradigms we adhere to?

Overall goal: Users of the current backlog implementation can continue to work with the newly introduced sprints with as little manual reconfiguration as possible. 

Thesises:

* Copying a version multiple times is to be avoided (not a must).

* All sprints <-> Work package relations continue to exist.

* Begin of the insertionWork packages don't change the project (must).

* End of the insertion Sprint sharing is disabled by default (see ##72004) and sharing option is changed in the migration if needed.

* It is ok if sprints are moved up in the project chain even if that means people will loose edit permissions and others gain it on those moved sprints.

* It is ok if sprints show up in projects they were not visible in before.

* It is ok if sprints vanish from projects if they were not used (no connection to a work package)

* Versions are considered sprints if they:

* Are used by any work package configured to be Story or Begin of the insertionTaskEnd of the insertion Begin of the deletion typeEnd of the deletion in a project with backlogs enabled.

* Are configured to be displayed "left"