Context
Some old forges still use the old tracker engine (named tracker v3) in addition of the current one (named tracker v5). When a project is created, based on an old one that still uses the old tracker v3 engine.
This point is important because of that, the old engine is still activaly used on theses Tuleap instances instead of seeing its usage decreasing.
Solution
The proposed solution is the following. When a project is created based on a project that still uses the old tracker v3 engine, the trackers defined in the tracker v3 service for the template project will be imported into the tracker v5 service for the new project and the tracker v3 service will not be activated (and activalbe ?) on the newly created project.